News
Recent
Planned changes in API Sandbox environment | April 29th, 2026
We kindly inform you, that on the 29th of April 2026, changes in payment initiation services (PIS) in the scope of structured address, will be made available to our API Sandbox environment. These changes affect the communication structure and data format in accordance with the ISO 20022 standard.
The changes consist in making a structured address available in domestic transfers (domestic/tax/recurring domestic and tax/ bundle domestic and tax) while still allowing transfers to be made using the old address format.
The changes concern the SenderPIS and RecipientPIS objects in the services:
/v3_0.1/auth/v3_0.1/authorize
/v3_0.1/auth/v3_0.1/token
In domestic transfers, the nameAddress or nameAddressStructured classes will be supported in parallel.
For EEA and nonEEA foreign transfers, the nameAddress field has been disabled, and only the nameAddressStructured field is supported.
The changes concern the SenderPIS and RecipientPIS objects in the services:
/v3_0.1/auth/v3_0.1/authorize
/v3_0.1/auth/v3_0.1/token
A structured address has been made available for domestic transfers (domestic/tax/recurring domestic and tax/ bundle domestic and tax) while still allowing transfers to be made using the old address format.
The changes concern the SenderPIS and RecipientPIS objects in the services:
/v3_0.1/payments/v3_0.1/tax
/v3_0.1/payments/v3_0.1/domestic
/v3_0.1/payments/v3_0.1/recurring
/v3_0.1/payments/v3_0.1/bundleTransfers can be made by providing only the recipient's name by completing at least 1 address line in nameAddress or by completing the name field in nameAddressStructured.
If the transfer contains data in the nameAddressStructured field and the addressStructured field, then it will be necessary to complete the data in the townName and countryCode fields.
Support for the countrySubDivision field for domestic transfers has been disabled. The data provided in this field will be transferred to the recipient's Bank only as part of a foreign transfer.
In other transfer types, the data entered in this field will be rejected.The following fields will be supported for domestic and tax transfers: streetName, buildingNumber, room, postCode, townName, country.
The remaining fields will be ignored.
Within the Sandbox environment, we provide the ability to test the solution in both the old and new address formats.
We will implement these changes in the production environment after the 1st of August 2026, and we will inform you about the exact date in a separate communication.
Once the changes are implemented in the production environment, a transition period will begin during which it will be necessary to switch from an unstructured address to a structured address.
The ability to make transfers with the old unstructured address will be disabled, and we will inform you about the exact date in advance.
After the transition period, using existing payment formats, as well as new ISO 20022 formats that are not adapted to a wider range of data, will result in payment rejection.
Unavailability of API services | March 29th, 2026
We kindly inform you that due to maintenance work planned by the Bank some of the services provided under the API production environment will be unavailable on 29th of March 2026 from 00:00 AM until 07:00 AM.
The Bank does not provide immediately available alternative options for payment service providers using the dedicated interface during its unavailability.
Previous
Unavailability of Sandbox and Developer Portal | February 19th, 2021
We kindly inform you that due to maintenance work planned by the Bank some of the services provided under the API Sandbox environment will be unavailable on February 19th from 8.00 a.m to 12.00 p.m. This unavailability will not impact the production environment.
We are also happy to announce that on 19th February new functionalities and improvements will be available in our Developer Portal.
Changelog - what’s new?
Deployment date: February 19, 2021
Change No. 026
Change description: Developer Portal
Service(s) & Product impacted: My Organization
Change impact: Improvement of the My organization management
process, including inviting other users into My organization.
Change No. 027
Change description: Developer Portal
Service(s) & Product impacted: Subscribe
Change impact: Adding the option to select an API version on the Subscribtion level.
Change No. 028
Change description: Developer Portal
Service(s) & Product impacted: New API Categories
Change impact: Introduction of a classification for API's published on the Developer Portal into two categories API Premium and API Compliance.
If you have any questions don’t hesitate to contact us at: developer@alior.pl
Polish API 3.0 & Refresh token available in the production environment // 18th February 2021
We are happy to announce that on 18th February a new version of our PSD2 APIs will be available in our production environment.
For details of improvements and new functionalities please refer to the documentation in PIS/AIS/CAF/AS APIs v3_0.1 PL sections.
Changelog - what’s new?
Deployment date: February 18, 2021
Change No. 030
Change description: Refresh token functionality
Service(s) & Product impacted: PIS, AIS
Change impact: The access token will be valid for 10 minutes. Upon its expiry, the token will need to be refreshed (refresh token) in order to obtain a new access token valid for another 10 minutes.
Change No. 031
Change description: The new header description in X-JWS-Signature response field
Service(s) & Product impacted: PIS, AIS
Change impact: Information about the used certificate will be sent in the JWS-Signature.
Change No. 032
Change description: The management process for request kid
Service(s) & Product impacted: PIS, AIS
Change impact: This enables for earlier registration of a new JWS certificate.
Unavailability of Open API | February 18th, 2021
We kindly inform you that due to the implementation work planned by the Bank some of the services provided under the API production environment will be unavailable on February 18th from 4.30 am until 7.00 am.
Unavailability of API services | February 12th/13th, 2021
We kindly inform you that due to maintenance work planned by the Bank some of the services provided under the API production environment will be unavailable on the night between 12 and 13 of February 2021 from 11.00 pm until 9.00 am.
Unavailability of API services | February 6th/7th, 2021
We kindly inform you that due to maintenance work planned by the Bank some of the services provided under the API production environment will be unavailable on the night between 6 and 7 of February 2021 from 8.00 am until 8.00 pm.
Unavailability of API services | February 6th/7th, 2021
We kindly inform you that due to maintenance work planned by the Bank some of the services provided under the API production environment will be unavailable on the night between 6 and 7 of February 2021 from 11.00 pm until 7.00 am.
Unavailability of API services | January 8th/9th, 2021
We kindly inform you that due to maintenance work planned by the Bank some of the services provided under the API production
environment will be unavailable on the night between 8 and 9 of January 2021 from 11.00 pm until 8.00 am.
Polish API 3.0 and Refresh token available in Sandbox environment // 17th December 2020
We are happy to announce that on 17th December a new version of our PSD2 APIs will be available in our Sandbox environment.
For details of improvements and new functionalities please refer to the documentation in PIS/AIS/CAF/AS APIs v3_0.1 PL sections.
The v3_0.1 APIs will be added to the production environment at the beginning of Q1/2021 – we will inform you about the exact implementation date in advance in a separate communication together with deprecation plans of previous versions.
Changelog - what’s new?
Deployment date: December 17, 2020
Change No. 023
Change description: Refresh token functionality
Service(s) & Product impacted: PIS, AIS
Change impact: The access token will be valid for 10 minutes. Upon its expiry, the token will need to be refreshed (refresh token) in order to obtain a new access token valid for another 10 minutes.
Change No. 024
Change description: The new header description in X-JWS-Signature response field
Service(s) & Product impacted: PIS, AIS
Change impact: Information about the used certificate will be sent in the JWS-Signature.
Change No. 025
Change description: The management process for request kid
Service(s) & Product impacted: PIS, AIS
Change impact: This enables for earlier registration of a new JWS certificate.
Deprecating previous versions API PIS and API AS (v2_1_1.1) on December 17th
After 8 months of maintaining in parallel both versions of API PIS (v2_1_1.1 & v2_1_1.2 ) and API AS (v2_1_1.1 & v2_1_1.2) in the production environment, we decided to deprecate the previous versions of our APIs.
We initially planned to deprecate versions of API PIS (v2_1_1.1) and API AS (v2_1_1.1) at the end of September 2020, however taking into account the active use of this version by TPPs the decision to deprecate it was postponed.
Therefore, we would like to inform that versions of API PIS (v2_1_1.1) and API AS (v2_1_1.1) will be finally deprecated on December 17th, 2020 in the production environment. Please take this change into account in your work on developing applications integrated with Alior Bank's Open API.
In case of any questions please contact us at developer@alior.pl
Disabling Sandbox API PIS (v2_1_1.1) and API AS (v2_1_1.1)
According to the communication published on 22nd June 2020, both versions of the PIS API (v2_1_1.1) and the AS API (v2_1_1.1) are disabled on the Sandbox.
For all subscriptions use the latest API version.
In case of any questions please contact us via developer@alior.pl