pain.012.001.08 MandateAcceptanceReportV08

ISO 20022 pain Messages

Report acceptance or rejection of a mandate request and, when applicable, return mandate information.

On 3 January Fictional Cedar Bank sends DEMO-M012-001 with Accptd=true for the 2 January initiation DEMO-M009-001 and mandate DEMO-MANDATE-001. The original message name is pain.009.001.08. This demonstrates a positive mandate-initiation response. It does not accept the later 20 January amendment or cancellation just because those messages mention the same mandate. An implementation should attach the report to the initiation request, retain the evidence and expose the appropriate mandate state to collection processing. The XML contains no payment transaction, booking or settlement result.

This message reports both positive and negative mandate outcomes. Accptd is a boolean, not a payment-status code such as ACTC and not evidence of settlement.

Base-XSD optionality and business sufficiency differ: original-request references and a rejection reason are not universally mandatory merely because a bank needs them for its workflow. Apply the documented service profile without changing the base definition.

An accepted copy request can return mandate information; receipt of copied information does not itself grant new authority to collect. The supplied worked example accepts initiation and is not a copy-response example.

The EPC 2025 SDD Core e-Mandate guide uses pain.012.001.06. This pain.012.001.08 lesson illustrates ISO base structure and fictional processing; it makes no SEPA or CBPR+ conformance claim.

Explore the complete Payment Life Cycle