pain File Guide
Payment Initiation
The CustomerCreditTransferInitiation message is composed of two building blocks:
- Group Header
The Group Header is mandatory and present once. It contains elements such as MessageIdentification, CreationDateAndTime, Grouping indicator.
- Payment Information
Payment Information is mandatory and repetitive. It contains information including elements related to the debit side of the transaction, such as Debtor or PaymentTypeInformation and CreditTransferTransactionInformation which contains information including elements related to the credit side of the transaction, such as Creditor or RemittanceInformation.
| Customer Credit Transfer Initiation Report | Mandatory information |
|---|---|
| Group Header | Mandatory information, present exactly once in the file |
| ....................................... | |
| Group Header | |
| Payment Information | 1 to multiple Payment Information Blocks per File. Each Payment Information Block contains 1 debtor account and 1 – multiple beneficiary accounts |
| Credit Transfer Transaction Information | |
| ....................................... | |
| Credit Transfer Transaction Information | |
| Payment Information | |
| Payment Information | |
| Credit Transfer Transaction Information | |
| ....................................... | |
| Credit Transfer Transaction Information | |
| Payment Information |
Drawdown Initiation
The ISO 20022 Creditor Payment Activation Request (pain.013) message is sent by the Creditor (sending party) to the Debtor (receiving party), directly or through agents. It is initiated by the sending party to request a movement of funds from the debtor account to a creditor. These specifications are based on the ISO 20022 XML Standards for Creditor Payment Activation Request (available on www.iso.org).
The CustomerCreditTransferInitiation message consists of the following component blocks:
-
Group Header
The Group Header is mandatory and present once. It contains identification of the file and is used to define the set of characteristics shared by all transactions included in the file. -
Payment Information
Payment Information is mandatory and repetitive. It contains a set of characteristics that apply to the debit side of the transaction. -
Supplementary Information
Additional information that cannot be captured in the structured elements, or within the other specific blocks. This block is not mandatory and can be present only once
| Creditor Payment Activation Request Report | Mandatory information |
|---|---|
| Group Header | Mandatory information, present exactly once in the file |
| ....................................... | |
| Group Header | |
| Payment Information | Mandatory information, which can contain multiple blocks. The pain.013 can contain one or more payment information block per file with transaction details of creditors |
| Creditor Payment Activation Request Information | |
| ....................................... | |
| Creditor Payment Activation Request Information | |
| Payment Information | |
| Supplementary Information | |
| ....................................... | |
| Supplementary Information |
pain.002.001.03
The CustomerPaymentStatusReport is composed of three building blocks
-
Group header:
The group header consists of identification of the file as well as information that is common to all the individual transactions in the file. This block is mandatory and present only once. -
Original Group Information and Status:
Original group information block consists of information concerning the group of transactions being reported back. This block is used along with group header to report file status. -
Original Payment Information and Status:
Payment information block consists of information concerning the original underlying payment, to which the status report message refers.
| Customer Payment Status Report | Mandatory information |
|---|---|
| Group Header | Contains only one occurrence & identification of the file including information common to all individual transactions |
| ....................................... | |
| Group Header | |
| Original Group information and Status | Contains only one occurrence & information concerning the group of transactions being reported back |
| ....................................... | |
| Original Group information and Status | |
| Original Payment Information and Status | Contains multiple occurrences depending on the number of payments. |
| ....................................... | |
| Original Payment Information and Status |
Was this page useful?
Give feedback to help us improve developer.gs.com and serve you better.