Developer

1. 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.
    

2. 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 
    

3. 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/bundle

    

4.  Transfers 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.

    

5. 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.

    

6. 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.

    

7. 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.