SepaData interface is the primary input for generating SEPA XML files. It contains all the information needed to create a valid SEPA credit transfer or direct debit XML document.
Interface Definition
The SEPA pain format version to use.Valid values:
pain.001.001.02- Credit Transfer v02pain.001.003.02- Credit Transfer v02 (alternative)pain.001.001.03- Credit Transfer v03pain.001.003.03- Credit Transfer v03 (alternative)pain.008.001.01- Direct Debit v01pain.008.003.01- Direct Debit v01 (alternative)pain.008.001.02- Direct Debit v02pain.008.003.02- Direct Debit v02 (alternative)
pain.001.001.03The XML version to use in the declaration.Default:
1.0The XML encoding to use in the declaration.Default:
UTF-8The XSI namespace URL for the XML schema instance.Default:
http://www.w3.org/2001/XMLSchema-instanceThe base URL for the ISO 20022 XML schema.Default:
urn:iso:std:iso:20022:tech:xsd:The local instrument code for direct debit transactions.Valid values:
CORE- SEPA Core Direct DebitCOR1- SEPA Core Direct Debit with 1-day lead timeB2B- SEPA Business-to-Business Direct Debit
The sequence type for direct debit transactions.Valid values:
FRST- First direct debit in a seriesRCUR- Recurring direct debitOOFF- One-off direct debitFNAL- Final direct debit in a series
Whether to use batch booking for all payment information blocks.Default:
trueThe unique message identification for the SEPA XML file.Constraints:
- Maximum length: 35 characters
- Must be unique
The date and time when the SEPA XML is created.Will be formatted as ISO 8601 (YYYY-MM-DDThh:mm:ss) in the output XML.
The name of the party initiating the payment.Constraints:
- Minimum length: 1 character
- Maximum length: 70 characters
An array of creditor payment information blocks. Each position represents a group of payments from/to a single creditor/debtor account.See CreditorPayments for the structure of each position.
Example
Related Types
CreditorPayments
Payment information block structure
Payment
Individual payment transaction details
Options
XML generation options