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
New functionality – Split Payments // 22.04.2020
We are excited to announce the release of the new functionality - upgrade of PIS API components for the execution of Split Payments. Starting April 22nd, you will be able to use both versions of our PIS APIs: the previous one (v2_1_1.1) as well as the new (v2_1_1.2) which includes the implementation of the Split Payment functionality for domestic, recurring, and bundle services for BusinessPro PSUs. The existing v2_1_1.1 will continue to be supported for at least 3 months and a separate notification on retirement will be sent out.
Due to the introduction of new APIs, our production environment may be temporarily unavailable for approximately 2 hours from 05.00 am to 07.00 am on April 22nd, 2020.
You can find more details in our documentation in PIS: 2_1_1.2 section.
Changelog - what’s new?
Change No. 012
Change description: Upgrade of PIS API components for the execution of Split Payment. Implementation of the Split Payment functionality in domestic, recurring, and bundle services.
Impact on TPP: The change affects only AISP TPPs. The functionality extending the scope with parameters related to Split Payment works as an alternative, and in parallel with the previous version of the PIS API.
Deployment date: April 22nd, 2020
If you have any questions don’t hesitate to contact us via developer@alior.pl.
Updates to Open API production environment // 30.03.2020
We would like to inform you that we are introducing additional features to our Open API production environment.
Therefore our API will be unavailable for approximately 2 hours from 06.00 am to 08.00 am on March 30th, 2020.
Deployment date: March 30, 2020
All changes are backwards compatible, so they will not impact your current production applications
What’s new?
Change No. 005
Change description: For EEA foreign transfers we have added the possibility to initiate transfers in EUR to domestic banks.
Change No. 006
Change description: For foreign transfers (non-EEA), we have added the possibility to perform such transfers to domestic banks.
Change No. 007
Change description: We have introduced fixes in the handling of the EEA transfer type
Change No. 008
Change description: Improved control of requestID in the getBundle header and body fields check
Change No. 009
Change description: Improvement of the issues associated with the blank AIS lists
Change No. 010
Change description: A fix to getTransactionsDone response to include sender and recipient name
Change No. 011
Change description: A fix to getTransactionDetails response to include sender and recipient name
If you have any questions don’t hesitate to contact us via developer@alior.pl.
Sandbox – what’s new? // March 2020
We would like to inform you that on March 12th we will introduce additional changes to our Sandbox – it will not impact the availability of our APIs.
What’s new?
Deployment date: March 12, 2020
Change No. 001
Change description: In EEA foreign transfers we enable transfers in EUR to banks in Poland
Change impact: no impact on TPPs
Change No. 002
Change description: For foreign transfers in non-EEA countries, we add foreign currency transfers to banks in Poland
Change impact: no impact on TPPs
Change No. 003
Change description: Improvement in the handling of the EEA transfer type
Change impact: no impact on TPPs
Change No. 004
Change description: The field with the requestID in the getBundle header and body service must be the same
Change impact: no impact on TPPs
Change No. 005
Change description: implementation of the Split payment functionality in domestic, recurring, and bundle services (version v2_1_1.2)
Change impact: no impact on TPPs
Change No. 006
Change description: Improvement of the issues associated with the blank lists on sandbox environment
Change impact: no impact on TPPs
If you have any questions don’t hesitate to contact us via developer@alior.pl
Changes to Open API production environment // 28.01.2020
We would like to inform you that we will introduce additional changes to our Open API production environment.
Therefore our API will be unavailable for just an hour from 11.00 am to 12:00 am on January 28th, 2020.
What’s new:
Deployment date: January 28, 2020
Change No. 001
Change description: The getConfirmationOfFunds service will accept the value utf-8 in Accept-Charset header. (was only UTF-8).
Change impact: no impact on TPPs
Change No. 002
Change description: If you send the request message for tax service, you have to set the full year in field ‘year’ (is optional)
Change impact: after this date, only the full-year value will be allowed in the field year
Change No. 003
Change description: The transfer for individual tax account will be forbidden for all transfer services except tax service.
Change impact: No technical impact. The transfer for individual tax account will be forbidden for all transfer services except tax service.
Change No. 004
Change description: If you send the request message, you have to change data in fields sendDate and scopeTimeLimit. The acceptable value of a string representing the given date in these fields will be in the ISO 8601 format according to universal time in the form of YYYY-MM-DDTHH:mm:ss.sssZ
Change impact: after this date the date in fields sendDate and scopeTimeLimit in other pattern than YYYY-MM-DDTHH:mm:ss.sssZ will be forbidden.
Sandbox - what's new? // January
Following the issues reported by our community, we introduce a couple of changes to our developer's portal.
What’s new:
Deployment date: January 16, 2020
Change No. 001
Change description: The getConfirmationOfFunds service will accept the value utf-8 in Accept-Charset header. (was only UTF-8).
Change impact: no impact on TPPs
Change No. 002
Change description: If you send the request message for tax service, you have to set the full year in field ‘year’ (is optional)
Change impact: after this date, only the full-year value will be allowed in the field year
Change No. 003
Change description: The transfer for individual tax account will be forbidden for all transfer services except tax service.
Change impact: No technical impact. The transfer for individual tax account will be forbidden for all transfer services except tax service.
If you need any additional information don't hesitate to contact us: developer@alior.pl.
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.
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.
Sandbox - what's new?
What’s new?
Change No. 001
Change description: If you send the request message, you have to change data in fields sendDate and scopeTimeLimit. The acceptable value of a string representing the given date in these fields will be in the ISO 8601 format according to universal time in the form of YYYY-MM-DDTHH:mm:ss.sssZ
Change impact: after this date the date in fields sendDate and scopeTimeLimit in other pattern than YYYY-MM-DDTHH:mm:ss.sssZ will be forbidden.
Change No. 002
Change description: The getTransactionsDone response will be enriched with simple name and postal address data. The fields sender and recipient could have new values when are available for the customer.
Change impact: no impact on TPPs.
Change No. 003
Change description: The getTransactionDetails response will be enriched with simple name and postal address data. The fields sender and recipient could have new values when are available for the customer.
Change impact: no impact on TPPs
If you need any additional information please do not hesitate to contact us