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
Temporary technical issues with initiating foreign transfers | November 13th, 2025
We kindly inform you, that due to maintenance work planned by the Bank that will take place on the 13th of November 2025 between 7:00 AM and 6:00 PM, there may be temporary technical issues with initiating foreign transfers under our API production environment.
Planned service downtime due to time change | October 25-26, 2025
We kindly inform you that due to the scheduled switch from daylight saving time to standard time, a temporary unavailability of services will occur. The downtime will begin on Saturday, October 25th, 2025 at 11:00 PM and will last until Sunday, October 26th, 2025 at 6:00 AM. During this time, access to the production environment of our API services may be limited or unavailable. We apologize for any inconvenience and appreciate your understanding.
Planned changes in API Sandbox environment | October 23rd, 2025
We kindly inform you, that on the 23rd of October 2025, changes in the account information services AIS 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.
In the following AIS services:
/v3_0.1/accounts/v3_0.1/getHolds
/v3_0.1/accounts/v3_0.1/getTransactionDetails
/v3_0.1/accounts/v3_0.1/getTransactionsCancelled
/v3_0.1/accounts/v3_0.1/getTransactionsDone
/v3_0.1/accounts/v3_0.1/getTransactionsPending
/v3_0.1/accounts/v3_0.1/getTransactionsRejected
/v3_0.1/accounts/v3_0.1/getTransactionsScheduled
the following objects have been added:
NameAddressStructured
AddressStructured
UltimateParty
Their usage has been described within the SenderRecipient object, where the following non-mandatory attributes have been added:
nameAddressStructured
identifiers
ultimateParty
We will inform about the production release of sender and recipient data, including the above-mentioned data in a separate notification.
Planned changes in foreign transfers | September 10th, 2025
According to the announcement published on the 25th of April 2025, regarding changes in the supporting of requests to initiate foreign transfers to our API, we kindly inform you, that the production deployment is scheduled for Wednesday, September 10th, 2025, will take place between 7:00 AM and 8:00 AM.
Domestic payments will not be affected.
Unavailability of Sandbox and Developer Portal | July 8th, 2025
We kindly inform you, that due to maintenance work planned by the Bank some of the services provided under the API Sandbox environment and our Developer Portal may be unavailable on the 8th of July 2025 between 8.00 AM and 3.00 PM. This unavailability will not impact the production environment.
EDIT: We inform you, that due with the continuation of maintenance work, some of the services provided under the API Sandbox environment may be unavailable on the 9th of July 2025 between 8.00 AM and 10.00 AM.
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.
Planned changes in API Sandbox environment | April 29th, 2025
We kindly inform you, that on the 29th of April 2025 to our API Sandbox environment, changes in the address structure of recipients in foreign transfers will be made available in accordance with the ISO 20022 standard.
Planned changes in foreign transfers
We kindly inform you, that after the 1st of August 2025 changes in the address structure of recipients in foreign transfers will be made available in accordance with the ISO 20022 standard.
Planned changes in initiating EEA and nonEEA transfers | January 16th, 2025
According to the announcment published on the 14th of October 2024, we kindly inform you, that on the 16th of January 2025 to our API production environment will be implement the requirement to complete at least the first line with the recipient`s name and the third line with the recipient`s address when initiating EEA and nonEEA transfers.