Dear Client,

Dear Client,

You will soon be able to subscribe for a new webhook notification sent for a payment being rerouted via Sepa Credit transfer, if the rejection is received from Sepa instant credit transfer scheme. Subscription event type is 'PaymentRouting'. In the webhook notification, you will find the reason for routing mentioned in the field 'routingStatus'.

It will soon be possible to select T2 as a clearing network for processing your single, bulk or correspondent payments. We are already supporting 'SEPAINST' and 'SEPA' as an upfront rail selection for EUR. 'T2' is an additional network rail to the allowed values of 'clearingNetwork' property. If the beneficiary's account is not enabled for Target2, the payment will get rejected and you have will have to re-instruct the payment using another value for clearing network.

We have introduced a new generic endpoint which you can use to take a specific action on your payment or direct debit. Currently we support only 'Reject' action for a direct debit, however more actions such as 'Cancel' and 'Recall' will be supported in future.

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: