camt.029.001.09 XSD schema and business logic

A camt.029 is the Resolution Of Investigation response message sent by a financial institution to resolve a previously raised investigation. In the context of payment cancellations it is the direct counterpart to the camt.056: the receiving bank uses camt.029 to accept, reject, or provide status on a cancellation request.

1. Message definition and structure

Access the message definition and structure here.

Document
└── RsltnOfInvstgtn               ← Root business message
    ├── Assgnmt      [1..1]        ← Case assignment (mandatory)
    ├── RslvdCase    [0..1]        ← Case being resolved (optional)
    ├── Sts          [1..1]        ← Investigation status (MANDATORY — heart of the message)
    ├── CxlDtls      [0..n]        ← Cancellation details (optional, one per underlying)
    ├── ModDtls      [0..1]        ← Modification status details (optional)
    ├── ClmNonRctDtls[0..1]        ← Claim non-receipt details (optional)
    ├── StmtDtls     [0..1]        ← Statement resolution entry (optional)
    ├── CrrctnTx     [0..1]        ← Corrective transaction reference (optional)
    ├── RsltnRltdInf [0..1]        ← Resolution-related data: settlement, compensation, charges (optional)
    └── SplmtryData  [0..n]        ← Supplementary / proprietary data (optional)

2. Business logic

2.1 Case assignment (`Assgnmt`)

The case assignment tag identifies who is assigning the case to whom

Element	Name	Presence	Description
`Id`	Case identification	Mandatory	Unique assignment identifier (same as message id)
`Assgnr`	Case assigner	Mandatory	Responding party (only Agent accepted)
`Assgne`	Case assignee	Mandatory	Requesting party receiving the response (only Agent accepted)
`CreDtTm`	Creation date time	Mandatory	Creation date time

2.2 Resolved case (`RslvdCase`)

The resolved case tag is ignored on incoming camt.029 and will not be populated for outgoing camt.029.

2.3 Investigation status (`Sts`)

The investigation status only accepts a confirmation code

Element	Name	Presence	Description
`Conf`	Investigation execution confirmation code	Mandatory	Can take one of the following values: `CNCL`: cancellation completed `RJCR`: cancellation rejected `PDCR`: cancellation pending

2.4 Cancellation details (`CxlDtls`)

The cancellation details tag provides the underlying payments concerned by the investigation status. Only individual transaction-level status TxInfAndSts is supported by Mambu Payments.

Each individual underlying payment is mapped according to the same rules as the incoming pacs.002 original payment identification here. The tags that will be taken into account to find the related payment are:

TxInfAndSts.OrgnlGrpInf.OrgnlMsgId
TxInfAndSts.OrgnlGrpInf.OrgnlMsgNmId
TxInfAndSts.OrgnlInstrId
TxInfAndSts.OrgnlEndToEndId
TxInfAndSts.OrgnlTxId
TxInfAndSts.OrgnlUETR

2.5. Identification of the cancellation status id (`CxlStsId`)

Each cancellation request is identified by a unique ID located at TxInfAndSts.CxlStsId that must be max 35 text.

2.6. Cancellation reason (`CxlRsnInf`)

The cancellation reason is provided by the TxInfAndSts.CxlStsRsnInf tag with following information:

Element	Name	Presence	Description
`Orgtr`	Originator	Mandatory	Originator If Reason code is `CUST` (customer request), the `Orgtr.Nm` (originator name) must be valued Else for other reason codes, the `Orgtr.Id.OrgId` must be valued with the bank code of the financial institution: `Orgtr.Id.OrgId.AnyBIC` if the bank code is a BIC format `Orgtr.Id.OrgId.Othr.Id` if the bank code is another format than a BIC
`Rsn.Cd`	Reason code	Mandatory	Reason code. Examples: `DUPL` — Duplicate payment `FRAD` — Fraudulent origin `TECH` — Technical problem `CUST` — Customer request `AC03` — Invalid creditor account number `AM09` — Wrong amount `CXLR` — Cancellation requested by counterpart
`AddtlInf`	Additional information	Optional	Additional information

2.7. Original Transaction Reference (`OrgnlTxRef`)

This tag echoes of the key fields from the original payment to help the receiving bank identify it. It usually contains the amount, interbank settlement amount and date, as well as parties (debtor, creditor, ultimate parties) description.

Mambu Payments do not rely on this information to find the related payment.

1. Message definition and structure

2. Business logic

2.1 Case assignment (Assgnmt)

2.2 Resolved case (RslvdCase)

2.3 Investigation status (Sts)

2.4 Cancellation details (CxlDtls)

2.5. Identification of the cancellation status id (CxlStsId)

2.6. Cancellation reason (CxlRsnInf)

2.7. Original Transaction Reference (OrgnlTxRef)