What is pacs.008?
The CBPR+ successor
to MT103.
A pacs.008 is an ISO 20022 message used by one financial institution to instruct another to make a customer credit transfer. Its XML structure carries payment parties, settlement information and the transaction’s UETR.
- One customer payment: debtor, creditor, amount, currency and remittance information.
- Structured XML: named elements replace the numbered fields familiar from an MT103.
- One reference: find the UETR inside the payment identification block.
What is a pacs.008?
A pacs.008 carries a customer credit transfer between financial institutions. It provides a structured record of the payment instruction, including the debtor, creditor, amount, currency and payment references. A copy of the instruction is different from confirmation that funds arrived.
pacs.008 at a glance
- MESSAGE TYPE
- pacs.008
- FULL NAME
- FIToFICustomerCreditTransfer
- STANDARD
- ISO 20022 · XML
- UETR LOCATION
- CdtTrfTxInf · PmtId · UETR
What does pacs.008 stand for?
pacs refers to Payments Clearing and Settlement, the ISO 20022 business area for payment messages exchanged between financial institutions. 008 identifies this particular customer credit transfer message.
The full name is FIToFICustomerCreditTransfer. In a complete identifier such as pacs.008.001.08, the final components identify the variant and version. Always check the version and usage guidelines required by the relevant payment scheme.
Related business areas include pain, Payments Initiation, and camt, Cash Management. These cover other parts of the payment journey, including initiation, reporting and investigation.
What does a pacs.008 look like? The format, element by element
The Group Header describes the message; the Credit Transfer Transaction Information block describes the payment. Select a line below to explore its purpose.
⌕ Interactive pacs.008 Element Explorer
The UETR sits inside PmtId, within CdtTrfTxInf.
<Document> </GrpHdr> </PmtId> </CdtTrfTxInf>
</FIToFICstmrCdtTrf>
</Document>UETR, the tracking reference
The 36-character reference connecting this payment across its journey. It is carried inside CdtTrfTxInf → PmtId → UETR.
Illustrative, abbreviated XML only. This example is not a complete, schema-valid payment instruction and does not represent a live transfer.
A message, two main blocks
Message ID · creation time · transaction count · settlement information
Payment identification · amount · date · parties · charges · remittance
PmtId → UETR → 3f2a91c7-5b4e-4d18-9c6f-2ae70b8d1f43Where is the UETR in a pacs.008?
Look inside CdtTrfTxInf → PmtId → UETR. The UETR is a 36-character UUID with five groups separated by hyphens. The same reference can appear in MT103 field 121. Understand the 36-character UETR reference before using it to find a transaction.
<PmtId> <InstrId>BANK-REF-001</InstrId> <EndToEndId>INVOICE-2026-001</EndToEndId> <UETR>3f2a91c7-5b4e-4d18-9c6f-2ae70b8d1f43</UETR> </PmtId>
Do not substitute InstrId or EndToEndId when a tracker requests the UETR. They serve different identification and reconciliation purposes. Ask the issuing bank for the original reference if you cannot locate it.
pacs.008 vs MT103: what actually changed
The payment reference connects the record even when the message structure changes.
| Aspect | MT103 · FIN | pacs.008 · XML |
|---|---|---|
| Syntax | Numbered fields in text blocks | Named XML elements |
| Party data | Field-based names, accounts and addresses | Separate party and account elements |
| UETR | Field 121 in Block 3 | PmtId → UETR |
| Remittance | Field 70 | RmtInf |
| Charges | 71A · OUR / BEN / SHA | ChrgBr · DEBT / CRED / SHAR |
The MT103 to pacs.008 field mapping
A practical orientation to familiar fields. Scheme-specific translation rules determine the complete mapping.
| MT103 field | pacs.008 element | Worth knowing |
|---|---|---|
| 20 · Sender’s reference | PmtId → InstrId | A point-to-point instruction reference. |
| 32A · Date / currency / amount | IntrBkSttlmDt + IntrBkSttlmAmt | Separate date and amount elements; currency is an attribute. |
| 33B · Instructed amount | InstdAmt | The amount originally instructed by the customer. |
| 50a · Ordering customer | Dbtr + DbtrAcct | Debtor identification and account details. |
| 52a · Ordering institution | DbtrAgt | The debtor’s financial institution. |
| 57a · Account with institution | CdtrAgt | The institution servicing the beneficiary. |
| 59a · Beneficiary | Cdtr + CdtrAcct | Creditor identification and account details. |
| 70 · Remittance information | RmtInf | Structured or unstructured reconciliation information. |
| 71A · Details of charges | ChrgBr | OUR → DEBT; BEN → CRED; SHA → SHAR. |
| 121 · UETR in Block 3 | PmtId → UETR | The same transaction reference is retained. |
MT103 → pacs.008
{3:{121:3f2a91c7-5b4e-4d18-9c6f-2ae70b8d1f43}}<UETR>3f2a91c7-5b4e-4d18-9c6f-2ae70b8d1f43</UETR>pacs.008 vs pacs.009, pacs.004 and pacs.002
Related messages perform different jobs: instructing payments, moving cover funding, reporting status, returning funds and requesting cancellation.
| Message | Full name | Related legacy role | Purpose |
|---|---|---|---|
| pacs.008 | FIToFICustomerCreditTransfer | MT103 | Customer payment instruction between financial institutions. |
| pacs.009 | FinancialInstitutionCreditTransfer | MT202 | Institution-to-institution transfer; the COV variant supports cover funding. |
| pacs.004 | PaymentReturn | Payment return | Returns funds with references to the original payment. |
| pacs.002 | FIToFIPaymentStatusReport | Status reporting | Reports the status of a payment instruction. |
| camt.056 | FIToFIPaymentCancellationRequest | MT192 | Requests cancellation; a request does not guarantee a recall. |
A status report and a payment instruction are separate messages. A cancellation request also differs from a completed return of funds.
How to track a pacs.008 transfer
You do not need to read every XML element. Start with the original transaction reference and follow our guide to tracking a transaction by UETR.
Get the payment confirmation
Ask the sending bank for its payment confirmation. If you are the recipient, ask the sender for the original document.
Find the UETR on it
Look for the 36-character reference in PmtId → UETR, or field 121 on an MT103-format confirmation.
Enter the UETR on UETR.io
Use the UETR, message date and your email to find a registered transaction. Amount and currency come from the saved record.
Read the recorded timeline
Follow recorded events and confirm your email for updates. UETR.io does not query the live SWIFT gpi network; confirm financial outcomes with your bank.
Is a pacs.008 proof of payment?
A payment instruction describes what a bank has been asked to process. Its existence alone does not establish that the beneficiary received funds. A document can contain a valid-looking reference without independently proving submission or settlement.
Obtain the bank-issued confirmation through official channels and ask the responsible bank about the actual financial outcome. UETR.io displays information registered with its transaction system; recorded events are not an independent confirmation of bank settlement.