ISO20022

Initiate payments with pain.001 and pain.002

Pain.001 is a Customer to Bank instruction used to initiate a payment. It adheres to the ISO20022 standard and is supported in XML. We support regular credit instructions as well as payments on behalf of (referred to as Dynamic Sender Name solution) payment instructions through pain.001.

This payment instruction format does not support Virtual account (VIBAN) payment processing at this time.

Pain.002 is Customer Payment Status which adheres to the ISO20022 standard. It is the response to pain.001 instruction.

Below you can find more information on which fields are supports and examples of instructions and responses. You will also find an implementation guide.

Link to pain.001 & pain.002 documentation.

Download the full ISO20022 documentation.

Customer Credit Transfer Initiation V03  
pain.001.001.03  
POST /api/v1/payments/iso20022/customer-credit-transfer-initiation  
xml file

Customer Payment Status Report V03  
pain.002.001.03  
xml format

Duplicate check using idempotency key

We have enhanced our duplicate checks by extending all payment initiation endpoints to accept an idempotency key header. The key can prevent the same payment from getting initiated more than once, for example in case of connectivity issues. The idempotency key, provided by you, needs to be unique and maximum 100 characters. The key will be valid for 10 days.

If the idempotency key is more than 100 characters, the endpoint will return a "400 Bad Request".

If the idempotency key is not unique (if the key has been used for the initiation of a previous payment within the past 10 days), the endpoint will return a "409 Conflict" and return the paymentId of the payment, for which the idempotency key was previously used.

This key will not be exposed in any report or endpoint.

Reconcile with camt.053

Camt.053 is a Bank to Customer Statement used for end of day reconciliation. It adheres to the ISO20022 standard and will give an overview of all transactions for a given time period in an XML format.

Below you will find an overview of the fields and parameters BC Connect supports through the endpoint, as well as an implementation guide.

Link to camt.053 documentation.

GET/api/v1/reports/iso20022/bank-to-customer-end-ofday/{TransactionDate}

Bank To Customer Statement V02  
camt.053.001.02  
xml file