Rejected, the clearing system or the beneficiary bank supplies a reason code. This page explains where to read it and what the codes you are most likely to meet on EKS mean.
Where to find the code
- API:
statusReasonin Get payment, with acodeand amessage. - Dashboard: open the payment and go to Status history.
Who rejects a payment
EKS: SEPA Credit Transfer
Codes set by the EKS clearing service of Latvijas Banka. Source: Latvijas Banka, EKS clearing service specification.U01, U02 and U03 are raised by the clearing service, not by the beneficiary bank. The payment did not settle. Create a new payment if it is still needed.
EKS: SEPA Instant
A code set by the beneficiary bank reflects that bank’s own decision. In the sandbox the test counterparty decides, so its answers can differ from what you will see in production.
Duplicates and AM05
AM05 means the clearing system or the beneficiary bank has already received the same message. The platform itself never rejects a payment as a duplicate:
- Same
Idempotency-Key: the platform returns the payment created by the first request. Nothing new is sent. - New
Idempotency-Key: the platform creates a new payment, even when every business field equals an earlier payment. Protect against double submission on your side by storing one key per payment intent.
endToEndId does not cause AM05.
An AM05 rejection does not name the original payment. To find a possible earlier payment, search your transactions by endToEndId, amount and creditor.