pain: Payments Initiation
pain.008 Customer Direct Debit Initiation
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
pain.008 is the ISO 20022 CustomerDirectDebitInitiation message in the Payments Initiation business area (pain). The latest version is pain.008.001.11, and 11 versions are in the repository.
- Message
- CustomerDirectDebitInitiation
- Latest version
- pain.008.001.11
- Submitting organisation
- ISTH/Swift
- MT equivalent
- None listed
In use: published in the current ISO 20022 catalogue.
What pain.008 is for
The CustomerDirectDebitInitiation message is sent by the initiating party to the forwarding agent or creditor agent. It is used to request single or bulk collection(s) of funds from one or various debtor's account(s) for a creditor.
The CustomerDirectDebitInitiation message can contain one or more direct debit instructions.
The message can be used in a direct or a relay scenario:
- In a direct scenario, the message is sent directly to the creditor agent. The creditor agent is the account servicer of the creditor.
- In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerDirectDebitInitiation message to the creditor agent.
The message can also be used by an initiating party that has authority to send the message on behalf of the creditor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate.
The CustomerDirectDebitInitiation message can be used in domestic and cross-border scenarios.
The CustomerDirectDebitInitiation may or may not contain mandate related information, i.e. extracts from a mandate, such as MandateIdentification or DateOfSignature. The CustomerDirectDebitInitiation message must not be considered as a mandate.
The CustomerDirectDebitInitiation message must not be used by the creditor agent to execute the direct debit instruction(s). The FIToFICustomerDirectDebit message must be used instead.
pain.008 versions
Every version published in the e-Repository, newest first. A message keeps its business purpose across versions; each new version is a separate schema with its own namespace.
| Version | Registration status | Published in |
|---|---|---|
| pain.008.001.11latest | Registered | Latest version set |
| pain.008.001.10 | Registered | Previous version set |
| pain.008.001.09 | Registered | Archive |
| pain.008.001.08 | Registered | Archive |
| pain.008.001.07 | Registered | Archive |
| pain.008.001.06 | Registered | Archive |
| pain.008.001.05 | Registered | Archive |
| pain.008.001.04 | Registered | Archive |
| pain.008.001.03 | Registered | Archive |
| pain.008.001.02 | Registered | Archive |
| pain.008.001.01 | Registered | Archive |
pain.008 message structure
The building blocks of pain.008.001.11 to three levels, with multiplicity ([0..1] optional, [1..1] mandatory, * any number) and the data type or component. Element names and definitions are from the ISO 20022 repository; usage guidelines such as CBPR+ or a market infrastructure's rules can restrict them further.
Document[1..1]CstmrDrctDbtInitnCustomerDirectDebitInitiation [1..1]GrpHdrGroup Header [1..1]GroupHeader118Set of characteristics shared by all individual transactions included in the message.
MsgIdMessage Identification [1..1]Max35TextPoint to point reference, assigned by the instructing party and sent to the next party in the chain, to unambiguously identify the message.
CreDtTmCreation Date Time [1..1]ISODateTimeDate and time at which the message was created.
AuthstnAuthorisation [0..2]Authorisation1Choice (choice)User identification or any user key that allows to check if the initiating party is allowed to initiate transactions from the account specified in...
CdCode [1..1]Authorisation1CodePrtryProprietary [1..1]Max128Text
NbOfTxsNumber Of Transactions [1..1]Max15NumericTextNumber of individual transactions contained in the message.
CtrlSumControl Sum [0..1]DecimalNumberTotal of all individual amounts included in the message, irrespective of currencies.
InitgPtyInitiating Party [1..1]PartyIdentification272Party that initiates the payment.
NmName [0..1]Max140TextPstlAdrPostal Address [0..1]PostalAddress27IdIdentification [0..1]Party52Choice (choice)CtryOfResCountry Of Residence [0..1]CountryCodeCtctDtlsContact Details [0..1]Contact13
FwdgAgtForwarding Agent [0..1]BranchAndFinancialInstitutionIdentification8Financial institution that receives the instruction from the initiating party and forwards it to the next agent in the payment chain for execution.
FinInstnIdFinancial Institution Identification [1..1]FinancialInstitutionIdentification23BrnchIdBranch Identification [0..1]BranchData5
PmtInfPayment Information [1..*]PaymentInstruction45Set of characteristics that apply to the credit side of the payment transactions included in the direct debit transaction initiation.
PmtInfIdPayment Information Identification [1..1]Max35TextUnique identification, as assigned by a sending party, to unambiguously identify the payment information group within the message.
PmtMtdPayment Method [1..1]PaymentMethod2CodeSpecifies the means of payment that will be used to move the amount of money.
ReqdAdvcTpRequested Advice Type [0..1]AdviceType1Type of advice details requested.
CdtAdvcCredit Advice [0..1]AdviceType1Choice (choice)DbtAdvcDebit Advice [0..1]AdviceType1Choice (choice)
BtchBookgBatch Booking [0..1]BatchBookingIndicatorIdentifies whether a single entry per individual transaction or a batch entry for the sum of the amounts of all transactions within the group of a...
NbOfTxsNumber Of Transactions [0..1]Max15NumericTextNumber of individual transactions contained in the payment information group.
CtrlSumControl Sum [0..1]DecimalNumberTotal of all individual amounts included in the group, irrespective of currencies.
PmtTpInfPayment Type Information [0..1]PaymentTypeInformation29Set of elements used to further specify the type of transaction.
InstrPrtyInstruction Priority [0..1]Priority2CodeSvcLvlService Level [0..*]ServiceLevel8Choice (choice)LclInstrmLocal Instrument [0..1]LocalInstrument2Choice (choice)SeqTpSequence Type [0..1]SequenceType3CodeCtgyPurpCategory Purpose [0..1]CategoryPurpose1Choice (choice)
ReqdColltnDtRequested Collection Date [1..1]ISODateDate and time at which the creditor requests that the amount of money is to be collected from the debtor.
CdtrCreditor [1..1]PartyIdentification272Party to which an amount of money is due.
NmName [0..1]Max140TextPstlAdrPostal Address [0..1]PostalAddress27IdIdentification [0..1]Party52Choice (choice)CtryOfResCountry Of Residence [0..1]CountryCodeCtctDtlsContact Details [0..1]Contact13
CdtrAcctCreditor Account [1..1]CashAccount40Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.
IdIdentification [0..1]AccountIdentification4Choice (choice)TpType [0..1]CashAccountType2Choice (choice)CcyCurrency [0..1]ActiveOrHistoricCurrencyCodeNmName [0..1]Max70TextPrxyProxy [0..1]ProxyAccountIdentification1
CdtrAgtCreditor Agent [1..1]BranchAndFinancialInstitutionIdentification8Financial institution servicing an account for the creditor.
FinInstnIdFinancial Institution Identification [1..1]FinancialInstitutionIdentification23BrnchIdBranch Identification [0..1]BranchData5
CdtrAgtAcctCreditor Agent Account [0..1]CashAccount40Unambiguous identification of the account of the creditor agent at its servicing agent in the payment chain.
IdIdentification [0..1]AccountIdentification4Choice (choice)TpType [0..1]CashAccountType2Choice (choice)CcyCurrency [0..1]ActiveOrHistoricCurrencyCodeNmName [0..1]Max70TextPrxyProxy [0..1]ProxyAccountIdentification1
UltmtCdtrUltimate Creditor [0..1]PartyIdentification272Ultimate party to which an amount of money is due.
NmName [0..1]Max140TextPstlAdrPostal Address [0..1]PostalAddress27IdIdentification [0..1]Party52Choice (choice)CtryOfResCountry Of Residence [0..1]CountryCodeCtctDtlsContact Details [0..1]Contact13
ChrgBrCharge Bearer [0..1]ChargeBearerType1CodeSpecifies which party/parties will bear the charges associated with the processing of the payment transaction.
ChrgsAcctCharges Account [0..1]CashAccount40Account used to process charges associated with a transaction.
IdIdentification [0..1]AccountIdentification4Choice (choice)TpType [0..1]CashAccountType2Choice (choice)CcyCurrency [0..1]ActiveOrHistoricCurrencyCodeNmName [0..1]Max70TextPrxyProxy [0..1]ProxyAccountIdentification1
ChrgsAcctAgtCharges Account Agent [0..1]BranchAndFinancialInstitutionIdentification8Agent that services a charges account.
FinInstnIdFinancial Institution Identification [1..1]FinancialInstitutionIdentification23BrnchIdBranch Identification [0..1]BranchData5
CdtrSchmeIdCreditor Scheme Identification [0..1]PartyIdentification272Credit party that signs the mandate.
NmName [0..1]Max140TextPstlAdrPostal Address [0..1]PostalAddress27IdIdentification [0..1]Party52Choice (choice)CtryOfResCountry Of Residence [0..1]CountryCodeCtctDtlsContact Details [0..1]Contact13
DrctDbtTxInfDirect Debit Transaction Information [1..*]DirectDebitTransactionInformation32Provides information on the individual transaction(s) included in the message.
PmtIdPayment Identification [1..1]PaymentIdentification6PmtTpInfPayment Type Information [0..1]PaymentTypeInformation29InstdAmtInstructed Amount [1..1]ActiveOrHistoricCurrencyAndAmountChrgBrCharge Bearer [0..1]ChargeBearerType1CodeDrctDbtTxDirect Debit Transaction [0..1]DirectDebitTransaction12UltmtCdtrUltimate Creditor [0..1]PartyIdentification272DbtrAgtDebtor Agent [1..1]BranchAndFinancialInstitutionIdentification8DbtrAgtAcctDebtor Agent Account [0..1]CashAccount40DbtrDebtor [1..1]PartyIdentification272DbtrAcctDebtor Account [1..1]CashAccount40UltmtDbtrUltimate Debtor [0..1]PartyIdentification272InstrForCdtrAgtInstruction For Creditor Agent [0..1]Max140TextPurpPurpose [0..1]Purpose2Choice (choice)RgltryRptgRegulatory Reporting [0..10]RegulatoryReporting3TaxTax [0..1]TaxData1RltdRmtInfRelated Remittance Information [0..10]RemittanceLocation8RmtInfRemittance Information [0..1]RemittanceInformation22SplmtryDataSupplementary Data [0..*]SupplementaryData1
SplmtryDataSupplementary Data [0..*]SupplementaryData1Additional information that cannot be captured in the structured elements and/or any other specific block.
PlcAndNmPlace And Name [0..1]Max350TextUnambiguous reference to the location where the supplementary data must be inserted in the message instance.
EnvlpEnvelope [1..1]SupplementaryDataEnvelope1Technical element wrapping the supplementary data.
Have a pain.008 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.
External code sets used in pain.008
These elements take their values from ISO 20022 external code sets, which are published separately and updated every quarter without a new message version.
- ExternalAccountIdentification1Code4 codes
- ExternalCashAccountType1Code28 codes
- ExternalCategoryPurpose1Code49 codes
- ExternalClearingSystemIdentification1Code172 codes
- ExternalCreditorReferenceType1Code7 codes
- ExternalDateType1Code5 codes
- ExternalDocumentAmountType1Code27 codes
- ExternalDocumentLineType1Code19 codes
- ExternalDocumentType1Code23 codes
- ExternalFinancialInstitutionIdentification1Code0 codes
- ExternalGarnishmentType1Code3 codes
- ExternalLocalInstrument1Code114 codes
- ExternalMandateSetupReason1Code0 codes
- ExternalOrganisationIdentification1Code15 codes
- ExternalPersonIdentification1Code11 codes
- ExternalProxyAccountType1Code22 codes
- ExternalPurpose1Code366 codes
- ExternalServiceLevel1Code29 codes
pain.008 questions
- What is the latest version of pain.008?
- The latest version in the ISO 20022 e-Repository release of 24 April 2025 is pain.008.001.11.
- What is the root element of pain.008?
- The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:pain.008.001.11, and its message element is CstmrDrctDbtInitn (CustomerDirectDebitInitiation).
- Is there an MT equivalent of pain.008?
- No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.
All ISO 20022 messages · ISO 20022 code sets · MT messages
The ISO 20022 message definitions, element names and definitions on this page are reproduced from material published at iso20022.org under the ISO 20022 Intellectual Property Rights policy. This is not the official source: the up-to-date ISO 20022 standards and repository material are published only at iso20022.org. Explanations in our own words are by ZagTrader. ZagTrader is not affiliated with or endorsed by ISO or Swift.