pacs.003.001.09 — FI to FI Customer Direct Debit

Field	Value
ISO name	FIToFICustomerDirectDebitV09
Registration status	Registered
Year	2019
Version	9

Overview

The pacs.003 message carries a customer direct debit between banks. It lets the creditor bank collect funds from the debtor bank.

Reviewed 23 March 2026. ISO catalogue date: 2025-02-27.

Key data elements

GrpHdr — Group Header with message identification and settlement information.
DrctDbtTxInf — Direct Debit Transaction Information with amount and parties.
Cdtr — Creditor identification and account details.
CdtrAgt — Creditor Agent (collecting institution) identification.
DbtrAgt — Debtor Agent (paying institution) identification.

Business context

Supports SEPA Core and B2B direct debit schemes.
Used for recurring collections such as subscriptions and bills.
Needs a valid mandate reference.
Can carry many direct debits in one message.

Key data elements and business context
Key data elements	Business context
GrpHdr — Group Header with message identification and settlement information	Supports SEPA Core and B2B direct debit schemes
DrctDbtTxInf — Direct Debit Transaction Information with amount and parties	Used for recurring collections such as subscriptions and bills
Cdtr — Creditor identification and account details	Needs a valid mandate reference
CdtrAgt — Creditor Agent (collecting institution) identification	Can carry many direct debits in one message
DbtrAgt — Debtor Agent (paying institution) identification	The creditor agent sends pacs.003 to the debtor agent. The debtor agent checks the mandate and either settles or returns the transaction.

CBPR+ and scheme context

Structured address and party-data rules also apply here.
Mandate data must be structured from November 2026.
It replaces older MT104-style direct-debit formats in cross-border flows.
Creditor scheme identifiers need closer validation.

Message flow

The creditor agent sends pacs.003 to the debtor agent. The debtor agent checks the mandate and either settles or returns the transaction.

Version commentary

ISO 20022 last updated this business area on 2025-02-27. This site documents pacs.003.001.09. The latest catalogue version is pacs.003.001.11.

Use this page for the version that pacs008 implements today, and review the newer catalogue version for roadmap planning.

Version-diff table

Version history and implementation guidance
Version range	Why it matters	Implementation takeaway
pacs.003.001.09	Current implementation in pacs008	Useful for direct-debit reference modelling in the current project.
pacs.003.001.10-11	Later catalogue revisions	Check later revisions for mandate, status, and interoperability updates before greenfield use.

Scheme-specific notes

This message is outside the SCT and SCT Inst credit-transfer rulebooks, so treat it as a separate direct-debit track.
Use this page as a guide, not as a substitute for scheme rulebooks.

When to use this message

Use pacs.003 for customer direct-debit collection between banks.

When not to use this message

Do not use pacs.003 for institution-own-account debits or customer credit transfers.

Implementation notes

Mandate and debtor-account data usually matter more than the XML.
Scheme timing, cutoffs, and return rights vary, so keep that logic outside the generic message model.
Store collection references separately from invoice references.

Common failure modes

Treating mandate data as optional operational context.
Failing to align debtor account checks with scheme-specific rules.
Ignoring return and reversal flows when designing the original debit pipeline.

Worked XML fragment

<FIToFICstmrDrctDbt>
  <GrpHdr>
    <MsgId>DD-2026-1001MsgId>
  GrpHdr>
  <DrctDbtTxInf>
    <PmtId><EndToEndId>MANDATE-7741EndToEndId>PmtId>
    <IntrBkSttlmAmt Ccy="EUR">250.00IntrBkSttlmAmt>
    <Dbtr><Nm>DBTR PARTY 01Nm>Dbtr>
    <Cdtr><Nm>CDTR PARTY 01Nm>Cdtr>
  DrctDbtTxInf>
FIToFICstmrDrctDbt>

Field commentary

EndToEndId: Keep mandate and collection identifiers separate from invoice references.
IntrBkSttlmAmt: Check amount precision and currency rules before rendering XML.
Dbtr / Cdtr: Direct-debit success often depends more on account and mandate quality than on XML structure.

Decision flow

Need a bank-to-bank customer direct debit?
Yes -> Use pacs.003.
No -> Need a customer credit transfer?
Yes -> Use pacs.008 instead.
No -> Re-check whether the case is really a direct debit.

Implementation FAQ

Is pacs.003 the direct-debit mirror of pacs.008?

No. It handles customer direct-debit flows, which have different mandate, timing, and exception rules.

What matters most operationally?

Mandate quality, debtor-account rules, and return handling matter more than XML generation.

Primary references

Related messages

Message type	Description	Overview
`pacs.004.001.11`	Payment Return	The pacs.004 message returns a payment that has already settled. It sends funds back when a payment cannot be applied.
`pacs.007.001.11`	FI to FI Payment Reversal	The pacs.007 message reverses an earlier payment instruction. Unlike pacs.004, it starts from the original sender.
`pacs.002.001.12`	FI to FI Payment Status Report	The pacs.002 message reports the status of an earlier payment instruction. It tells another institution whether the payment was accepted, rejected, pending, or settled.