Cancellation Requests

The investigation family: MT192 and MT292 requests for cancellation to and from camt.056, and customer cancellation requests (camt.055) forwarded to the interbank formats.

Formats

Format	What it is	Versions accepted	Emitted by default
`mt192`	Request for cancellation (customer payments)	n/a	n/a
`mt292`	Request for cancellation (bank transfers)	n/a	n/a
`camt.056`	FI-to-FI payment cancellation request	`.001.08` – `.001.11`	`.001.08`
`camt.055`	Customer payment cancellation request (source only)	`.001.08`	n/a

Pairs

From	To
`mt192`, `mt292`	`camt.056`
`camt.056`	`mt192`, `mt292`
`camt.055`	`mt192`, `mt292`, `camt.056`

Queries (MT195/MT295, camt.110) and answers (MT196/MT296, camt.111) share the same canonical model but are separate families, so a cancellation request never converts into either. The answer to a camt.056, camt.029, is normalize-only. There is no canonical source.

How fields map

The canonical model is an investigation of kind cancellation-request: a case id, the references of the original payment, reason codes and free narrative.

MT192/MT292 to camt.056.

:20: becomes the case id and assignment id; :21: the original end-to-end id.
:11S: identifies the original message: line 1 (the MT type, such as 103) becomes the original message name MT103; the date and optional session and sequence numbers become the original message id.
:75: lines that start with a cancellation reason codeword (/DUPL/, /FRAD/, /CUST/, …) become reason codes; other text becomes narrative.
:79: lines become narrative.
The copy of the original message that follows is kept as narrative, except the first copied :32A:, which becomes the original amount and settlement date.

camt.056 to MT192/MT292. One MT message per underlying transaction. Reason codes become /CODE/ lines in :75:; narrative goes to :79:. The target id (mt192 or mt292) decides the message type. An original message name like pacs.008.001.08 is reduced to its MT type (103) for :11S:.

camt.055 sources. A customer's cancellation request becomes one interbank request per underlying transaction. A reason given at batch or group level fills in every transaction that has none of its own.

Where information is lost

Situation	Warning
camt.056 needs an assigner, an assignee and a creation time that MT does not carry; `NOTPROVIDED` placeholders and the conversion time are used	`MISSING_REQUIRED_DEFAULTED`
`:11S:` needs a date: the original settlement date or creation time is used when the original message id is not a date	`MISSING_REQUIRED_DEFAULTED`
A reason code outside the recognised set, or a proprietary reason	`RETURN_REASON_UNMAPPED`
UETR, assigner, creation time and the losing reference (MT has one `:21:`)	`DROP_FIELD`
An original message name that is an ISO id: the version is reduced to the MT type	`DROP_FIELD`
An original message name with no MT type; `:11S:` gets `199`	`CODE_UNMAPPED_PROPRIETARY`
camt.055 original payment information id and requested collection date (no slot)	`DROP_FIELD`
A case id longer than 16 characters; narrative over 35 lines	`TRUNC_REFERENCE`, `TRUNC_REMITTANCE`

Conventions

Recognised cancellation reasons: AGNT, AM09, COVR, CURR, CUST, CUTA, DUPL, FRAD, TECH, UPAY. Others travel as written and are flagged.
Original message id. MT has no original message id, only the :11S: date (YYMMDD) with optional session and sequence numbers. That digit string becomes the camt.056 original message id, and a 6- or 16-digit id converts back into :11S:.
Distinct case ids. When several transactions of one camt.056 or camt.055 fall back to the shared assignment id, each output gets a -1, -2, … suffix so no two MT messages share a :20:.
Sibling detection. A bare MT292 detects as mt192; send the FIN envelope or from=mt292 to keep the type.

Example

curl -sS -X POST "https://api.transmute.403fin.io/v1/convert?to=camt.056" \
  -H "Authorization: Bearer $TRANSMUTE_KEY" \
  -H "Content-Type: text/plain" \
  --data-binary @- <<'MT'
:20:CNCL-2026-0001
:21:PAY-2026-0001
:11S:103
260610
:75:/DUPL/
:79:DUPLICATE OF AN EARLIER TRANSFER
:32A:260610EUR1250,00
MT

The result document, formatted:

<Assgnmt>
  <Id>CNCL-2026-0001</Id>
  <Assgnr><Pty><Nm>NOTPROVIDED</Nm></Pty></Assgnr>
  <Assgne><Pty><Nm>NOTPROVIDED</Nm></Pty></Assgne>
  <CreDtTm>2026-06-10T09:00:00Z</CreDtTm>
</Assgnmt>
<Case><Id>CNCL-2026-0001</Id>...</Case>
<Undrlyg>
  <TxInf>
    <OrgnlGrpInf><OrgnlMsgId>260610</OrgnlMsgId><OrgnlMsgNmId>MT103</OrgnlMsgNmId></OrgnlGrpInf>
    <OrgnlEndToEndId>PAY-2026-0001</OrgnlEndToEndId>
    <OrgnlIntrBkSttlmAmt Ccy="EUR">1250.00</OrgnlIntrBkSttlmAmt>
    <OrgnlIntrBkSttlmDt>2026-06-10</OrgnlIntrBkSttlmDt>
    <CxlRsnInf><Rsn><Cd>DUPL</Cd></Rsn><AddtlInf>DUPLICATE OF AN EARLIER TRANSFER</AddtlInf></CxlRsnInf>
  </TxInf>
</Undrlyg>

The response carries four MISSING_REQUIRED_DEFAULTED (info) warnings, for Assgnmt/Assgne, Assgnmt/Assgnr, Case/Cretr and Assgnmt/CreDtTm; meta.targetType is camt.056.001.08.

Was this page helpful?