XML message for Payment Initiation Implementation Guideline

Pain001

Version 1.0

1

Version history Version 1.0

Changes First version

Date 21.09.2015

2

Table of Contents 1.

Introduction ............................................................................................................................................................................................................................................ 4

2.

Character set ......................................................................................................................................................................................................................................... 4

3.

XML escape characters ........................................................................................................................................................................................................................ 4

4.

Message content of the Customer Credit Transfer ............................................................................................................................................................................... 5

5.

Examples ............................................................................................................................................................................................................................................. 15

3

1. Introduction The purpose of this document is to provide guidance on the use of XML Customer Credit Transfer Initiation message ISO20022 XML – pain.001.001.03 sent to Danske Bank Estonia. Document covers Estonian and EU payments (SEPA payments) as well as other payments. This document is based on the Estonian implementation guidelines for Payment Standards for Customer to Bank, which can be found on the Estonian Banking Association webpage: http://www.pangaliit.ee/en/settlements-and-standards/xml-b2c-c2b-messages. Only Danske Bank specific rules are shown herein. This document should be read together with the ISO 20022 XML message standards, as the ISO rules on the usage of the elements have not been repeated in this document and should be taken into account where applicable.

2. Character set The UTF8 encoding must be used and declared in the XML header. The following characters must be used: Latin letters: a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Numbers: 0 1 2 3 4 5 6 7 8 9 Whitelisted characters: + - ( ) . , / space. Local characters õ ä ö ü Õ Ä Ö Ü which however are replaced with o a o u O A O U respectively when payment is transmitted outside Estonia. If Danske Bank forwards a foreign currency payment to a beneficiary’s bank or an intermediary bank via the SWIFT network, the non-permitted SWIFT characters will be replaced. References, identifications and identifiers must respect the following:  Content is restricted to the Latin character set as defined above  Content must not start or end with a ‘/’  Content must not contain ‘//’s

3. XML escape characters & must be replaced as & " must be replaced as " ' must be replaced as ' < must be replaced as < > must be replaced as >

4

4. Message content of the Customer Credit Transfer The message consists of two mandatory building blocks: Group Header and Payment Information. Group Header: This block is presented only once and it contains elements such as Message Identification, Creation Date and Time and Initiating Party. Payment Information: This block is repetitive and it contains elements related to the debit side of the transaction, such as Debtor, Debtor Account, Payment Type Information and Requested Execution Date and also one or several Credit Transfer Transaction Information parts which contain elements related to the credit side of the transaction, such as Creditor, Creditor Agent and Remittance Information. The message is described in the following table. Below is the explanation of each column of the table. “Index” column – number refers to the corresponding description in the ISO 20022 XML Message Definition Report. This report can be found at www.iso20022.org under “Catalogue of ISO 20022 messages” with “pain.001.001.03” as reference. “Mult” column – indicates whether an element is mandatory or optional and how many repetitions are allowed for the element. For example:  [1..1] – shows that element is mandatory and can be presented only once  [1..n] – shows that element is mandatory and can be presented 1 to unlimited number of times  [0..1] – shows that element is optional and can be presented only once  [0..n] – shows that element is optional and can be presented 0 to unlimited number of times  {Or…Or} – indicates that only one of several elements may be presented “Message Element” column – element name used in ISO 20022 XML Message Definition Report. “XML Tag” column – short name identifying an element within an XML message, which is put between brackets, e.g. “Danske Bank rules” column – includes Danske Bank specific rules for Estonian and EU payments (rules resulting from SEPA) as well as other payments. Payment type indentifying data may be present at either "Payment Information" or "Credit Transfer Transaction Information" level. It is recommended to be used only at "Payment Information" level and not at "Credit Transfer Transaction Information" level. Therefore if "Payment Type Information" is present at both "Payment Information" level and "Credit Transfer Transaction Information" level, then values given at "Payment Information" level are used. Only the "Local Instrument" values are used for payment type determination. If the customer gives extra information which cannot be utilised or forwarded in the payment chain, the information is not processed or it is cut off. The extra information does not cause the rejection of the payment unless it is checked (as, for example, too long "Remittance Information"). Message Root Index Mult. [1..1]

Group Header Index Mult. 1.0

[1..1]

Message Element



Customer Credit Transfer Initiation



Message Element



+ Group Header



Danske Bank Rules

Danske Bank Rules

5

1.1 1.2

[1..1] [1..1]

++ Message Identification ++ Creation Date Time

1.6

[1..1]

++ Number Of Transaction

1.7

[0..1]

++ Control Sum

1.8 1.8 1.8

[1..1] [0..1] [0..1]

1.8

{Or

1.8 1.8 1.8 1.8 1.8 1.8

{{Or Or}} [1..1] [0..1] [1..1] Or}

1.8

{Or

1.8 1.8 1.8 1.8 1.8 1.8 1.8

[1..1] [1..1] [1..1] Or} [1..1] [0..1] [1..1]

++ Initiating Party +++ Name +++ Identification ++++ Organisation Identification +++++ BIC or BEI +++++ Other ++++++ Identification ++++++ Scheme Name +++++++ Code ++++ Private Identification +++++ Date And Place Of Birth ++++++ Birth Date ++++++ City Of Birth ++++++ Country Of Birth +++++ Other ++++++Identification ++++++ Scheme Name +++++++ Code

Payment Information Index Mult. Message Element 2.0

[1..n]

2.1

[1..1]

2.2

[1..1]

+ Payment Information ++ Payment Information Identification ++ Payment Method

2.3

[0..1]

++ Batch Booking



May not contain whitelisted special characters Date and time at which the message was created by the initiating party. The given value will be checked with the total number of transactions in the entire message. In case of mismatch the file will not be accepted. If given, the value will be checked with the total amount of all individual transactions in the entire message. In case of mismatch the file will not be accepted. Accepted but not processed. Limited to 70 characters in length





Danske Bank Rules



Recommended to be unique. May not contain special characters



Accepted code: TRF. In case of other codes the file will not be accepted. Default value is ”false”. If batch booking is not used or false, then all payments will be debited separately. For the Consolidated Payment functionality value “true” should be used:  all payments in payment information block must be with transaction currency EUR  all beneficiaries must locate in Estonia  "Local Instrument" values other than NORM are ignored In case of other currencies or beneficiaries outside Estonia the file will not be accepted. Internet Bank user must have respective teleservices rights to import contsolidated payments. 6

2.4

[0..1]

++ Number of Transactions

2.5

[0..1]

++ Control Sum

2.6

[0..1]

++ Payment Type Information

2.7 2.8

[0..1] [0..1]

+++ Instruction Priority +++ Service Level

2.9

[1..1]

++++ Code

2.11 2.12

[0..1] {Or

+++ Local Instrument ++++ Code

2.13

Or}

++++ Proprietary

2.14

[0..1]

+++ Category Purpose

2.15

[1..1]

++++ Code

2.17 2.19

[1..1] [1..1]

++ Requested Execution Date ++ Debtor

2.19

[1..1]

+++ Name

2.19

[0..1]

+++ Postal Address

2.19

[0..1]

++++ Country







2.19

[0..2]

++++ Address Line

2.19

[0..1]

+++ Identification



The given value will be checked with the total number of transactions in the "Payment Information" level. In case of mismatch the file will not be accepted. In case of mismatch the file will not be accepted. Recommended usage is at "Payment Information" level. If present at both "Payment Information" level and "Credit Transfer Transaction Information" level, then values given on "Payment Information" level are used. Accepted but not used Accepted but not used Usage Rule: Only following codes are allowed: SEPA; URGP; SDVA; NURG Only value SEPA is forwarded to the beneficiary bank in case of Estonian and EU payments if appilcable. Accepted codes: NORM – payment type is set to normal HIGH – payment type is set to urgent for Estonian and international payments EXPR – payment type is set to urgent for Estonian, and international payments. Payment type is set to express for international payments in EUR, USD. Value dates and cut-off times of different payment types are available in Price List. If Local Instrument Proprietary is not entered by the initiating party, the bank processes the payment as non-urgent payment. If present on "Credit Transfer Transaction Information" level and "Payment Information" level, then value given on "Payment Information"level is used. Accepted but not used. Forwarded to the beneficiary bank in case of Estonian and EU payments if applicable. Cannot be more than 180 days in future. Past dates are converted to current date. Accepted but not used. The Debtor's name will be taken from bank's customer database and this value will be sent to the Beneficiary Bank. Accepted but not used. Accepted and forwarded to the beneficiary bank in case of Estonian and EU payments if applicable. In case of international payments the debtor's country is taken from bank's customer database and this value is sent to the beneficiary bank. Accepted but only 2 occurences allowed and forwarded to the beneficiary bank in case of Estonian and EU payments if applicable, the rest will be ignored. In case of international payments the debtor's address is taken from bank's customer database and this value is sent to the beneficiary bank. Accepted and forwarded to the beneficiary bank in case of Estonian and EU payments if applicable. 7

2.19

{Or

2.19 2.19 2.19 2.19 2.19 2.19 2.19

{{Or Or}} [1..1] [0..1] {{{Or Or}}} Or}

2.19

{{Or

2.19 2.19 2.19 2.19 2.19 2.19 2.19 2.19

[1..1] [1..1] [1..1] Or}} [1..1] [0..1] {{{Or Or}}}

++++ Organisation Identification +++++ BIC or BEI +++++ Other ++++++ Identification ++++++ Scheme Name +++++++ Code +++++++ Proprietary ++++ Private Identification +++++ Date And Place Of Birth ++++++ Birth Date ++++++ City Of Birth ++++++ Country Of Birth +++++ Other ++++++ Identification ++++++ Scheme Name +++++++ Code +++++++ Proprietary

2.20

[1..1]

++ Debtor Account

2.20 2.20 2.20 2.21

[1..1] [1..1] [0..1] [1..1]

2.21

[1..1]

2.21

[1..1]

+++ Identification ++++ IBAN +++ Currency ++ Debtor Agent +++ Financial Institution Identification ++++ BIC

2.23

[0..1]

++ Ultimate Debtor

2.23 2.23

[0..1] [0..1]

2.23

{Or

2.23 2.23 2.23 2.23 2.23 2.23

{{Or Or}} [1..1] [0..1] [1..1] Or}

2.23

{{Or

+++ Name +++ Identification ++++ Organisation Identification +++++ BIC or BEI +++++ Other ++++++ Identification ++++++ Scheme Name +++++++ Code ++++ Private Identification +++++ Date And Place Of Birth

>CityOfBirth>

Identification of an organisation. Usage Rule: Same rule as in SEPA Core Requirements applies. Either "BIC or BEI" or one occurence of "Other" is allowed.

Only IBAN is allowed. In case of incorrect account, the file can’t be imported. Must be account in Danske Bank Estonia. Forwarded to beneficiary bank. Used for cover currency for all payments.

Only Danske Bank’s BIC FOREEE2X is allowed. Forwarded to beneficiary bank. Accepted and forwarded to Beneficiary Bank in case of Estonian and EU payments if applicable. Limited to 70 characters in length

Either "BIC or BEI" or one occurence of "Other" is allowed.

Either "DateAndPlaceOfBirth" or one occurence of "Other" is allowed.

8

2.23 2.23 2.23 2.23 2.23 2.23 2.23

[1..1] [1..1] [1..1] Or}} [1..1] [0..1] [1..1]

++++++ Birth Date ++++++ City Of Birth ++++++ Country Of Birth +++++ Other ++++++ Identification ++++++ Scheme Name +++++++ Code

2.24

[0..1]

++ Charges Bearer

2.25 2.25 2.25

[0..1] [1..1] [1..1]

++ Charges Account +++ Identification ++++ IBAN

2.25

[0..1]

+++ Currency

2.27

[1..n]

2.28

[1..1]

++ Credit Transfer Transaction Information +++ Payment Identification

2.29

[0..1]

++++ Instruction Identification

2.30

[1..1]

++++ End To End Identification

2.31

[0..1]

+++ Payment Type Information

2.33

[0..1]

++++ Service Level





[1..1]

+++++ Code

Gives a possibility to set a currency from where the charges should be debited. Account must be the same as Debtor Account, currency may differ.



2.34

Recommended to use at "Payment Information" level. Therefore if present at "Credit Transfer Transaction Information" level and "Payment Information" level, then value given on "Payment Information"level is used. Accepted codes: DEBT – “payment in full” – all transaction charges are to be borne by the debtor. Not valid for SEPA. SHAR – “shared” – transaction charges on the sender side are to be borne by the debtor, transaction charges on the receiver side are to be borne by the creditor. SLEV – following service level. Charges are to be applied following the rules agreed in the service level and/or scheme. CRED – code is not allowed and will be treated as SLEV. If missing, it will be treated as SLEV. If used, must be same as Debtor account.



Recommended to be unique in payment message. The value is not passed on to the beneficiary. The value is forwarded to the beneficiary in case of Estonian and EU payments if applicable. Recommended to be unique for better identification of transaction. Special value “NOTPROVIDED” for empty content. May not contain special characters including ”å”, “ä” and “ö”. Recommended usage is at "Payment Information" level. If present at both "Payment Information" level and "Credit Transfer Transaction Information" level, then values given on "Payment Information" level are used. Accepted but not used. Usage Rule: Only following codes are allowed: SEPA; URGP; SDVA; NURG Only value SEPA is forwarded to the beneficiary bank in case of Estonian and EU payments if applicable. 9

[0..1] {Or Or}

++++ Local Instrument +++++ Code +++++ Proprietary



2.39

[0..1]

++++ Category Purpose

2.40

[1..1]

+++++ Code



2.42

[1..1]

+++ Amount

2.43

{Or

++++ Instructed Amount

2.44 2.45 2.46

Or} [1..1] [1..1]

++++ Equivalent Amount +++++Amount +++++Currency Of Transfer

2.36 2.37

2.38

2.51

[0..1]

+++ Charge Bearer

2.70

[0..1]

+++ Ultimate Debtor

2.70 2.70

[0..1] [0..1]

2.70

{Or

2.70 2.70 2.70 2.70

{{Or Or}} [1..1] [0..1]

++++ Name ++++ Identification +++++ Organisation Identification ++++++ BIC or BEI ++++++ Other +++++++ Identification +++++++ Scheme Name





Accepted codes: NORM – payment type is set to normal HIGH – payment type is set to urgent for Estonian, and international payments EXPR – payment type is set to urgent for Estonian, and international payments. Payment type is set to express for international payments in EUR, USD. Value dates and cut-off times of different payment types are available in Price List. Other values will be set to NORM. If "Local Instrument" "Proprietary" is not entered by the initiating party, the bank processes the payment as non-urgent payment. If present on "Credit Transfer Transaction Information" level and PmtInf level, then value given on "Payment Information" level is used. Accepted but not used. Forwarded to the beneficiary bank in case of Estonian and EU payments if applicable. Needs to be positive. Limited to 14 digits in total and 2 fraction digits. Forwarded to beneficiary bank. Not supported

Recommended to use at "Payment Information" level. Therefore if present on "Credit Transfer Transaction Information" level and "Payment Information" level, then value given on "Payment Information" level is used. Accepted codes: DEBT- “payment in full” – all transaction charges are to be borne by the debtor. Not valid for SEPA. SHAR – “shared” – transaction charges on the sender side are to be borne by the debtor, transaction charges on the receiver side are to be borne by the creditor. SLEV – following service level. Charges are to be applied following the rules agreed in the service level and/or scheme. CRED – code is not allowed and will be treated as SLEV. If missing, it will be treated as SLEV. Accepted but not used, will be forwarded to Beneficiary Bank in case of Estonian and EU payments if applicable. Limited to 70 characters in length. Either "BIC or BEI" or one occurence of "Other" is allowed.

10

2.70 2.70

[1..1] Or}

2.70

{{Or

2.70 2.70 2.70 2.70 2.70 2.70 2.70

[1..1] [1..1] [1..1] Or}} [1..1] [0..1] [1..1]

++++++++ Code +++++ Private Identification ++++++ Date And Place Of Birth +++++++ Birth Date +++++++ City Of Birth +++++++ Country Of Birth ++++++ Other +++++++Identification +++++++ Scheme Name ++++++++ Code

2.71

[0..1]

+++ Intermediary Agent 1

2.71

[1..1]

2.71

[0..1]

2.71

[0..1]

2.71

[0..1]

2.71 2.71 2.71 2.71 2.71 2.71

[1..1] [1..1] [0..1] [0..1] [0..1] [0..2]

2.72

[0..1]

2.72 2.72

[1..1] {Or

++++ Financial Institution Identification +++++ BIC +++++ Clearing System Member Identification ++++++ Clearing System Identification +++++++ Code ++++++ Member Identification +++++ Name +++++ Postal Address ++++++ Country ++++++ Address Line +++ Intermediary Agent 1 Account ++++ Identification +++++ IBAN

Or}

+++++ Other

2.72

[1..1]

++++++ Identification

2.77

[0..1]

+++ Creditor Agent

2.77

[1..1]

++++ Financial Institution Identification

2.77

[0..1]

+++++ BIC

2.77

[0..1]

+++++ Clearing System

2.72



Either "DateAndPlaceOfBirth" or one occurence of "Other" is allowed.

Only valid for for international payments, when applicable. Used to indicate correspondent bank of beneficiary’s bank.



RUB payments: "RUCBC" RUB payments: value of the BIK code of parent bank (9 digits) Limited to 70 characters in lenght.

Only two occurences accepted