News
Recent
Unavailability of API production environment | June 30th, 2025 between 2:30 PM and 2:45 PM
We kindly inform you, that due to urgent technical work, our API production environment will be unavailable today on the 30th of June 2025 between 2:30 PM and 2:45 PM.
The Bank does not provide immediately available alternative options for payment service providers using the dedicated interface during its unavailability.
Migration of businesses customers to the new service system
We have started the process of transferring businesses customers service from the current BusinessPro online banking system to the new Alior Business system, which is gradually include subsequent groups of customers.
After transferring the service to the new system, consents to access accounts information service (AIS service) which were authorized by customers in BusinessPro banking, will no longer be supported. This is due to the fact each time the consent is authorized in the context of a specific online banking system through which the customer has online access to his accounts. In order to continue using the AIS service, customers will have to initiate the consent refresh process or grant a new one consent in your systems to provide the AIS service and go through the authorization process of this consent in the new Alior Business banking.
Previous
Sandbox – what’s new?? // May 2020
We would like to inform you that we introduced additional features & improvements to our Sandbox. They will be valid across all versions of our PIS & AIS APIs (v2_1_1.1 and v2_1_1.2). We plan to implement the following changes in the production environment at the beginning of June – we will inform you about the exact implementation date in advance in a separate communication.
Changelog - what’s new?
Deployment date: May 13, 2020
Change No. 013
Change description: We start providing information in the tppBundleId field.
Service(s) & Product impacted: bundle, getBundle in PIS.
Change impact: You can start using tppBundleId field included in our response.
Change No. 014
Change description: We implemented a detailed error message. You will receive a detailed message when there is no Alior Bank account number on the Sandbox environment to be used for testing.
Service(s) & Product impacted: domestic in PIS.
Change impact: no impact on TPP.
Change No. 015
Change description: You will be able to browse the holds created dynamically via domestic.
Service(s) & Product impacted: getHolds in AIS.
Change impact: no impact on TPP.
If you have any questions don’t hesitate to contact us via developer@alior.pl
Unavailability of API on May 9th, 2020
We kindly inform you that due to the implementation work planned by the Bank on May 9th 2020, between 04:00 and 07:00 am, some of the services provided under the API will be unavailable.
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