Adding more details to GET single payments endpoints and Webhooks payload
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.
Action required: Extension of production IP whitelist for Webhook 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.
Upcoming breaking change
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.
New self-service functionality for recalls
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.
Additional remittance information now available in reports and notifications
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).
Specify the EUR payment rail
We have released a new functionality, which allows you to specify a payment to be executed as a SEPA Instant payment.
Specify the payment purpose code for CNH payments to China
It is now required to specify a payment purpose code for CNH payments to China. If the purpose code is not provided, the payment may be rejected, delayed, or incur additional charges. You can specify the payment purpose code via both the Client Portal and API. The supported codes are:
Specify the charge bearer
Until recently, Banking Circle generally only supported outgoing payments via the Banking Circle API with the 'SHA' charge bearer, which indicates that charges are split between sender and beneficiary.
Enhanced duplicate checks based on idempotency
We have enhanced our duplicate checks by extending all payment initiation endpoint to accept an idempotency key header. This key will prevent same payment getting initiated more than once due to for example connectivity issues. The idempotency key provided by you needs to be unique, maximum 100 characters and will have validity of 10 days. This key is used internally only and will not be exposed in any report or endpoint.
Held rates added to our FX solution
It is now possible to request held rates (FX rates that have a longer time span than 30 seconds). That allows you to lock in a FX rate for a given time period that you decide, thereby simplifying and adding certainty to the following trades where you choose to use the held rate.