Full ISO20022 Purpose Code Support for SEPA Instant Payments
SEPA Instant Payments now support the full set of ISO20022 External Purpose Codes, enabling more granular payment purpose classification and improved reconciliation.
SEPA Instant Payments now support the full set of ISO20022 External Purpose Codes, enabling more granular payment purpose classification and improved reconciliation.
FX rates are now included in payment confirmations (e.g. pacs.008 and MT103 messages) for applicable Agency Banking and Correspondent Banking transactions involving currency conversion.
We have deprecated our V1 and V2 FX rates endpoints as they have been replaced by a brand new, unified V3 FX rates endpoint.
Support for additional purposeCode values for SEPA Instant payments is now live, enabling more granular payment purpose definition.
As part of our ongoing efforts to improve our platform, we will be introducing new version of Bank-To-Customer Statement, which may require actions from you. The changes will be in effect from the 15th of July, 2026. Additionally, we are introducing a new intraday reconciliation report - Bank-To-Customer Account Report, which will be available in JSON, CSV and CAMT.052.001.08.
We are introducing a new optional parameter, mtlsEnabled, which allows you to enable or disable mTLS for a webhook subscription when using the subscription update endpoint.
Soon, you’ll be able to specify routing preferences for currencies beyond EUR, giving you greater control over how your payments are routed and enabling you to optimise for speed, cost, or specific scheme requirements.
We are introducing new optional properties that allow you to specify the debtor country code via Payment Initiation endpoints and various Virtual Account endpoints. For non-EEA debtors, the country must be provided using a valid ISO country code, which will be transmitted to the beneficiary as part of the payment.
Soon you will be able to initiate WERO refunds via all our payment initiation endpoints. We are adding a new optional property, categoryPurposeCode, and expanding the values for the existing purposeCode property: