News
Recent
Temporary issues with API services | June 13th/14th, 2026
We kindly inform you that due to maintenance work planned in the Bank’s systems, there may be temporary issues with using API services on the night from 10:00 PM on the 13th of June to 6:00 AM on the 14th of June 2026.
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.
Previous
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
Temporary issues with authentication process in Alior Bank internet banking for AIS
Please be advised that temporary issues with authentication process for AIS requests requiring full SCA through Internet Banking have been fixed.
If you have any questions, please do not hesitate to contact us: developer@alior.pl
Unavailability of Open API | November 28th/29th, 2020
With regard to the planned merger of T-Mobile Banking Services branch with Alior Bank on 29.11.2020, Open API will be unavailable. The technical break will last from Saturday 28.11.2020 from 11 pm to Sunday 29.11.2020 until 7 pm.
Operational merger of T-Mobile Banking Services and Alior Bank
T-Mobile Poland and Alior Bank have decided to end their cooperation under the brand of T-Mobile Banking Services. Therefore as of November, 29th 2020 T-Mobile Banking Services customers will use Alior Online internet banking and Alior Mobile application.
What does this mean for TPP?
The operational merger of T-Mobile Banking Services and the Bank means that as of November, 29th 2020:
- both the brand and logo of T-Mobile Banking Services will not be present in the market - existing T-Mobile Banking Services customers after the operational merger with Alior Bank will use Alior Bank's online banking and mobile application;
- the consent granted to T-Mobile Banking Services will cease to apply after the operational merger of T-Mobile Banking Services and Alior Bank. In order to provide the services defined within PSD2, a new PSU consent will be required and a new token will be required from TPP;
- account numbers and transaction ids will remain unchanged.
This change is connected with carrying out the necessary IT works, therefore the planned unavailability of API will take place on 29th November, 2020. We will inform you about its details in a separate correspondence and will publish the information in the News section of the Developer Portal.
In case of any questions, please do not hesitate to contact us at developer@alior.pl
Kind regards,
Open Banking Team, Alior Bank S.A.
Alior Bank Developer Satisfaction Survey
We invite you to participate in a survey about the Alior Bank developer portal. (Please click here: Alior Bank Developer Satisfaction Survey).
We would like to hear the voice of our community & improve our portal with accordance to your opinion.
The answers are completely anonymous and will help us to identify directions for further development and improvements.
We will be grateful for your feedback!
Unavailability of Open API | October 25th, 2020
We kindly inform you that due to the implementation
work planned by the Bank some of the services provided under the API
productionenvironment will be unavailable on October 25th from 0.30 am until 8.00 am.
Unavailability of Open API | October 22nd/23rd, 2020
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 the night between 22 and 23 of October from 11.00 pm until 0.30 am.
Planned changes in Open API Sandbox environment // 21st October 2020
We are happy to announce that on 21st October we implement a series of improvements and functionalities to our Open API Sandbox environment.
Hence, we would like to inform that due to the implementation of the changes, there may be some interruptions in the functionality of our Sandbox on October 21, 2020 from 10:00 am to 11:00 am.
You can find more details about the changes in our documentation in PIS section 2_1_1.2 & AIS 2_1_1.1.
Changelog - what’s new?
Deployment date: October 21, 2020
Change No. 016
Change description: Enabling the execution of requests with ipv6 address.
Service(s) & Product impacted: AIS, PIS, CAF, AS
Impact on TPP and Developers: Yes
Change No. 017
Change description: Enabling the tradeDate field for the getHolds service.
Service(s) & Product impacted: getHolds -AIS
Impact on TPP and Developers: Yes
Change No. 018
Change description: Enabling all AIS services to be requested any number of times in 4 slots for 5 minutes per day from the first call. After the 5-minute slot is completed, each subsequent request automatically opens another 5-minute slot until the 4 slots limit is reached.
Service(s) & Product impacted: all services -AIS
Impact on TPP and Developers: Yes
Change No. 019
Change description: Enabling transfers in the amount defined in the PolishApi Standard for bundle and tax services.
Service(s) & Product impacted: tax, bundle - PIS
Impact on TPP and Developers: Yes
Change No. 020
Change description: Adding mcc field for card transactions in the getTransactionDetail service.
Service(s) & Product impacted: getTransactionDetail - AIS
Impact on TPP and Developers: Yes
Change No. 021
Change description: Disabling an empty object for nontax transactions in the getTransactionsDone service.
Service(s) & Product impacted: getTransactionsDone - AIS
Impact on TPP and Developers: Yes
Change No. 022
Change description: Adjusting the output object to the PolishAPI Standard for the cancelPayment service. One element list will be returned.
Service(s) & Product impacted: cancelPayment - PIS
Impact on TPP and Developers: Yes
If you have any questions don’t hesitate to contact us via developer@alior.pl
Planned changes in Open API Production environment // 15th October 2020
We are happy to announce that on 15th October we implement a series of improvements and functionalities to our Open API production environment.
Hence, we would like to inform that due to the implementation of the changes, there may be some interruptions in the functionality of our production API on October 15, 2020 from 4.00 am to 6.00 am.
You can find more details about the changes in our documentation in PIS section 2_1_1.2 & AIS 2_1_1.1.
Additionally we kindly inform you, that according to the previous communication, currently supported API versions are API PIS 2_1_1.2 and API AS 2_1_1.2.
Changelog - what’s new?
Deployment date: October 15, 2020
Change No. 019
Change description: Enabling the execution of requests with ipv6 address.
Service(s) & Product impacted: AIS, PIS, CAF, AS
Impact on TPP: Yes
Change No. 020
Change description: Enabling the tradeDate field for the getHolds service.
Service(s) & Product impacted: getHolds -AIS
Impact on TPP: Yes
Change No. 021
Change description: Enabling all AIS services to be requested any number of times in 4 slots for 5 minutes per day from the first call. After the 5-minute slot is completed, each subsequent request automatically opens another 5-minute slot until the 4 slots limit is reached.
Service(s) & Product impacted: all services -AIS
Impact on TPP: Yes
Change No. 022
Change description: Enabling transfers in the amount defined in the PolishApi Standard for bundle and tax services.
Service(s) & Product impacted: tax, bundle - PIS
Impact on TPP: Yes
Change No. 023
Change description: Adding mcc field for card transactions in the getTransactionDetail service.
Service(s) & Product impacted: getTransactionDetail - AIS
Impact on TPP: Yes
Change No. 024
Change description: Disabling an empty object for non tax transactions in the getTransactionsDone service.
Service(s) & Product impacted: getTransactionsDone - AIS
Impact on TPP: Yes
Change No. 025
Change description: Adjusting the output object to the PolishAPI Standard for the cancelPayment service. One element list will be returned.
Service(s) & Product impacted: cancelPayment - PIS
Impact on TPP: Yes
Change No. 026
Change description: Enabling split payment functionality for a domestic service in the KW channel.
Service(s) & Product impacted: domestic - PIS
Impact on TPP: Yes
Change No. 027
Change description: Enabling mapping in the detailedStatus field for business customers.
Service(s) & Product impacted: PIS
Impact on TPP: Yes
Change No. 028
Change description: Modification of description field for card transactions in getTransactionsDone and getTransactionDetails services.
Service(s) & Product impacted: getTransactionsDone, getTransactionDetails - AIS
Impact on TPP: Yes
Change No. 029
Change description: Enabling the cancelRecurringPayment service for corporate clients.
Service(s) & Product impacted: cancelRecurringPayment - PIS
Impact on TPP: Yes
If you have any questions don’t hesitate to contact us via developer@alior.pl
Unavailability of Open API | October 9/10th, 2020
We kindly inform you that due to the implementation workplanned by the Bank some of the services provided under the API production environment will be unavailable on the night between 9 and 10 of October from 11.00 pm until 6.00 am.