GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
PAYMENTSSIGNAL

The interactive academy for the standards, messages, and rails that move money.

PROGRESS
pain.008ISO 20022

pain.008 — Customer Direct Debit Initiation

Carries a creditor's customer-to-bank request to collect one or more direct debits under referenced mandates. It initiates a collection; it does not itself debit the debtor or prove interbank settlement.

DIRECTION: Sent by a creditor or initiating party to the creditor agent under a bank, scheme, or implementation-profile agreement.

Version + profile: pain.008 is a message-family identifier, not a complete version. The numeric .001.xx definition and field rules depend on the scheme, service, usage guideline, and implementation version named in each context; sample namespaces show only the illustrated version.

Contributor Shubham Mathure

DOMAIN + EDITORIAL AUDITAudited 2026-07-18 for payment logic, source scope, technical writing, and Payments Signal voice — see the method.

EVIDENCE AT ARM'S REACH

IMPLEMENTATION RESOURCES

Start with the exact message version, then apply the scheme or network profile that governs your implementation.

An XSD checks XML structure. A usage guideline adds profile rules, conditional fields, code restrictions, and business controls. XSD-valid does not mean scheme-compliant.

XSD + definitionBase ISO 20022current

ISO 20022 message definitions and XSDs

Choose the exact message definition in the official catalogue. The base XSD checks XML structure; it does not prove compliance with a scheme profile.

Owner
ISO 20022 Registration Authority
Checked
2026-07-12
Access
Official page · Public official catalogue; select the required message version before downloading.
OPEN OFFICIAL SOURCE
RulebookSEPA SDD Corecurrent

SEPA Direct Debit Core rulebook

The controlling scheme rules for mandates, collections, R-transactions, timelines, and consumer refund rights.

Owner
European Payments Council
Version
2025 version 1.1 (EPC016-06)
Checked
2026-07-13
Access
Official page · Public EPC document page; use the version effective for the collection date.
OPEN OFFICIAL SOURCE
Usage guidelineSEPA SDD Corecurrent

SEPA Direct Debit Core implementation guidelines and XSDs

Customer-to-PSP and Inter-PSP SDD Core profiles. EPC XSD technical validation subsets express guideline restrictions but are not production artefacts or proof of complete scheme compliance.

Owner
European Payments Council
Version
2025 version 1.0
Checked
2026-07-19
Access
Official page · Public EPC scheme page with owner-hosted guideline and XSD downloads.
OPEN OFFICIAL SOURCE
RulebookSEPA SDD B2Bcurrent

SEPA Direct Debit B2B rulebook

The business-to-business mandate, debtor-bank checking, collection, exception, and refund-right rules.

Owner
European Payments Council
Version
2025 version 1.1 (EPC222-07)
Checked
2026-07-13
Access
Public download · Public owner-hosted EPC PDF; confirm the effective version before implementation.
DOWNLOAD FROM OWNER
Usage guidelineSEPA SDD B2Bcurrent

SEPA Direct Debit B2B implementation guidelines and XSDs

Customer-to-PSP, Inter-PSP, and e-mandate profiles. EPC XSD technical validation subsets express guideline restrictions but are not production artefacts or proof of complete scheme compliance.

Owner
European Payments Council
Version
2025 version 1.0
Checked
2026-07-19
Access
Official page · Public EPC scheme page with owner-hosted guideline and XSD downloads.
OPEN OFFICIAL SOURCE
Teaching sampleScheme-neutral teachingcurrent

pain.008 customer direct-debit initiation — raw XML

A fictional SDD Core customer collection carrying one mandate reference. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.

Owner
Payments Signal
Version
pain.008.001.08
Checked
2026-07-19
Integrity
crc32:73a7fbd5
Access
Payments Signal download · Original fictional teaching sample; no login required.
DOWNLOAD
Field matrixBase ISO 20022current

pain.008 field matrix

Curated field requirements, contexts, operational meaning, and implementation cautions.

Owner
Payments Signal
Checked
2026-07-19
Integrity
crc32:e90cab41
Access
Payments Signal download · Original, source-backed teaching asset; no login required.
DOWNLOAD
Profile packSEPA SDD Corecurrent

SEPA direct-debit implementation pack

Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.

Owner
Payments Signal
Checked
2026-07-19
Integrity
crc32:458732a2
Access
Payments Signal download · Original generated teaching pack; no login required.
DOWNLOAD

WHO IS INVOLVED

  • Creditor / initiating partySupplies the collection, mandate reference, due date, debtor details and creditor identifiers.
  • Creditor agentValidates the customer file, applies controls and creates the applicable inter-PSP collection message such as pacs.003.

KEY FIELDS

Curated teaching subset. Exact mandatory fields, sequence types, lead times and mandate rules come from the bank and scheme implementation profile, not from the base ISO message alone.

Key fields of pain.008
FIELDNAMEPRESENCEWHAT IT MEANS
GrpHdr/MsgIdMessage identificationMANDATORYBase ISO 20022 pain.008 message definitionUnique identifier for the customer initiation message.
PmtInf/PmtInfIdPayment information identificationMANDATORYBase ISO 20022 pain.008 message definitionIdentifies a block of collections sharing service and creditor-side data.
PmtInf/ReqdColltnDtRequested collection dateMANDATORYBase ISO 20022 pain.008 message definitionDate on which the creditor asks for the debtor account to be debited.
PmtInf/CdtrSchmeIdCreditor scheme identificationCONDITIONALRequired where the scheme or bank profile uses a creditor identifierIdentifies the creditor within the direct-debit scheme.
DrctDbtTxInf/PmtId/EndToEndIdEnd-to-end identificationMANDATORYBase ISO 20022 pain.008 transactionCreditor reference used to reconcile the collection through its lifecycle.
DrctDbtTxInf/InstdAmtInstructed amountMANDATORYBase ISO 20022 pain.008 transactionAmount and currency the creditor asks to collect.
DrctDbtTxInf/DrctDbtTx/MndtRltdInf/MndtIdMandate identificationMANDATORYDirect-debit profile using mandate-related informationReference linking the collection to the debtor's mandate.
DrctDbtTxInf/DbtrAcct/IdDebtor accountMANDATORYBase ISO 20022 pain.008 transactionAccount from which the collection is requested.

FIELD BY FIELD — FULL STRUCTURE

The whole pain.008 laid out as a parent-child tree: every field in its nesting, with a sample value and what it means. Expand a branch to drill in. Values are fictional (SYNTHETIC / TRAINING ONLY); this is a curated practitioner view, not the full schema.

  • Document—The root of an ISO 20022 message — the business payload, which a Business Application Header (head.001) accompanies as a separate document.
    • CstmrDrctDbtInitn—
      • GrpHdr—Group header — data that applies to the whole message: its identity, when it was created, how many transactions it carries, and shared settlement data.
        • MsgIdDEMO-PAIN008-001MandatoryUnique identifier for the customer initiation message.
          Use case
          Quoted when a status report or return refers back to this whole message; changes at every interbank hop.
          Example
          DEMO-PACS008-001
        • CreDtTm2026-07-18T08:00:00ZMandatoryCreation date and time — when this message was created (a UTC timestamp), separate from when the payment is executed.
          Use case
          A processing timestamp for the message — distinct from the requested execution or settlement date.
          Example
          2026-07-12T09:01:00Z
        • NbOfTxs1Number of transactions the message carries — a control total the receiver checks against the transactions it finds.
          Use case
          The receiver counts the transactions it parsed and rejects the whole message if the tally disagrees.
          Example
          <NbOfTxs>2</NbOfTxs>
        • CtrlSum480.00Control sum — the total of all instructed amounts, a second control the receiver reconciles.
          Use case
          A second integrity check alongside NbOfTxs — the summed amounts must equal this figure.
          Example
          <CtrlSum>2500.00</CtrlSum>
        • InitgPty—Initiating Party — who created the instruction (often the debtor, or a party acting for them).
          • NmAsha TradersName — the free-text name of a party.
            Use case
            The name screening and verification-of-payee compare against; quality here directly affects whether a payment clears.
            Example
            <Nm>Demo Trading Ltd</Nm>
            Watch out
            A creditor name that doesn't match the account holder can trigger a name-check warning or return.
      • PmtInf—Payment Information — a batch of one or more payments in a pain.001 that share a debtor, a debit account, and an execution date.
        • PmtInfIdDEMO-SDD-CORE-001MandatoryIdentifies a block of collections sharing service and creditor-side data.
          Use case
          The handle a corporate uses to reconcile a batch's status report back to the file it sent.
          Example
          DEMO-BATCH-001
        • PmtMtdDDPayment method — TRF for a credit transfer (the everyday value), TRA, or CHK.
          Use case
          Set to TRF for essentially every credit transfer; the other values cover cheques and transfer-advice.
          Example
          <PmtMtd>TRF</PmtMtd>
        • NbOfTxs1Number of transactions the message carries — a control total the receiver checks against the transactions it finds.
          Use case
          The receiver counts the transactions it parsed and rejects the whole message if the tally disagrees.
          Example
          <NbOfTxs>2</NbOfTxs>
        • CtrlSum480.00Control sum — the total of all instructed amounts, a second control the receiver reconciles.
          Use case
          A second integrity check alongside NbOfTxs — the summed amounts must equal this figure.
          Example
          <CtrlSum>2500.00</CtrlSum>
        • PmtTpInf—Payment Type Information — how the payment should be handled: its service level, local instrument, category purpose, and priority.
          • SvcLvlchoice—Service Level — the rulebook or agreed service under which the payment runs (e.g. a SEPA scheme).
            • CdSEPAService-level code — the 4-letter code naming the scheme/service (e.g. SEPA).
              Use case
              Set SEPA for a euro retail payment; SDVA to ask for same-day value.
              Example
              SEPA
              Codes
              see codes →
          • LclInstrmchoice—Local Instrument — a further, community- or scheme-specific qualifier of how the payment is cleared (e.g. an instant variant).
            • CdCORELocal-instrument code — the 4-letter code for the clearing variant (e.g. INST).
              Use case
              INST with service level SEPA marks a SEPA Instant payment.
              Example
              INST
              Codes
              see codes →
          • SeqTpRCURSequence Type — identifies the collection's place in the mandate sequence, such as one-off or recurring, under the applicable scheme profile.
        • ReqdColltnDt2026-07-21MandatoryDate on which the creditor asks for the debtor account to be debited.
        • CdtrSchmeId—ConditionalIdentifies the creditor within the direct-debit scheme.
          • Idchoice—Identification — a party or account identifier; for a party this is a choice of organisation id or private id.
            • PrvtId—Private Identification — identifies a party that is a private individual (e.g. date/place of birth or a scheme id).
              • Othr—Other — an identifier that does not fit the named types, given as a scheme-plus-value pair.
                • IdchoiceDEMO-CREDITOR-001Identification — a party or account identifier; for a party this is a choice of organisation id or private id.
        • Cdtr—MandatoryCreditor — the party being paid: the beneficiary.
          • NmAsha TradersName — the free-text name of a party.
            Use case
            The name screening and verification-of-payee compare against; quality here directly affects whether a payment clears.
            Example
            <Nm>Demo Trading Ltd</Nm>
            Watch out
            A creditor name that doesn't match the account holder can trigger a name-check warning or return.
        • CdtrAcct—Creditor Account — the account to credit; in SEPA the beneficiary's IBAN.
          • Idchoice—Identification — a party or account identifier; for a party this is a choice of organisation id or private id.
            • IBANDE02120300000000202051International Bank Account Number — the standardised account identifier used across SEPA and beyond.
              Use case
              Encodes country, bank, and account with a checksum, so a typo usually fails validation before it leaves.
              Example
              DE02120300000000202051
        • CdtrAgt—Creditor Agent — the creditor's bank, which credits the beneficiary at the end of the chain.
          • FinInstnId—Financial Institution Identification — how a bank is identified, usually by its BIC.
            • BICFIDEMODEFFXXXBusiness Identifier Code (financial institution) — the 8- or 11-character BIC naming a bank.
              Use case
              The primary way a bank is identified across the chain; 8 characters for the institution, 11 to name a branch.
              Example
              DEMODEFFXXX
        • DrctDbtTxInf—
          • PmtId—Payment Identification — the set of references that identify this payment along the chain.
            • EndToEndIdDEMO-SDD-E2E-001MandatoryCreditor reference used to reconcile the collection through its lifecycle.
              Use case
              The reference the beneficiary matches to an invoice and ops teams use to correlate status reports and returns.
              Example
              DEMO-E2E-001
              Watch out
              Filling it with 'NOTPROVIDED' wastes the single best reconciliation field in the chain.
          • InstdAmt480.00Ccy=EURMandatoryAmount and currency the creditor asks to collect.
            Use case
            What the customer asked to pay; compare it against the interbank settlement amount to see what charges or FX did to the figure.
            Example
            <InstdAmt Ccy="EUR">1250.00</InstdAmt>
          • DrctDbtTx—
            • MndtRltdInf—
              • MndtIdDEMO-MANDATE-001MandatoryReference linking the collection to the debtor's mandate.
              • DtOfSgntr2026-01-10Date of Signature — the date recorded for the debtor's signing of the mandate.
          • DbtrAgt—Debtor Agent — the debtor's bank, the one being instructed.
            • FinInstnId—Financial Institution Identification — how a bank is identified, usually by its BIC.
              • BICFIDEMOGB2LXXXBusiness Identifier Code (financial institution) — the 8- or 11-character BIC naming a bank.
                Use case
                The primary way a bank is identified across the chain; 8 characters for the institution, 11 to name a branch.
                Example
                DEMODEFFXXX
          • Dbtr—MandatoryDebtor — the party whose account is debited: the payer.
            • NmRiya ExampleName — the free-text name of a party.
              Use case
              The name screening and verification-of-payee compare against; quality here directly affects whether a payment clears.
              Example
              <Nm>Demo Trading Ltd</Nm>
              Watch out
              A creditor name that doesn't match the account holder can trigger a name-check warning or return.
          • DbtrAcct—Debtor Account — the account to debit; in SEPA an IBAN.
            • Idchoice—MandatoryAccount from which the collection is requested.
              • IBANGB33BUKB20201555555555International Bank Account Number — the standardised account identifier used across SEPA and beyond.
                Use case
                Encodes country, bank, and account with a checksum, so a typo usually fails validation before it leaves.
                Example
                DE02120300000000202051
          • RmtInf—Remittance Information — what the payment is for, so the creditor can reconcile it; either unstructured free text or structured references.
            • UstrdDEMO INVOICE 480Unstructured — free-text remittance information (e.g. an invoice note); readable but not machine-parseable.
              Use case
              Fine for a human-read note; SEPA allows one occurrence of up to 140 characters.
              Example
              <Ustrd>DEMO INVOICE 1001</Ustrd>
              Watch out
              This text is screened — careless free text ('payment for Iran project') creates sanctions alerts that stop clean payments.
Sources for the field structure4
  1. Official requirement

    ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pain/pacs/camt message-definition elements

    Defines the current versions of all ISO 20022 message definitions, including the pain, pacs, and camt messages taught on this site. · Checked 2026-07-12

    Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.

  2. Official requirement

    Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · cross-border agent chain and structured-data usage

    Defines how ISO 20022 messages (including pacs.008, pacs.009, pacs.002, pacs.004, and camt investigation messages) are used and validated for cross-border payments on the Swift network. · Checked 2026-07-18

    Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.

  3. Official requirement

    Swift Standards MT (annual standards releases) ↗ — Swift · FIN block structure

    Defines the MT message standards (including MT101, MT103, MT202/202 COV, and the MT9xx statement messages) exchanged over the Swift FIN network, maintained through annual standards releases. · Checked 2026-07-18

    Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login. Coexistence for in-scope FI-to-FI payment instructions ended on 22 November 2025, but treatment differs by MT: some instructions are NAKed and selected messages can enter temporary, chargeable contingency conversion. Reporting, initiation, investigations and correspondence follow separate roadmaps.

  4. Simplified educational illustration

    Payments Signal editorial teaching models — Payments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    What this simplifies: One-line plain-language descriptions of the commonly-populated elements — a practitioner view, not the authoritative ISO 20022 / MT schema, which defines many more optional elements.

    Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.

COMMON ERRORS

  • Treating a mandate reference as proof that every scheme condition is satisfied.Consequence: A collection is rejected, returned, refunded or disputed despite being syntactically valid.Avoid it: Validate the mandate lifecycle, sequence, creditor identifier, dates and scheme rules before submission.
  • Resubmitting an uncertain collection with reused or ambiguous references.Consequence: The debtor may be charged twice and the duplicate is difficult to identify.Avoid it: Resolve the original status and apply controlled duplicate checks before any new submission.

USAGE CONTEXTS

  • SEPA Direct DebitThe EPC customer-to-PSP implementation guidelines constrain pain.008 for SDD Core and B2B collections.
  • Bank-specific direct debit serviceA bank may use a different pain.008 version or profile; its contract defines acceptance and status reporting.
OPEN ANNOTATED SAMPLE

SEE IT IN A PLAYABLE FLOW

LEARN THE CONTEXT

Sources for this reference3
  1. Official requirement

    ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pain.008 CustomerDirectDebitInitiation message definition

    Defines the current versions of all ISO 20022 message definitions, including the pain, pacs, and camt messages taught on this site. · Checked 2026-07-12

    Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.

  2. Scheme-specific rule2025 v1.1 (EPC016-06)

    2025 SEPA Direct Debit Core rulebook version 1.1 (EPC016-06) ↗ — European Payments Council · SDD Core customer-to-PSP collection initiation and mandate process

    Rules of the SEPA Direct Debit Core scheme: mandates, collection lifecycle, timelines, R-transactions, and refund rights. · Effective 2025-10-05 · Checked 2026-07-13

  3. Simplified educational illustration

    Payments Signal editorial teaching models — Payments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    What this simplifies: One collection and a compact field subset; bank-specific profile details are omitted.

    Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.

COMMUNITY SIGNAL

Discuss this learning page

Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.

NEXT QUESTION REVIEWMonday, 27 Jul, 8:00 amMonday answer runs use source-supported educational material. Some questions may need owner review.
WHAT ARE YOU SHARING?

Publish only lawful, relevant content. Never include confidential payment or personal data.

Public discussion

LOADING

Loading the discussion…