pain.008.001.12 CustomerDirectDebitInitiationV12

ISO 20022 pain Messages

Ask a bank to collect money from one or more debtor accounts for a creditor.

Example Services requests EUR 125.00 from Cedar Books for invoice INV-DEMO-201, the January service subscription. DEMO-M008-001 is created at 2026-01-08T09:00:00Z; DEMO-DD-BATCH-001 asks for collection on 2026-01-10. DEMO-DD-INSTR-001 and DEMO-DD-E2E-001 identify the transaction. The file references DEMO-MANDATE-001 with signature date 2026-01-02, matching the separate fictional mandate story. Fictional Services Bank is the creditor agent and Fictional Cedar Bank the debtor agent. The scenario assumes appropriate authority outside the XML for teaching, but the message itself proves neither mandate effectiveness nor successful collection. The setup-fee credit transfer is a separate EUR 125.00 obligation.

The message can carry mandate references and extracts, but is not itself a mandate. In the V12 base schema, DrctDbtTx, its nested MndtRltdInf and the mandate-reference fields used here are optional at their local levels. A selected profile may impose stricter presence rules. Optional base structure does not establish authority to collect without a valid mandate where the applicable service requires one.

The global initiation can support individual or bulk, domestic or cross-border use. That broad capability is not permission to submit these demonstration accounts to a real scheme. The receiving bank's service specifies permitted versions, account and party identification, eligibility and usage restrictions. No scheme acceptance or operationally usable routing is demonstrated by the fictional names and proprietary account IDs.

The inspected EPC 2025 SDD Core customer-to-PSP guideline uses pain.008.001.08, rather than this catalogue V12. Its customer reversal and rejection reports also use older versions than the mounted examples. Keep base-schema facts, historical profile requirements and bank-specific rules separate. If implementing SDD Core, use the actual effective profile and addenda; this worked V12 XML is not labelled a SEPA-certified instance.

For current address requirements, the inspected September 2026 EPC notice postpones removal of unstructured addresses beyond 15 November 2026 and leaves the replacement date undetermined. It overrides older 22 November references in the affected guidelines. This message contains no address example to validate against that policy; the point is to check current notices rather than turn a superseded date into a mandate.

The related reversal request does not cancel DEMO-MANDATE-001; amending or cancelling mandate authority is a separate operation. Any return rights, reversal eligibility, refund obligations, time limits and accounting treatment require the actual scheme, account agreement and applicable legal rules. If a customer disputes a collection, operations must identify the relevant procedure rather than turn a generic error-handling path into an assumed right or deadline.

The stored V12 XSD checks its declared grammar and datatype restrictions. It does not compare the control sums with the transaction amount, verify that an account exists, establish signature authenticity, enforce mandate authority or run the bank's screening controls. The supplied namespace-aware field reference is useful for mapping and testing structure; business consistency and runtime controls need their own verified tests.

Explore the complete Payment Life Cycle