We will soon introduce automation to retry and re-route SEPA Instant payments upon soft and hard rejections, respectively. These additions will increase the transparency and enhance the straight-through processing of payments.
We will soon be adding two new properties to the response of the GET single payments, GET single payment by ID, GET single payment by transaction reference number endpoints and to the payload of the Webhooks notifications.
We will soon be adding a new property to the response of the GET single payments, GET single payment by ID, GET single payment by transaction reference number endpoints and to the payload of the Webhooks notifications.
All the Webhook notifications will include this property, except for the outgoingPaymentBooked notification type.
We will soon be adding three new properties to the response of the GET single payments, GET single payment by ID endpoints, the Reconciliation report and to the payload of the Webhooks notifications.
We have made some changes to the payment form in the Client Portal to improve the user experience, and as part of a general maintenance:
We will soon be adding three new properties to the response of the GET single payments and GET single payment by ID endpoints, and to the payload of the Webhooks notifications.
We have extended the list of production IPs, we require you to whitelist to continue to receive webhook notifications from us for certain events.
We will be making changes to our API endpoints from February 1st 2024 and you have until this date to take action if you use the affected endpoints to retrieve data that is older than six (6) months.
It is now possible to recall a payment yourself via the Client Portal and API, to increase transparency and speed on the management of payments.
We have added more details to our reconciliation report and our notifications, related to the additional remittance information (equivalent to field 72 of a MT103).
