pain.001.001.13 CustomerCreditTransferInitiationV13

ISO 20022 pain Messages

Ask a bank to make one or more payments from the debtor’s account to creditors.

Cedar Books Ltd asks Fictional Cedar Bank to transfer EUR 125.00 to Example Services Ltd at Fictional Services Bank for the one-time setup invoice INV-DEMO-101. The message was created on 5 January 2026 and requests execution on 6 January 2026. Its one payment group and one transaction use separate message, batch, instruction and end-to-end identities. Both stored control sums equal 125.00. The remittance narrative supports supplier matching after a credit is actually observed. No status or settlement message is included in this XML; the story establishes an instruction, not completed beneficiary payment.

Retain the message’s customer credit-transfer initiation role: single or bulk, domestic or cross-border, internal book transfer, and schema-supported electronic or cheque possibilities are subject to the selected service. This TRF example does not demonstrate every method or optional structure. Use the version-specific Message Definition Report for business meaning and the receiving service’s guideline for its permitted usage.

Local presence rules are not universal business requirements. For example, InstrId is 0..1 inside included PaymentIdentification6, while EndToEndId is 1..1 there. DbtrAcct is required in PaymentInstruction51, but its Id child is 0..1 in CashAccount40; an Othr/Id is required only if that optional Id and the Othr choice are selected. A bank may require account identification under its contract. Read the optional ancestors and choices in Fields and XPath before calling a nested value mandatory.

The ISO catalogue includes pain.001.001.13, but catalogue publication does not make it the required SEPA version. The inspected 2025 EPC SCT customer-to-PSP guideline uses pain.001.001.09 and pain.002.001.10. Its profile restrictions cannot be imported as V13 base cardinalities, and this worked example is not SEPA-certified.

Current-date caveat, checked 11 October 2026: September 2026 EPC notices postponed the earlier unstructured-address removal dates, with a replacement date undetermined. Swift’s September 2026 CBPR+ roadmap warns that SR2026 postponement can make displayed dates inaccurate. No old November deadline or authenticated Swift mandatory-field rule is taught here; select the current service publications before implementation.

pain.001 is not a settlement confirmation, beneficiary statement, automatic refund or customer-payment reversal. A pre-execution cancellation request and a post-execution exception require the applicable message/service process. In particular, this lesson’s pain.007 example concerns a settled direct-debit reversal, not a generic cancellation of this credit transfer.

Namespace-aware XPath is useful for assertions and mappings, but a matching field path proves only selection in the tested XML. Preserve semantic source-to-target mappings and distinguish base schema, external vocabulary, scheme/usage rules and illustrative bank architecture. No API, MQ, Kafka, database layout or payment-hub implementation is required by this lesson.

Explore the complete Payment Life Cycle