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.

Before this change, all single payments initiations, submitted via the POST / /v1/payments/singles have been subject a duplicate check to ensure that the same payment is not processed twice. If two single payments with the same amount, currency, beneficiary name and address, debtor reference and execution date are submitted, the second payment will be rejected. The second payment will get status pendingProcessing before being rejected. This duplicate check will still apply, in addition to the new check based on the idempotency key.