camt.056 payment cancellation request

EVERY ANNOTATED FIELD

Assgnmt/Id Assignment identification — mandatory

A unique reference for this assignment of the case from one party to the next.

Each hop of a relayed cancellation request is a new assignment with its own identification — the case travels, the assignment is per leg.

Assgnmt/Assgnr Assigner — mandatory

Who is handing the case over — the party asking for the cancellation on this leg.

Assgnmt/Assgne Assignee — mandatory

Who is being asked to deal with the case on this leg.

⚠ Sending the request to an agent that never saw the original payment produces a 'no original transaction received' answer and wastes the most time-critical hours of a recall.

Assgnmt/CreDtTm Assignment creation date and time — mandatory

When this assignment was created — the timestamp that starts the clock on this leg of the case.

Scheme rulebooks define windows for submitting recalls and for answering them; timestamps are the evidence in any dispute about deadlines.

Undrlyg/TxInf/CxlId Cancellation identification — optional

A unique reference for this specific cancellation request, assigned by the requester.

The reference the answering camt.029 echoes back — persist it, or matching answers to requests becomes guesswork.

Undrlyg/TxInf/OrgnlGrpInf/OrgnlMsgId Original message identification — conditional

The MsgId of the message that carried the payment to be cancelled, together with its message type in the same block.

Undrlyg/TxInf/OrgnlEndToEndId Original end-to-end identification — conditional

The EndToEndId of the payment the request is about, echoed exactly as it travelled.

Undrlyg/TxInf/OrgnlUETR Original UETR — conditional

The unique tracking identifier of the payment to be cancelled.

The UETR is what lets tracking infrastructure route and correlate a cancellation across the whole chain rather than hop by hop — the single most useful identifier in the message.

Undrlyg/TxInf/OrgnlIntrBkSttlmAmt Original interbank settlement amount — conditional

The amount and currency of the original payment — part of proving you are talking about the right transaction.

Undrlyg/TxInf/OrgnlIntrBkSttlmDt Original interbank settlement date — conditional

When the original payment settled — it also tells the receiving agent whether it is being asked to stop a payment or claw one back.

Undrlyg/TxInf/CxlRsnInf/Orgtr Cancellation originator — optional

Who wants the payment cancelled — the customer or the bank itself.

Schemes care about this distinction: which reason codes are available can depend on whether the customer or the PSP originated the request.

Undrlyg/TxInf/CxlRsnInf/Rsn/Cd Cancellation reason code — conditional

Why the cancellation is requested, coded from the ISO external cancellation reason set — for example DUPL (duplicate payment), TECH (technical problem), FRAD (fraudulent origin), CUST (requested by the debtor), or AM09 (wrong amount).

The reason changes the handling: a fraud-coded recall triggers a different urgency, and in some schemes a different consent and indemnity path, than a duplicate. The rulebook in force defines which codes are available to whom.

⚠ Coding a customer's ordinary mistake as FRAD to speed things up mislabels the case, can freeze the wrong things, and erodes trust with the counterpart bank.