ISO 20022 Message Implementation Guide
for Payment Initiation
Pain001
Pain002
Version: 1.5
Issue date: 16 November 2015
Author: Swedbank
Table of Contents
1. Introduction
2. Customer Credit Transfer Initiation V3 pain.001.001.03
3. Customer Payment Status Report pain.002.001.03
3.1 Statuses in Pain002
4. Examples
4.1 Domestic Payment Estonia, 2 payments
4.2 International Payment example (express payment in USD, via correspondent bank)
4.3 European Payment example (Sepa Credit Transfer)
4.4 Consolidated Payment example
4.5 International payment in Russian roubles example (via correspondent bank)
4.6 Payment status report pain.002.001.03 example (accepted)
4.7 Payment status report pain.002.001.03 example (rejected)
Revision history
Version
1.0
Changes
First version of the MIG, main focus on EE local Banking Association MIG
Date
1.1
Revision history added
Allowed characters and file encoding described in more detail.
InstructionIdentification will become optional starting from 10.04.2014, limitation on length removed
from International Payment. Lithuania will still have local clearing related limitations applied to
interbank Domestic Payment.
ClearingSystemMemberIdentification not supported.
PaymentTypeInformation logic and rules explained for payment type determination.
RegulatoryReporting updated, not used in Estonia starting from 01.02.2014.
Pain.002 GroupStatus, PaymentInformationStatus and TransactionStatus updated
2014.02.27
1.2
Express payment currencies list updated
InstructionIdentification remains mandatory for Consolidated Payment
2014.04.02
1.3
Payment type definition page added to Introduction
Payment type detection rules explained in detail
2014.06.19
2013.12.09
Version
1.4
Changes
€ added to whitelisted characters set.
Specified characters restriction for domestic payments referencies, identifications and identifiers
Updated description of payment types and payment types detection
pain001:
PrivateIdentification is accepted for InitiatingParty and Debtor.
DebtorAgent Name is acepted. BIC changed to optional
Identification SchemeName Codes for Domestic payments are updated
Identification SchemeName Proprietary is accepted for SEPA cross-border payments
Creditor CountryOfResidence rule in Latvia is updated
UltimateCreditor Name is optional field
Information about UltimateDebtor and UltimateCreditor PostalAddress is overpopulated and tags are
removed from Swedbank MIG
Customer rules of RegulatoryReporting in Latvia updated
RemittanceInformation rules for Lithuania are updated
pain002:
StatusReasonInformation added in following blocks: OriginalGroupInformationAndStatus,
OriginalPaymentInformationAndStatus
Originator Identification and AccountServicerReference added to TransactionInformationAndStatus
block
1.5
Complemented explanations for:
ChargeBearer type CRED
xml escape characters: < >
Consolidated payments execution priority
Aligned terms: Payer changed to Creditor, field replaced with tag
Added reference to External code set at ISO 20022 site
Possibility to provide structured details for consolidated payments will appear in December, 2015.
Complemented list of countries where SEPA payments can be made
Date
2015.07.09
2015.11.16
1. Introduction
The purpose with this document is to provide guidance about how the Payment ISO messages shall shall be structured when exchanging information between
Customer and Swedbank for the following messages:
-Pain.001.001.03 - used to initiate a credit transfer
-Pain.002.001.03 - used to report on the status of a credit transfer initiation
This document should be read together with the ISO 20022 Message Definition Report since not all information have been repeated. Message elements that are
not represented in this document will be viewed as overpopulated and will be ignored. External code set specification could be found at
http://www.iso20022.org/external_code_list.page
This Message Implementation Guide complies with the international definitions for content and use of ISO20022, Common Global Implementation (CGI)
recommendations and country MIG guidelines. In case of differences in documents please consult with bank about correct Swedbank ISO MIG usage.
Character set
In UNIFI messages the UTF8 encoding must be used. Encoding must be declared in the XML header.
The Latin character set, which is commonly used for international communication, must be used.
It contains the following characters:
abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ
0123456789
/ - ? : ( ) . , ' + space
Local characters
In interbank Domestic Payments additionally local characters are allowed:
In Estonia: Šš, Žž, Õõ, Ää, Öö, Üü
In Latvia: Āā, Čč, Ēē, Ģģ, Īī, Ķķ, Ļļ, Ņņ, Šš, Ūū, Žž
In Lithuania: Ąą, Čč, Ęę, Ėė, Įį, Šš, Ųų, Ūū, Žž
Whitelisted characters
Commonly used characters, which will be accepted, but replaced in domestic bank-to-bank message with ?, are:
&%#|_";=!€
XML escape characters
Symbols not allowed in XML must be replaced in message according to escaping rules:
& replaced with &amp;
< replaced with &lt;
" replaced with &quot;
> replaced with &gt;
' replaced with &apos;
Characters for domestic payments references, identifications and identifiers
Instruction ID, End-to-End ID, Transaction ID, Message ID, Payment Information ID, Creditor and Debtor ID, Ultimate Debtor/Creditor ID, Remittance ID,
Proprietary codes must respect the following:
• Content is restricted to the Latin character set
• Content must not start or end with a ‘/’
• Content must not contain ‘//’s
Description on the columns:
ISO Index NO – Number that 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”
Or – indicates that only one of several elements may be presented
Message Item - Element name used in ISO 20022 XML Message Definition Report.
Tag Name - Name that identifies an element within an XML message. Is based on the
ISO 20022 XML Message Definition Report.
ISO Type - Indicates the ISO type
Mult - 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 n 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 n times
Rules - Provides information of usage in Swedbank messages.
Description of payment types
Intrabank payment
- payment in any currency to other account in Swedbank
Domestic payment
- payment in euros to other local bank
- Consolidated payment
Sub-type of Domestic payment, which combines Intrabank and Domestic of the same currency. It's defined with value
SALA in tag CategoryPurpose/Code. Payments initiated with code SALA are presented on account statement as single entry
for the users who are not permitted to view individual salary payments one by one.
European payment
- payment in euros to bank located in SEPA*
It is mandatory to indicate Creditor's IBAN and Creditor Agent's BIC till 2016.02.01. ChargeBearer has to be set as SHAR or
SLEV
International non-European payment
- payment in euros to bank located outside of European Economic Area
- payment in any other currency to
- other local bank
- bank located in SEPA
- bank located outside of SEPA
Swedbank group payment
- payment to a Creditor in Swedbank Sweden, Norway, Denmark, Finland, Estonia, Latvia or Lithuania. Approved currencies
are SEK, NOK, DKK, EUR, USD.
-------------------*SEPA:
Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece,
French Guyana, Gibraltar, Guadeloupe, Hungary, Iceland, Ireland, Italy, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta,
Monaco, San Marino, Switzerland, The Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, United
Kingtom.
Payments within one Baltic country are considered as domestic payments.
Payment type detection
Column Order indicates in which order system should check if there exists a specific combination, as stated in column pain.001 code
Order
pain001 code
Intrabank,
Swedbank group,
Consolidated
payment
STEP1
STEP2
Local Instrument/Proprietary=NORM
Local Instrument/Proprietary=HIGH
NORMAL
NORMAL
NORMAL
URGENT
NORMAL
URGENT
NORMAL
URGENT
STEP3
STEP4
Local Instrument/Proprietary=EXPR
Service Level/Code=SEPA
Service Level/Code=SEPA& Local
Instrument/Code=ONCL
Service Level/Code=SEPA& Local
Instrument/Code=SDCL
Service Level/Code=NURG
Service Level/Code=URGP
Service Level/Code=SDVA
NORMAL
NORMAL
URGENT
NORMAL
EXPRESS
NORMAL
URGENT
NORMAL
NORMAL
NORMAL
NORMAL
NORMAL
NORMAL
NORMAL
NORMAL
NORMAL
URGENT
NORMAL
URGENT
URGENT
NORMAL
NORMAL
URGENT
EXPRESS
NORMAL
NORMAL
URGENT
URGENT
STEP5
STEP6
STEP7
STEP8
STEP9
International non- International nonDomestic*,
European (express European (other
European payment currency)
currency)
If customer indicates any other value in 2.8 <SvcLvl>/ <Cd>, in 2.11 <LclInstrm>/ <Cd>, in 2.33 <SvcLvl>/ <Cd> or
in 2.37 <LclInstrm>/ <Cd> then Bank accepts it and sets payment priority to NORMAL.
Payment type indentifying data is required at either PaymentInformation (PmtInf) or CreditTransferTransactionInformation (CdtTrfTxInf) level.
Recommended usage is at PaymentInformation level.
If present on both PmtInf level and CdtTrfTxInf level, then values given on CdtTrfxinf level are used.
In case of conflicting values for ServiceLevel and LocalInstrument, the LocalInstrument values are used for payment type determination.
* Lithuania: Urgent Domestic payments are available starting from 2016.01.01. There should be taken Intrabank payment rules in 2015.
2. Customer Credit Transfer Initiation V3 pain.001.001.03
Swedbank
ISO
Index
No.
Or
1.0
1.1
Message Item
Tag Name
Structural
Sequence
ISO Type
Mult.
Customer Credit Transfer Initiation
GroupHeader
MessageIdentification
<CstmrCdtTrfInitn
<GrpHdr>
<MsgId>
+
++
Text
[1..1]
[1..1]
Customer RULES
This Id will be stored for 90 days and will be used for duplicate control. Will be returned in
status report
1.2
1.6
CreationDateTime
NumberOfTransactions
<CreDtTm>
<NbOfTxs>
++
++
DateTime
Text
[1..1]
[1..1]
1.7
ControlSum
<CtrlSum>
++
Quantity
[0..1]
1.8
InitiatingParty
Text
[0..1]
Limited to 70 characters in length.
Ignored if it's the same as Debtor
[0..1]
[1..1]
[1..1]
Accepted but not used at the moment.
9.1.0
9.1.12
9.1.13
9.1.15
{Or
9.1.16
9.1.17
9.1.18
9.1.21
9.1.22
9.1.23
9.1.25
9.1.26
9.1.27
9.1.28
9.1.29
9.1.30
2.0
2.1
2.2
<InitgPty>
++
Name
<Nm>
+++
Identification
OrganisationIdentification
Other
<Id>
<OrgId>
<Othr>
+++
++++
+++++
<Id>
<SchmeNm>
<Cd>
++++++
++++++
+++++++
<PrvtId>
<DtAndPlcOfBirth>
<BirthDt>
<CityOfBirth>
<CtryOfBirth>
<Othr>
<Id>
<SchmeNm>
<Cd>
<PmtInf>
<PmtInfId>
++++
+++++
++++++
++++++
++++++
+++++
++++++
++++++
+++++++
+
++
<PmtMtd>
++
Identification
SchemeName
Code
Or}
{{Or
Or}}
PrivateIdentification
DateAndPlaceOfBirth
BirthDate
CityOfBirth
CountryOfBirth
Other
Identification
SchemeName
Code
PaymentInformation
PaymentInformationIdentification
PaymentMethod
Swedbank checks the given value with the total number of transactions in the entire
message.
If given, Swedbank checks the given value with the total amount of all individual transactions
in the entire message.
[1..1]
Text
Code
[1..1]
[0..1]
[1..1]
Text
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[0..1]
[1..1]
[1..n]
[1..1]
Code
[1..1]
DateTime
Text
Code
Text
Code
Only one occurence is allowed, rest will be ignored
Accepted code:
BANK
Other code values will be set to 'Bank'
Either DateAndPlaceOfBirth or one occurence of Other is allowed
Only one occurence is allowed, rest will be ignored
Recommended to be unique. Will be returned in status report.
Accepted code:
TRF
Other code values will be set to 'TRF'
Page 9 of 43
ISO
Index
No.
Or
2.6
Message Item
PaymentTypeInformation
2.8
ServiceLevel
2.9
Code
Tag Name
Structural
Sequence
<PmtTpInf>
++
<SvcLvl>
+++
<Cd>
++++
ISO Type
Mult.
[0..1]
Customer RULES
Required at either PaymentInformation (PmtInf) or CreditTransferTransactionInformation
(CdtTrfTxInf) level. Recommended usage is at PaymentInformation level.
If present on both PmtInf level and CdtTrfTxInf level, then values given on CdtTrfxinf level
are used.
In case of conflicting values for ServiceLevel and LocalInstrument, the LocalInstrument values
are used for payment type determination.
[0..1]
Code
[1..1]
Accepted codes:
NURG
SEPA
- if a payment fulfills the SEPA conditions the payment will automatically be an European or
Domestic payment depending on the payment instructions
URGP
- payment type is set to urgent for Domestic, European(SEPA Credit Transfer) and
International non-European payments
SDVA
- payment type is treated as urgent for Domestic, European and International non-European
payments (please look exeception below)
- payment type is set to express for International non-European payments in EUR, USD
(Estonia) and EUR, USD, SEK, GBP (Latvia)
Value dates and cut-off times of different payment types are available in Price List.
Empty or other values will be set to NURG or SEPA depending on payment instructions
2.11
2.12
LocalInstrument
{Or
Code
<LclInstrm>
+++
<Cd>
++++
[0..1]
Code
[1..1]
Accepted codes:
SDCL
If code is set to SDCL and 2.9 <Cd> is set to SEPA then payment type is set to urgent for
domestic and European payment
ONCL is not supported by Swedbank.
Page 10 of 43
ISO
Index
No.
Or
2.13
Or}
Message Item
Proprietary
Tag Name
Structural
Sequence
<Prtry>
++++
<CtgyPurp>
+++
<Cd>
++++
ISO Type
Text
Mult.
[1..1]
Customer RULES
Accepted codes for Estonia and Latvia:
NORM
HIGH
- payment type is set to urgent for Domestic, European and International non-European
payments
EXPR
- payment type is set to urgent for Domestic, European and International non-European
payments (please look execption below)
- payment type is set to express for International non-European payments in EUR, USD
(Estonia) and EUR, USD, SEK, GBP (Latvia)
Value dates and cut-off times of different payment types are available in Price List.
Other values will be set to NORM
2.14
CategoryPurpose
2.15
Code
2.17
2.19
RequestedExecutionDate
<ReqdExctnDt>
++
Debtor
[0..1]
Code
DateTime
[1..1]
[1..1]
<Dbtr>
++
9.1.0
Name
<Nm>
+++
9.1.1
PostalAddress
<PstlAdr>
+++
9.1.10
Country
<Ctry>
++++
9.1.11
AddressLine
<AdrLine>
++++
<Id>
+++
[0..1]
<OrgId>
++++
[1..1]
9.1.12
9.1.13
Identification
{Or
OrganisationIdentification
9.1.14
{{Or
BICOrBEI
<BICOrBEI>
+++++
9.1.15
9.1.16
9.1.17
Or}}
Other
Identification
SchemeName
<Othr>
<Id>
<SchmeNm>
+++++
++++++
++++++
Accepted codes:
SALA -Will be used for Consolidated Payment functionality. Indicator for consolidated
functionality can only be set at Payment Information level.
Other values will be ignored by Swedbank but forwarded to Beneficiary bank.
Requirements for Consolidated payment:
- file containing Consolidated payment(s) should not contain other payment types
- all underlying sub-payments in a Consolidated payment must be valid in order to be
accepted for processing.
- <InstrId> and <RmtInf> are mandatory for Consolidated payment. Only unstructured
details are acceptable. Possibility to provide structured details for consolidated payments will
appear in December, 2015.
- On camt messages Consolidated payment indicator is <BkTxCd><Prtry><Cd>MP
Cannot be more than 365 days in future. Yesterday's date is converted to Current Date, older
dates are not accepted.
[1..1]
Text
[0..1]
Accepted but not used. The Debtor's name will be taken from Swedbank's customer database
and this value will be sent to the Beneficiary Bank.
[0..1]
Accepted but not used. The Debtor's postal address will be taken from Swedbank's customer
database.
Code
[0..1]
Accepted but not used.
Text
[0..2]
Accepted but not used. Only 2 occurences allowed, the rest will be ignored.
Identifier
[1..1]
Text
[1..1]
[1..1]
[0..1]
Page 11 of 43
Accepted but not used. The Debtor's ID will be taken from Swedbank's customer database
and this value will be sent to the CreditorAgent.
Either BIC or BEI or one occurence of "Other" is allowed.
Only one occurence is allowed, rest will be ignored
ISO
Index
No.
Or
Message Item
9.1.18
9.1.21
Code
Or}
PrivateIdentification
Tag Name
Structural
Sequence
<Cd>
+++++++
<PrvtId>
++++
ISO Type
Code
Mult.
Customer RULES
[1..1]
[1..1]
Either DateAndPlaceOfBirth or one occurence of Other is allowed
Estonia, Latvia: Accepted but not used. The Debtor's ID will be taken from Swedbank's
customer database and this value will be sent to the CreditorAgent.
Lithuania: Provided ID will be frowarded to CreditorAgent.
9.1.22
9.1.23
9.1.25
9.1.26
9.1.27
9.1.28
9.1.29
9.1.30
2.20
1.1.0
1.1.1
1.1.11
{{Or
Or}}
DateAndPlaceOfBirth
BirthDate
CityOfBirth
CountryOfBirth
Other
Identification
SchemeName
Code
DebtorAccount
Identification
IBAN
Currency
<DtAndPlcOfBirth>
<BirthDt>
<CityOfBirth>
<CtryOfBirth>
<Othr>
<Id>
<SchmeNm>
<Cd>
<DbtrAcct>
<Id>
<IBAN>
<Ccy>
+++++
++++++
++++++
++++++
+++++
++++++
++++++
+++++++
++
+++
++++
+++
DateTime
Text
Code
Text
Code
Identifier
Code
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[0..1]
[1..1]
[1..1]
[1..1]
[1..1]
[0..1]
Only one occurence is allowed, rest will be ignored
Only IBAN is allowed
Accepted but not used.
For European and International non-European payments cover currency will be taken from
the main account currency on the agreement in case there is not enough 2.43 Instructed
Amount currency on the account.
2.21
DebtorAgent
6.1.0
6.1.1
FinancialInstitutionIdentification
BIC
6.1.7
Name
2.23
UltimateDebtor
<DbtrAgt>
++
[1..1]
<FinInstnId>
<BIC>
+++
++++
Identifier
[1..1]
[0..1]
Text
<Nm>
++++
<UltmtDbtr>
++
Accepted but not used. Forward to Beneficiary Bank when it's possible.
[0..1]
Limited to 70 characters in length
9.1.0
Name
<Nm>
+++
9.1.12
Identification
<Id>
+++
[0..1]
<OrgId>
++++
[1..1]
<BICOrBEI>
<Othr>
<Id>
<SchmeNm>
<Cd>
+++++
+++++
++++++
++++++
+++++++
9.1.13
{Or
9.1.14
9.1.15
9.1.16
9.1.17
9.1.18
{{Or
Or}}
{{Or
OrganisationIdentification
BICOrBEI
Other
Identification
SchemeName
Code
Text
[0..1]
[0..1]
Identifier
Text
Code
Page 12 of 43
[1..1]
[1..1]
[1..1]
[0..1]
[1..1]
Either "BIC" or "BEI" or one occurence of "other" is allowed.
Either Code or Proprietary must be filled
Code according ISO20022 external code set.
Recomended codes for Domestic Payments
Estonia: COID, CUST, TXID
Latvia: TXID
Lithuania: COID. Code according ISO20022 external code set aceptable after Clearing switch
starting from 2016.01.01
ISO
Index
No.
Or
9.1.19
Or}}
9.1.21
9.1.22
9.1.23
9.1.25
9.1.26
9.1.27
9.1.28
Or}
{{Or
Or}}
Message Item
Proprietary
PrivateIdentification
DateAndPlaceOfBirth
BirthDate
CityOfBirth
CountryOfBirth
Other
Identification
9.1.29
9.1.30
{{Or
SchemeName
Code
9.1.31
Or}}
Proprietary
2.24
ChargeBearer
Tag Name
Structural
Sequence
<Prtry>
+++++++
<PrvtId>
<DtAndPlcOfBirth>
<BirthDt>
<CityOfBirth>
<CtryOfBirth>
<Othr>
<Id>
++++
+++++
++++++
++++++
++++++
+++++
++++++
<SchmeNm>
<Cd>
++++++
+++++++
<Prtry>
<ChrgBr>
ISO Type
Mult.
Customer RULES
Text
[1..1]
Might be used for European cross-border payments.
It is ignored in case of domestic payments.
Either DateAndPlaceOfBirth or one occurence of Other is allowed
DateTime
Text
Code
Text
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
Code
[0..1]
[1..1]
Either Code or Proprietary must be filled
Code according ISO20022 external code set.
Recomended codes for Domestic Payments
Estonia: NIDN, CUST, TXID
Latvia: NIDN
Lithuania: NIDN. Code according ISO20022 external code set acceptable after local Clearing
switch starting from 2016.01.01
+++++++
Text
[1..1]
Might be used for European cross-border payments.
It is ignored in case of domestic payments.
++
Code
[0..1]
Strongly recommended to use at this PaymentInformation (PmtInf) level.
If present on CdtTrfTxInf level and PmtInf level, then value given on CdtTrfTxInf level is
used.
Accepted codes:
DEBT- Not valid for SEPA
SHAR
SLEV
CRED - Not valid in Swedbank
If missing or not valid code, will be treated as SHAR
2.27
2.28
CreditTransferTransactionInformation
PaymentIdentification
<CdtTrfTxInf>
<PmtId>
++
+++
[1..n]
[1..1]
2.29
InstructionIdentification
<InstrId>
++++
Text
[0..1]
Optional starting from mid April 2014, except for Consolidated Payment.
Recommended to be unique in payment message. The value is not passed on to the
beneficiary. Returned in pain.002 message and in camt message of the payment initiator.
2.30
EndToEndIdentification
<EndToEndId>
++++
Text
[1..1]
The value is forwarded to the beneficiary in case of European and Intrabank payments.
Recommended to be unique for better identification of transaction. Returned in pain.002 and
camt messages.
<PmtTpInf>
+++
[0..1]
Required at either PaymentInformation (PmtInf) or CreditTransferTransactionInformation
(CdtTrfTxInf) level. Recommended usage is at PaymentInformation level.
If present on both PmtInf level and CdtTrfTxInf level, then values given on CdtTrfxinf level
are used.
In case of conflicting values for ServiceLevel and LocalInstrument, the LocalInstrument values
are used for payment type determination.
2.31
PaymentTypeInformation
Page 13 of 43
ISO
Index
No.
Or
2.33
Message Item
ServiceLevel
2.34
Code
Tag Name
Structural
Sequence
<SvcLvl>
++++
<Cd>
+++++
ISO Type
Mult.
Customer RULES
[0..1]
Code
[1..1]
Accepted codes:
NURG
SEPA
- if a payment fulfills the SEPA conditions the payment will automatically be an European or
Domestic payment depending on the payment instructions
URGP
- payment type is set to urgent for Domestic, European (SEPA Credit Transfer) and
International non-European payments
SDVA
- payment type is treated as urgent for Domestic, European and International non-European
payments (please look exeception below)
- payment type is set to express for International non-European payments in EUR, USD
(Estonia) and EUR, USD, SEK, GBP (Latvia)
Value dates and cut-off times of different payment types are available in Price List.
Empty or other values will be set to NURG or SEPA depending on payment instructions
2.36
2.37
LocalInstrument
{Or
Code
<LclInstrm>
++++
<Cd>
+++++
[0..1]
Code
[1..1]
Accepted codes:
SDCL
If code is set to SDCL and 2.9 <Cd> is set to SEPA then payment type is set to urgent for
domestic and European payment
ONCL is not supported by Swedbank.
2.38
Or}
Proprietary
<Prtry>
+++++
Text
[1..1]
Accepted codes:
NORM
HIGH
- payment type is set to urgent for Domestic, European and International non-European
payments
EXPR
- payment type is set to urgent for Domestic, European and International non-European
payments (please look execption below)
- payment type is set to express for international non-European payments in EUR, USD
(Estonia, Lithuania) and EUR, USD, SEK, GBP, RUB (Latvia)
Value dates and cut-off times of different payment types are available in Price List.
Other values will be set to NORM
2.39
2.40
2.42
CategoryPurpose
Code
Amount
<CtgyPurp>
<Cd>
++++
+++++
<Amt>
+++
Code
[0..1]
[1..1]
[1..1]
Page 14 of 43
Indicator for Consolidated payment functionality should only be set at Payment information
level, see 2.14<CategoryPurpose><Cd>
ISO
Index
No.
Or
2.43
Message Item
InstructedAmount
2.51
ChargeBearer
Tag Name
Structural
Sequence
ISO Type
Mult.
Customer RULES
<InstdAmt
Ccy="AAA">
++++
Amount
[1..1]
Needs to be positive. Limited to 14 digits in total and 2 fraction digits. If Instructed Amount
Currency does not exist on the Debtor account in required amount, cover currency will be
set to the account main currency.
<ChrgBr>
+++
Code
[0..1]
Strongly recommended to use at PmtInf level.
If present on CdtTrfTxInf level and PmtInf level, then value given on CdtTrfTxInf level is
used.
Accepted codes:
DEBT- Not valid for SEPA
SHAR
SLEV
CRED - Not valid in Swedbank
If missing or not valid code, will be treated as SHAR
2.70
UltimateDebtor
9.1.0
9.1.12
9.1.13
9.1.14
9.1.15
9.1.16
{Or
{{Or
Or}}
<UltmtDbtr>
+++
Name
<Nm>
++++
Identification
OrganisationIdentification
<Id>
<OrgId>
++++
+++++
BICOrBEI
Other
Identification
<BICOrBEI>
<Othr>
<Id>
++++++
++++++
+++++++
<SchmeNm>
<Cd>
9.1.17
9.1.18
{{Or
SchemeName
Code
9.1.19
Or}}
Proprietary
9.1.21
9.1.22
9.1.23
9.1.25
9.1.26
9.1.27
9.1.28
Or}
{{Or
9.1.29
Or}}
PrivateIdentification
DateAndPlaceOfBirth
BirthDate
CityOfBirth
CountryOfBirth
Other
Identification
SchemeName
Text
Identifier
[0..1]
Only used at PmtInf level.
[0..1]
Limited to 70 characters in length
[0..1]
[1..1]
Either "BIC" or "BEI" or one occurence of "other" is allowed.
Text
[1..1]
[1..1]
[1..1]
+++++++
++++++++
Code
[0..1]
[1..1]
Either Code or Proprietary must be filled
Code according ISO20022 external code set.
Recomended codes for Domestic Payments
Estonia: COID, CUST, TXID
Latvia: TXID
Lithuania: COID. Code according ISO20022 external code set acceptable after local Clearing
switch starting from 2016.01.01
<Prtry>
++++++++
Text
[1..1]
<PrvtId>
<DtAndPlcOfBirth>
<BirthDt>
<CityOfBirth>
<CtryOfBirth>
<Othr>
<Id>
+++++
++++++
+++++++
+++++++
+++++++
++++++
+++++++
DateTime
Text
Code
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
Might be used for European cross-border payments.
It is ignored in case of domestic payments.
Either "DateAndPlaceOfBirth" or one occurence of "Other is allowed".
<SchmeNm>
+++++++
Text
[0..1]
Page 15 of 43
Either Code or Proprietary must be filled
ISO
Index
No.
Or
9.1.30
{{Or
9.1.31
Or}}
2.71
Message Item
Tag Name
Structural
Sequence
Code
<Cd>
++++++++
Code
[1..1]
Code according ISO20022 external code set.
Recomended codes for Domestic Payments
Estonia: NIDN, CUST, TXID
Latvia: NIDN
Lithuania: NIDN. Code according ISO20022 external code set acceptable after local Clearing
switch starting from 2016.01.01
Proprietary
<Prtry>
++++++++
Text
[1..1]
<IntrmyAgt1>
+++
Might be used for European cross-border payments.
It is ignored in case of domestic payments.
Only valid for for International non-European Payments, when applicable. Used to indicate
correspondent bank of Creditor Agent
<FinInstnId>
<BIC>
<Nm>
++++
+++++
+++++
IntermediaryAgent1
6.1.0
6.1.1
6.1.7
FinancialInstitutionIdentification
BIC
Name
ISO Type
Mult.
[0..1]
Identifier
Text
[1..1]
[0..1]
[0..1]
Customer RULES
Only 70 characters
RUB payments: the data of the parent bank - full name + city + BIK of the parent bank (9
digits) + correspondent account of the parent bank in the Central Bank of the Russian
Federation (20 digits, starts with 301)
6.1.8
6.1.17
6.1.18
2.72
1.1.0
1.1.1
1.1.2
1.1.3
2.73
PostalAddress
Country
AddressLine
{Or
Or}
6.1.0
6.1.1
6.1.7
FinancialInstitutionIdentification
BIC
Name
6.1.8
6.1.17
6.1.18
2.74
1.1.0
1.1.1
1.1.2
1.1.3
2.77
IntermediaryAgent1Account
Identification
IBAN
Other
Identification
IntermediaryAgent2
PostalAddress
Country
AddressLine
{Or
Or}
IntermediaryAgent2Account
Identification
IBAN
Other
Identification
CreditorAgent
<PstlAdr>
<Ctry>
<AdrLine>
+++++
++++++
++++++
<IntrmyAgt1Acct>
<Id>
<IBAN>
<Othr>
<Id>
<IntrmyAgt2>
+++
++++
+++++
+++++
++++++
+++
<FinInstnId>
<BIC>
<Nm>
++++
+++++
+++++
<PstlAdr>
<Ctry>
<AdrLine>
+++++
++++++
++++++
<IntrmyAgt2Acct>
<Id>
<IBAN>
<Othr>
<Id>
<CdtrAgt>
+++
++++
+++++
+++++
++++++
+++
[0..1]
[0..1]
[0..2]
Only two occurences accepted
[0..1]
[1..1]
[1..1]
[1..1]
[1..1]
[0..1]
Only valid for for International non-European payments, when applicable.
Identifier
Text
[1..1]
[0..1]
[0..1]
Only 70 characters
Code
Text
[0..1]
[0..1]
[0..2]
Only two occurences accepted
Code
Text
Identifier
Text
Identifier
Text
[0..1]
[1..1]
[1..1]
[1..1]
[1..1]
[0..1]
In case of Domestic Payment – whole block of Creditor Agent is ignored (e.g. if BIC belongs
to SEB EE but Creditor Account IBAN belongs to Nordea EE
then payment order is not rejected but processed according to IBAN)
International non-European payment - either CreditorAgent/BIC or CreditorAgent/Name (or
both) must be filled.
European Payment (SEPA Credit Transfer) - if currency=EUR and CreditorAgent IBAN starts
with country code of EU/EEA then CreditorAgent/BIC tag is mandatory untill 2016.02.01.
Page 16 of 43
ISO
Index
No.
Or
6.1.0
6.1.1
Message Item
FinancialInstitutionIdentification
BIC
Tag Name
Structural
Sequence
<FinInstnId>
<BIC>
++++
+++++
ISO Type
Mult.
Identifier
[1..1]
[0..1]
6.1.2
6.1.3
6.1.4
ClearingSystemMemberIdentification <ClrSysMmbId>
ClearingSystemIdentification
<ClrSysId>
Code
<Cd>
+++++
++++++
+++++++
Code
[0..1]
[0..1]
[1..1]
6.1.6
6.1.7
MemberIdentification
Name
++++++
+++++
Text
Text
[1..1]
[0..1]
<MmbId>
<Nm>
Customer RULES
In case of European payments BIC is mandatory untill 2016.02.01.
Accepted but not used. Currently not supported in Swedbank
Only 70 characters
RUB payment - full name of the Creditor's Agent + city + BIC of the Creditor Agent (9 digits)
+ correspondent account of the Creditor's Agent in the Central Bank of the Russian
Federation (20 digits, starts with 301). The last three digits of the BIC and the correspondent
account must coincide.
In case Creditor's Agent is a branch of the bank: the name of the branch and the account are
inserted in the tag CreditorAgent/Name
6.1.8
6.1.17
6.1.18
2.78
1.1.0
1.1.1
1.1.2
1.1.3
2.79
9.1.0
PostalAddress
Country
AddressLine
{Or
Or}
CreditorAgentAccount
Identification
IBAN
Other
Identification
Creditor
Name
<PstlAdr>
<Ctry>
<AdrLine>
+++++
++++++
++++++
<CdtrAgtAcct>
<Id>
<IBAN>
<Othr>
<Id>
<Cdtr>
<Nm>
+++
++++
+++++
+++++
++++++
+++
++++
Code
Text
Identifier
Text
Text
[0..1]
[0..1]
[0..2]
Only two occurences accepted
[0..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
Only 70 characters
RUB payment - the taxpayer identification number or INN (and KPP) is inserted in the tag
Creditor/Name before the name. If the Creditor's name is too long, the remainder of the
name must be written in the PstlAdr/AdrLine tag without any spaces (without a hyphen).
9.1.1
PostalAddress
9.1.10
9.1.11
9.1.12
9.1.13
9.1.14
9.1.15
9.1.16
9.1.17
Country
AddressLine
{Or
{{Or
Or}}
Identification
OrganisationIdentification
BICOrBEI
Other
Identification
SchemeName
<PstlAdr>
++++
<Ctry>
<AdrLine>
+++++
+++++
[0..1]
Forward if possible
Code
Text
[0..1]
[0..2]
<Id>
<OrgId>
<BICOrBEI>
Only two occurences accepted, total length max 70 characters
++++
+++++
++++++
Identifier
[0..1]
[1..1]
[1..1]
Either BIC or BEI or one occurence of "Other" is allowed.
<Othr>
<Id>
++++++
+++++++
Text
[1..1]
[1..1]
<SchmeNm>
+++++++
[0..1]
Page 17 of 43
Either Code or Proprietary must be filled
ISO
Index
No.
Or
9.1.18
{{Or
9.1.19
Or}}
9.1.21
9.1.22
9.1.23
9.1.25
9.1.26
9.1.27
9.1.28
Or}
{{Or
Or}}
Message Item
Tag Name
Structural
Sequence
Code
<Cd>
++++++++
Code
[1..1]
Code according ISO20022 external code set.
Recomended codes for Domestic Payments
Estonia: COID, CUST, TXID
Latvia: TXID
Lithuania: COID, CUST. Code according ISO20022 external code set acceptable after local
Clearing switch starting from 2016.01.01
Proprietary
<Prtry>
++++++++
Text
[1..1]
Might be used for European cross-border payments.
It is ignored in case of domestic payments.
<PrvtId>
<DtAndPlcOfBirth>
<BirthDt>
<CityOfBirth>
<CtryOfBirth>
<Othr>
<Id>
+++++
++++++
+++++++
+++++++
+++++++
++++++
+++++++
Either DateAndPlaceOfBirth or one occurence of "Other" is allowed.
DateTime
Text
Code
Text
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
<SchmeNm>
<Cd>
+++++++
++++++++
Code
[0..1]
[1..1]
Either Code or Proprietary must be filled
Code according ISO20022 external code set.
Recomended codes for Domestic Payments
Estonia: NIDN, CUST, TXID
Latvia: NIDN
Lithuania: NIDN, CUST. Code according ISO20022 external code set acceptable after local
Clearing switch starting from 2016.01.01
<Prtry>
++++++++
Text
[1..1]
<CtryOfRes>
++++
Code
[0..1]
Might be used for European cross-border payments.
It is ignored in case of domestic payments.
Latvia: User shall provide Country Of Recidence if Creditor is non-resident, exluding when
both Debtor and Creditor are non-residents and the amount > 10000EUR
<CdtrAcct>
<Id>
<IBAN>
+++
++++
+++++
Identifier
[1..1]
[1..1]
[1..1]
<Othr>
<Id>
+++++
++++++
Text
[1..1]
[1..1]
RUB payment - a 20-digit number, the digits 6-8 of which are 810
<UltmtCdtr>
+++
[0..1]
Only forwarded with Domestic and European payment (except payment with type urgent)
[0..1]
Only 70 character
PrivateIdentification
DateAndPlaceOfBirth
BirthDate
CityOfBirth
CountryOfBirth
Other
Identification
9.1.29
9.1.30
{{Or
SchemeName
Code
9.1.31
Or}}
Proprietary
9.1.33
2.80
1.1.0
1.1.1
1.1.2
1.1.3
CountryOfResidence
{Or
Or}
2.81
CreditorAccount
Identification
IBAN
Other
Identification
UltimateCreditor
9.1.0
Name
<Nm>
++++
9.1.12
Identification
<Id>
++++
9.1.13
{Or
9.1.14
9.1.15
{{Or
Or}}
OrganisationIdentification
BICOrBEI
Other
ISO Type
Text
Mult.
Customer RULES
In case of Domestic and European payment IBAN is mandatory
[0..1]
<OrgId>
+++++
[1..1]
Either "BIC" or "BEI" or one occurence of "other" is allowed.
<BICOrBEI>
<Othr>
++++++
++++++
Identifier
[1..1]
[1..1]
Only one occurence is allowed, rest will be ignored
Text
[1..1]
9.1.16
Identification
<Id>
+++++++
9.1.17
SchemeName
<SchmeNm>
+++++++
[0..1]
Page 18 of 43
Either Code or Proprietary must be filled
ISO
Index
No.
9.1.18
Or
{{Or
9.1.19
Or}}
9.1.21
9.1.22
9.1.23
9.1.25
9.1.26
9.1.27
9.1.28
Or}
{{Or
9.1.29
9.1.30
9.1.31
Message Item
Or}}
Tag Name
Structural
Sequence
Code
<Cd>
++++++++
Code
[1..1]
Code according ISO20022 external code set.
Recomended codes for Domestic Payments
Estonia: COID, CUST, TXID
Latvia: TXID
Lithuania: COID. Code according ISO20022 external code set acceptable after local Clearing
switch starting from 2016.01.01
Proprietary
<Prtry>
++++++++
Text
[1..1]
Might be used for European cross-border payments.
It is ignored in case of domestic payments.
<PrvtId>
<DtAndPlcOfBirth>
<BirthDt>
<CityOfBirth>
<CtryOfBirth>
<Othr>
<Id>
+++++
++++++
+++++++
+++++++
+++++++
++++++
+++++++
Either "DateAndPlaceOfBirth" or one occurence of "Other is allowed".
DateTime
Text
Code
Text
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
<SchmeNm>
<Cd>
+++++++
++++++++
Code
[0..1]
[1..1]
Either Code or Proprietary must be filled
Code according ISO20022 external code set.
Recomended codes for Domestic Payments
Estonia: NIDN, CUST, TXID
Latvia: NIDN
Lithuania: NIDN. Code according ISO20022 external code set acceptable after local Clearing
switch starting from 2016.01.01
<Prtry>
++++++++
Text
[1..1]
Might be used for European cross-border payments.
It is ignored in case of domestic payments.
PrivateIdentification
DateAndPlaceOfBirth
BirthDate
CityOfBirth
CountryOfBirth
Other
Identification
SchemeName
Code
{{Or
Or}}
Proprietary
2.86
Purpose
<Purp>
+++
2.87
2.89
Code
RegulatoryReporting
<Cd>
<RgltryRptg>
++++
+++
11.1.4
Details
<Dtls>
++++
ISO Type
Mult.
Customer RULES
[0..1]
Code
[1..1]
Information about declaration of payments.
Only one occurence allowed, rest is ignored
[0..1]
Latvia:
Regulatory reporting is mandatory if one of the parties is resident and another party is not
resident(i.e. exluding when both Debtor and Creditor are residents or both Debtor and
Creditor are non-residents) and the amount > 10000EUR
[0..0]
Estonia, Lithuania:
Is not used, information will be ignored
11.1.5
Type
<Tp>
+++++
Text
[0..2] Latvia:
Only two occurences are valid the rest are ignored.
[0..1] Latvia:
Should contain EKK when budget income code is transferred in <Cd> (11.1.8)
Should contain AMK when external payment code is transferred in <Cd> (11.1.8)
11.1.7
Country
<Ctry>
+++++
Code
[0..1]
Page 19 of 43
Country ISO code (ISO 3166, Alpha-2 code), see
http://www.iso.org/iso/country_codes/iso_3166_code_lists/country_names_and_code_eleme
nts.htm
ISO
Index
No.
11.1.8
Or
Message Item
Code
Tag Name
Structural
Sequence
<Cd>
+++++
ISO Type
Text
Mult.
[1..1]
Customer RULES
Latvia:
Code of the balance of payment. For appropriate code see:
http://www.bank.lv/en/legal/list-of-external-payment-codes-lepc-21
If tag <Tp> (11.1.5) contains code EKK then the code value should contain budget income
code
11.1.10
2.98
Information
RemittanceInformation
<Inf>
+++++
<RmtInf>
+++
Text
[0..1]
[0..1]
Domestic Payments:
Estonia: unstructured or structured remittance information or both needs to be present. When
the client fills both, the structured and unstructured information tags, only 130 characters of
combined length is accepted. When bank cannot forward both tags, then creditor reference
under the structured information will be lifted to the unstructured information tag in
accordance with EACT standard for unstructured remittance information formatting rules. If
the remittance information as a result will be longer than 140 characters, then the bank will
deliver only 140 characters of the remittance information. For example
/RFB/XXXXXX/TXT/ZZZZZZ, where RFB stands for the code of creditor reference, XXXXXX
stands for the creditor reference, TXT stands for the code of unstructured information and
ZZZZZZ stands for the unstructured information.
Latvia: Either unstructured or structured remittance information must be present but not
both. Creditor reference under the structured information will be copied to the unstructured
information tag in accordance with EACT standard for unstructured remittance information
formatting rules - to assure compatibility with legacy statement formats.
Lithuania: Either unstructured or structured remittance information must be present but not
both. In case Structured remittance information is provided unstructured information tag will
be filled with minus ("-") character to assure compatibility with legacy payment formats until
2016.01.01.
European Payment: Either unstructured or structured remittance information must be present
but not both.
International non-European payments: Only unstructured remittance information is accepted.
Page 20 of 43
ISO
Index
No.
2.99
Or
Message Item
Unstructured
Tag Name
Structural
Sequence
<Ustrd>
++++
ISO Type
Text
Mult.
Customer RULES
[0..1] Only 1 occurence allowed with maximum 140 Characters. If unstructured and structured
references are both used the maximum accepted combined length is 130.
Estonia:
If in Domestic payment information is filled in accordance of EACT standard for Unstructured
remittance information formatting rules, RFB value will be validated by same rules as
Structured Reference. In case of successful validation, the information is stored to separate
values for payment initiator's account statement => Payment details and Creditor Reference.
International non-European payment in RUB - currency transaction code (VO) + verbal
clarification of the payment (detailed information about goods/service, if payment is executed
before goods are delivered then should be written predoplata za...., if payment is executed
after goods are delivered then oplata za....) + commercial invoice and/or contract number,
date + VAT amount (NDS). If no tax is imposed on the goods or services, “BEZ NDS” must be
added.
2.100
2.120
2.121
2.122
2.123
2.125
2.126
Structured
CreditorReferenceInformation
Type
CodeOrProprietary
Code
Issuer
Reference
<Strd>
++++
[0..1]
Only 1 occurence of "Structured" is allowed.
<CdtrRefInf>
<Tp>
<CdOrPrtry>
<Cd>
+++++
++++++
+++++++
++++++++
Code
[1..1]
[1..1]
[1..1]
[1..1]
Accepted values is SCOR.
<Issr>
+++++++
Text
[0..1]
All other values will be set to SCOR .
ISO in case of ISO11649 reference number
<Ref>
++++++
Text
[1..1]
If Creditor Reference Information is used, Reference must be included.
Estonia:
When reference number is filled in Domestic Payment, the correctness of reference number is
checked against Estonian reference number standard. For information about Estonian
reference number standard see http://www.pangaliit.ee/en/settlements-andstandards/reference-number-of-the-invoice. ISO11649 reference number is accepted and the
correctness validated
Latvia, Lithuania:
No validations are performed on the value currently
Page 21 of 43
3. Customer Payment Status Report pain.002.001.03
Swedbank
ISO
Index
No.
0.0
1.0
1.1
1.2
1.3
9.1.12
9.1.13
9.1.14
2.0
2.1
Or
Message Item
Tag Name
Structural
Sequence
Customer Payment Status Report
GroupHeader
MessageIdentification
CreationDateTime
InitiatingParty
Identification
OrganisationIdentification
<CstmrPmtStsRpt>
<GrpHdr>
<MsgId>
<CreDtTm>
<InitgPty>
<Id>
<OrgId>
+
++
++
++
+++
++++
BICOrBEI
OriginalGroupInformationAndStatus
OriginalMessageIdentification
Type
Text
DateTime
Mult.
RULES
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
<BICOrBEI>
+++++
Identifier
[1..1]
<OrgnlGrpInfAndSts>
<OrgnlMsgId>
+
++
Text
[1..1]
[1..1]
2.2
OriginalMessageNameIdentification
<OrgnlMsgNmId>
++
Text
[1..1]
2.4
OriginalNumberOfTransactions
<OrgnlNbOfTxs>
++
Text
[1..1]
2.5
OriginalControlSum
<OrgnlCtrlSum>
++
Quantity
[0..1]
2.6
GroupStatus
<GrpSts>
++
Code
[0..1]
<GrpHdr>
+<MsgId> value from corresponding C2B pain.001 file
Specifies the original message name identifier to which the message refers, e.g.
pain.001.001.03
NumberOfTransactions from the Credit Transfer file
(pain.001.001.03)
ControlSum from the Credit Transfer file
(pain.001.001.03)
Status codes used by Swedbank:
RJCT - in case the whole file was rejected.
PART - Partially accepted, at least one payment in response is in ACSP status
ACSP - All preceding checks such as technical validation and customer profile were
successful within the whole file.
ACSC - Settlement on the debtor’s account has been completed for all payments in the
file.
GroupStatus is not sent with the final processing messages of Consolidated Payment,
International payment and European payment.
2.7
2.8
9.1.12
9.1.13
9.1.14
2.9
2.10
2.12
3.0
3.1
3.4
StatusReasonInformation
Originator
Identification
OrganisationIdentification
BICOrBEI
Reason
Code
<StsRsnInf>
<Orgtr>
<Id>
<OrgId>
<BICOrBEI>
<Rsn>
<Cd>
AdditionalInformation
<AddtlInf>
OriginalPaymentInformationAndStatus
<OrgnlPmtInfAndSts>
OriginalPaymentInformationIdentification <OrgnlPmtInfId>
PaymentInformationStatus
<PmtInfSts>
++
+++
++++
+++++
++++++
+++
++++
Identifier
Code
+++
+
++
Text
++
[0..n]
[0..1]
[0..1]
[1..1]
[0..1]
[0..1]
[1..1]
Swedbank Gateway error description.
Text
[0..n]
[0..n]
[1..1]
Code
[0..1]
Status codes used by Swedbank:
<PmtInfId> value from corresponding C2B pain.001 file
RJCT - in case the whole payment initiation block was rejected.
PART - Partially accepted
ACSP - All preceding checks such as technical validation and customer profile were
successful within the payment information block.
ACSC - Settlement on the debtor’s account has been completed for all payments in
payment information block.
Page 22 of 43
ISO
Index
No.
Or
3.5
3.6
9.1.12
9.1.13
9.1.14
3.7
3.8
3.10
3.15
3.17
3.18
3.19
Message Item
StatusReasonInformation
Originator
Identification
OrganisationIdentification
BICOrBEI
Reason
Code
AdditionalInformation
TransactionInformationAndStatus
OriginalInstructionIdentification
OriginalEndToEndIdentification
TransactionStatus
Tag Name
Structural
Sequence
<StsRsnInf>
<Orgtr>
<Id>
<OrgId>
<BICOrBEI>
<Rsn>
<Cd>
<AddtlInf>
<TxInfAndSts>
<OrgnlInstrId>
<OrgnlEndToEndId>
<TxSts>
++
+++
++++
+++++
++++++
+++
++++
+++
++
+++
+++
+++
Type
Identifier
Code
Text
Text
Text
Code
Mult.
[0..n]
[0..1]
[0..1]
[1..1]
[0..1]
[1..1]
[1..1]
[0..n]
[0..n]
[1..1]
[1..1]
[1..1]
RULES
Swedbank Gateway error description.
Status codes used by Swedbank:
RJCT - in case the transaction was rejected.
ACSP - All preceding checks such as technical validation and customer profile were
successfull.
ACSC – Settlement on the debtor’s account has been completed.
In case of Swedbank Payments (intrabank) successful checks such as technical
validation, customer profile and sufficient available balance produce ACSC status
immediately, ACSP will be skipped.
3.20
3.21
9.1.12
9.1.13
9.1.14
3.22
3.23
StatusReasonInformation
Originator
Identification
OrganisationIdentification
BICOrBEI
Reason
Code
<StsRsnInf>
<Orgtr>
<Id>
<OrgId>
<BICOrBEI>
<Rsn>
<Cd>
+++
++++
+++++
++++++
+++++++
++++
+++++
3.25
3.30
3.32
AdditionalInformation
AccountServicerReference
OriginalTransactionReference
<AddtlInf>
<AcctSvcrRef>
<OrgnlTxRef>
++++
+++
+++
<Amt>
<InstdAmt Ccy="AAA">
<ReqdExctnDt>
<Dbtr>
<Nm>
<DbtrAcct>
<Id>
<IBAN>
<Ccy>
<DbtrAgt>
<FinInstnId>
<BIC>
<CdtrAgt>
<FinInstnId>
<BIC>
++++
+++++
++++
++++
+++++
++++
+++++
++++++
+++++
++++
+++++
++++++
++++
+++++
++++++
3.34
3.35
3.41
3.121
9.1.0
3.122
1.1.0
1.1.1
1.1.11
3.123
6.1.0
6.1.1
3.125
6.1.0
6.1.1
6.1.2
6.1.3
6.1.4
6.1.6
{Or
Or}
Amount
InstructedAmount
RequestedExecutionDate
Debtor
Name
DebtorAccount
Identification
IBAN
Currency
DebtorAgent
FinancialInstitutionIdentification
BIC
CreditorAgent
FinancialInstitutionIdentification
BIC
ClearingSystemMemberIdentification
<ClrSysMmbId>
ClearingSystemIdentification<ClrSysId>
Code
<Cd>
MemberIdentification
<MmbId>
++++++
+++++++
++++++++
+++++++
Identifier
Code
Text
Text
[1..1]
[0..1]
[0..1]
[1..1]
[0..1]
[1..1]
[1..1]
[1..1]
[0..1]
[0..1]
Swedbank Gateway error description.
Not reported for Consolidated payments
Identifier
[0..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[0..1]
[1..1]
[1..1]
Code
Text
[1..1]
[0..1]
[1..1]
[1..1]
Amount
DateTime
Text
Identifier
Code
Identifier
Page 23 of 43
ISO
Index
No.
3.127
9.1.0
3.128
1.1.0
1.1.1
1.1.2
1.1.3
Or
{Or
Or}
Message Item
Creditor
Name
CreditorAccount
Identification
IBAN
Other
Identification
Tag Name
Structural
Sequence
<Cdtr>
<Nm>
<CdtrAcct>
<Id>
<IBAN>
<Othr>
<Id>
++++
+++++
++++
+++++
++++++
++++++
+++++++
Type
Text
Identifier
Text
Page 24 of 43
Mult.
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
RULES
3.1 Statuses in Pain002
4. Examples
4.1 Domestic Payment Estonia, 2 payments:
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03">
<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>201111251</MsgId>
<CreDtTm>2013-08-30T11:16:58.696</CreDtTm>
<NbOfTxs>2</NbOfTxs>
<CtrlSum>1</CtrlSum>
<InitgPty>
<Nm>ETTEVÕTE AS</Nm>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>PMTID005</PmtInfId>
<PmtMtd>TRF</PmtMtd>
<NbOfTxs>2</NbOfTxs>
<PmtTpInf>
<SvcLvl>
<Cd>SEPA</Cd>
</SvcLvl>
</PmtTpInf>
<ReqdExctnDt>2013-09-26</ReqdExctnDt>
<Dbtr>
<Nm>ETTEVÕTE AS</Nm>
<PstlAdr>
<Ctry>EE</Ctry>
<AdrLine>Metsa 8, Tallinn</AdrLine>
</PstlAdr>
<Id>
<OrgId>
<Othr>
<Id>123456789</Id>
</Othr>
</OrgId>
</Id>
</Dbtr>
<DbtrAcct>
<Id>
<IBAN>EE942200221017496868</IBAN>
</Id>
<Ccy>EUR</Ccy>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<BIC>HABAEE2X</BIC>
</FinInstnId>
</DbtrAgt>
<ChrgBr>SLEV</ChrgBr>
<CdtTrfTxInf>
<PmtId>
<InstrId>115</InstrId>
<EndToEndId>327</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="EUR">0.15</InstdAmt>
</Amt>
<Cdtr>
<Nm>FIRMA AS</Nm>
<PstlAdr>
<Ctry>EE</Ctry>
<AdrLine>Leevikese 5,Tallinn</AdrLine>
</PstlAdr>
<Id>
<OrgId>
<Othr>
<Id>100000009</Id>
</Othr>
</OrgId>
</Id>
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>EE572200221017496855</IBAN>
</Id>
</CdtrAcct>
<RmtInf>
<Strd>
<CdtrRefInf>
<Tp>
<CdOrPrtry>
<Cd>SCOR</Cd>
</CdOrPrtry>
</Tp>
<Ref>8806947</Ref>
</CdtrRefInf>
</Strd>
</RmtInf>
</CdtTrfTxInf>
<CdtTrfTxInf>
<PmtId>
<InstrId>116</InstrId>
<EndToEndId>328</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="EUR">0.85</InstdAmt>
</Amt>
<Cdtr>
<Nm>Mari Ööbik</Nm>
<PstlAdr>
<Ctry>EE</Ctry>
<AdrLine>Pronksi 12, Tallinn</AdrLine>
</PstlAdr>
<Id>
<PrvtId>
<Othr>
<Id>48606112009</Id>
</Othr>
</PrvtId>
</Id>
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>EE142200221000127063</IBAN>
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>Here enter payment details</Ustrd>
<Strd>
<CdtrRefInf>
<Tp>
<CdOrPrtry>
<Cd>SCOR</Cd>
</CdOrPrtry>
</Tp>
<Ref>88069474660</Ref>
</CdtrRefInf>
</Strd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
4.2 International Payment example (express payment in USD, via correspondent bank):
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03">
<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>201111258</MsgId>
<CreDtTm>2013-09-27T11:16:58.696</CreDtTm>
<NbOfTxs>1</NbOfTxs>
<CtrlSum>5</CtrlSum>
<InitgPty>
<Nm>ETTEVÕTE AS</Nm>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>PMTID0051</PmtInfId>
<PmtMtd>TRF</PmtMtd>
<NbOfTxs>1</NbOfTxs>
<PmtTpInf>
<SvcLvl>
<Cd>SDVA</Cd>
</SvcLvl>
</PmtTpInf>
<ReqdExctnDt>2013-11-14</ReqdExctnDt>
<Dbtr>
<Nm>ETTEVÕTE AS</Nm>
<PstlAdr>
<Ctry>EE</Ctry>
<AdrLine>Metsa 2, Tallinn</AdrLine>
</PstlAdr>
</Dbtr>
<DbtrAcct>
<Id>
<IBAN>EE942200221017496868</IBAN>
</Id>
<Ccy>USD</Ccy>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<BIC>HABAEE2X</BIC>
</FinInstnId>
</DbtrAgt>
<ChrgBr>DEBT</ChrgBr>
<CdtTrfTxInf>
<PmtId>
<InstrId>12345</InstrId>
<EndToEndId>323009</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="USD">5</InstdAmt>
</Amt>
<IntrmyAgt1>
<FinInstnId>
<BIC>BKTRUS33</BIC>
<Nm>Deutche Bank Trust</Nm>
<PstlAdr>
<AdrLine>New York 60 Wall Street</AdrLine>
</PstlAdr>
</FinInstnId>
</IntrmyAgt1>
<IntrmyAgt1Acct>
<Id>
<Othr>
<Id>1234567890</Id>
</Othr>
</Id>
</IntrmyAgt1Acct>
<CdtrAgt>
<FinInstnId>
<BIC>SWEDSESS</BIC>
<Nm>Swedbank AB Sweden</Nm>
<PstlAdr>
<AdrLine>Stockholm Brunkebergstorg 8</AdrLine>
</PstlAdr>
</FinInstnId>
</CdtrAgt>
<CdtrAgtAcct>
<Id>
<Othr>
<Id>987654321</Id>
</Othr>
</Id>
</CdtrAgtAcct>
<Cdtr>
<Nm>Beneficiary Test1</Nm>
<PstlAdr>
<Ctry>SE</Ctry>
<AdrLine>Stockholm Ridmansgatan 3F</AdrLine>
</PstlAdr>
</Cdtr>
<CdtrAcct>
<Id>
<Othr>
<Id>56949203947</Id>
</Othr>
</Id>
</CdtrAcct>
<RgltryRptg>
<Dtls>
<Ctry>SE</Ctry>
<Cd>310</Cd>
</Dtls>
</RgltryRptg>
<RmtInf>
<Ustrd>Test payment in USD dollars with express payment type</Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
4.3 European Payment example (Sepa Credit Transfer):
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03">
<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>201111258</MsgId>
<CreDtTm>2013-08-30T11:16:58.696</CreDtTm>
<NbOfTxs>1</NbOfTxs>
<CtrlSum>0.65</CtrlSum>
<InitgPty>
<Nm>ETTEVÕTE AS</Nm>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>PMTID0051</PmtInfId>
<PmtMtd>TRF</PmtMtd>
<NbOfTxs>1</NbOfTxs>
<PmtTpInf>
<SvcLvl>
<Cd>SEPA</Cd>
</SvcLvl>
</PmtTpInf>
<ReqdExctnDt>2013-09-27</ReqdExctnDt>
<Dbtr>
<Nm>ETTEVÕTE AS</Nm>
<PstlAdr>
<Ctry>EE</Ctry>
<AdrLine>Metsa 2, Tallinn</AdrLine>
</PstlAdr>
</Dbtr>
<DbtrAcct>
<Id>
<IBAN>EE942200221017496868</IBAN>
</Id>
<Ccy>EUR</Ccy>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<BIC>HABAEE2X</BIC>
</FinInstnId>
</DbtrAgt>
<ChrgBr>SLEV</ChrgBr>
<CdtTrfTxInf>
<PmtId>
<InstrId>123456</InstrId>
<EndToEndId>323009</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="EUR">0.65</InstdAmt>
</Amt>
<CdtrAgt>
<FinInstnId>
<BIC>NDEAFIHH</BIC>
</FinInstnId>
</CdtrAgt>
<Cdtr>
<Nm>Company AB</Nm>
<PstlAdr>
<Ctry>FI</Ctry>
<AdrLine>HELSINKI</AdrLine>
</PstlAdr>
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>FI0524001800005605</IBAN>
</Id>
</CdtrAcct>
<RgltryRptg>
<Dtls>
<Ctry>FI</Ctry>
<Cd>999</Cd>
</Dtls>
</RgltryRptg>
<RmtInf>
<Ustrd>Payment details</Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
4.4 Consolidated Payment example
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03">
<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>201111251</MsgId>
<CreDtTm>2013-08-30T11:16:58.696</CreDtTm>
<NbOfTxs>3</NbOfTxs>
<CtrlSum>0.6</CtrlSum>
<InitgPty>
<Nm>AS MKONTSERN</Nm>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>PMTID005</PmtInfId>
<PmtMtd>TRF</PmtMtd>
<NbOfTxs>3</NbOfTxs>
<PmtTpInf>
<SvcLvl>
<Cd>SEPA</Cd>
</SvcLvl>
<CtgyPurp>
<Cd>SALA</Cd>
</CtgyPurp>
</PmtTpInf>
<ReqdExctnDt>2013-10-01</ReqdExctnDt>
<Dbtr>
<Nm>AS MKONTSERN</Nm>
<PstlAdr>
<Ctry>EE</Ctry>
<AdrLine>Liivalaia, Tallinn</AdrLine>
</PstlAdr>
</Dbtr>
<DbtrAcct>
<Id>
<IBAN>EE892200221000214468</IBAN>
</Id>
<Ccy>EUR</Ccy>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<BIC>HABAEE2X</BIC>
</FinInstnId>
</DbtrAgt>
<ChrgBr>SLEV</ChrgBr>
<CdtTrfTxInf>
<PmtId>
<InstrId>1</InstrId>
<EndToEndId>01</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="EUR">0.10</InstdAmt>
</Amt>
<Cdtr>
<Nm>MARI METS</Nm>
<PstlAdr>
<Ctry>EE</Ctry>
<AdrLine>Leevikese 5,Tallinn</AdrLine>
</PstlAdr>
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>EE142200221000127063</IBAN>
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>september salary</Ustrd>
</RmtInf>
</CdtTrfTxInf>
<CdtTrfTxInf>
<PmtId>
<InstrId>2</InstrId>
<EndToEndId>02</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="EUR">0.2</InstdAmt>
</Amt>
<Cdtr>
<Nm>MAGNUS MERI</Nm>
<PstlAdr>
<Ctry>EE</Ctry>
<AdrLine>Siinseal, Tallinn</AdrLine>
</PstlAdr>
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>EE602200221000235748</IBAN>
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>september salary</Ustrd>
</RmtInf>
</CdtTrfTxInf>
<CdtTrfTxInf>
<PmtId>
<InstrId>3</InstrId>
<EndToEndId>03</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="EUR">0.3</InstdAmt>
</Amt>
<Cdtr>
<Nm>AADU KALA</Nm>
<PstlAdr>
<Ctry>EE</Ctry>
<AdrLine>Leevikese 5,Tallinn</AdrLine>
</PstlAdr>
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>EE602200221000235748</IBAN>
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>september salary</Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
4.5 International payment in Russian roubles example (via correspondent bank)
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03">
<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>201111258</MsgId>
<CreDtTm>2013-09-27T11:16:58.696</CreDtTm>
<NbOfTxs>1</NbOfTxs>
<CtrlSum>5</CtrlSum>
<InitgPty>
<Nm>ETTEVÕTE AS</Nm>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>PMTID0052</PmtInfId>
<PmtMtd>TRF</PmtMtd>
<NbOfTxs>1</NbOfTxs>
<PmtTpInf>
<SvcLvl>
<Cd>NURG</Cd>
</SvcLvl>
</PmtTpInf>
<ReqdExctnDt>2013-11-15</ReqdExctnDt>
<Dbtr>
<Nm>ETTEVÕTE AS</Nm>
<PstlAdr>
<Ctry>EE</Ctry>
<AdrLine>Metsa 2, Tallinn</AdrLine>
</PstlAdr>
</Dbtr>
<DbtrAcct>
<Id>
<IBAN>EE942200221017496868</IBAN>
</Id>
<Ccy>EUR</Ccy>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<BIC>HABAEE2X</BIC>
</FinInstnId>
</DbtrAgt>
<ChrgBr>DEBT</ChrgBr>
<CdtTrfTxInf>
<PmtId>
<InstrId>133456</InstrId>
<EndToEndId>323011</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy="RUB">5</InstdAmt>
</Amt>
<IntrmyAgt1>
<FinInstnId>
<Nm>OAO AKB Probiznesbank, g.Moskva, 044525986.30101810600000000986</Nm>
</FinInstnId>
</IntrmyAgt1>
<CdtrAgt>
<FinInstnId>
<Nm>Vernadskoe otdelenie 9038, 303xxxxxxxxxxxxxxxxx</Nm>
</FinInstnId>
</CdtrAgt>
<Cdtr>
<Nm>INN1234567891.KPP123456001 OOO Severnyy Tr/e/vel</Nm>
</Cdtr>
<CdtrAcct>
<Id>
<Othr>
<Id>41234810487623900000</Id>
</Othr>
</Id>
</CdtrAcct>
<RgltryRptg>
<Dtls>
<Ctry>RU</Ctry>
<Cd>310</Cd>
</Dtls>
</RgltryRptg>
<RmtInf>
<Ustrd>(VO20100) predoplata za transportnye uslugi, schet no.5 ot 15.10.2013, NDS 5.00 RUB</Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
4.6 Payment status report pain.002.001.03 example (accepted)
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.03">
<CstmrPmtStsRpt>
<GrpHdr>
<MsgId>20131115-093012731-466-1816/2325</MsgId>
<CreDtTm>2013-11-22T15:50:34</CreDtTm>
<InitgPty>
<Id>
<OrgId>
<BICOrBEI>HABAEE2X</BICOrBEI>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<OrgnlGrpInfAndSts>
<OrgnlMsgId>201111251</OrgnlMsgId>
<OrgnlMsgNmId>pain.001.001.03</OrgnlMsgNmId>
<OrgnlNbOfTxs>1</OrgnlNbOfTxs>
<OrgnlCtrlSum>1.6</OrgnlCtrlSum>
<GrpSts>ACSC</GrpSts>
</OrgnlGrpInfAndSts>
<OrgnlPmtInfAndSts>
<OrgnlPmtInfId>PMTID006</OrgnlPmtInfId>
<PmtInfSts>ACSC</PmtInfSts>
<TxInfAndSts>
<OrgnlInstrId>315</OrgnlInstrId>
<OrgnlEndToEndId>527</OrgnlEndToEndId>
<TxSts>ACSC</TxSts>
<OrgnlTxRef>
<Amt>
<InstdAmt Ccy="EUR">1.60</InstdAmt>
</Amt>
<ReqdExctnDt>2013-11-22</ReqdExctnDt>
<Dbtr>
<Nm>ETTEVÕTE AS</Nm>
</Dbtr>
<DbtrAcct>
<Id>
<IBAN>EE942200221017496868</IBAN>
</Id>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<BIC>HABAEE2X</BIC>
</FinInstnId>
</DbtrAgt>
<CdtrAgt>
<FinInstnId>
<BIC>HABAEE2X</BIC>
</FinInstnId>
</CdtrAgt>
<Cdtr>
<Nm>FIRMA AS</Nm>
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>EE572200221017496855</IBAN>
</Id>
</CdtrAcct>
</OrgnlTxRef>
</TxInfAndSts>
</OrgnlPmtInfAndSts>
</CstmrPmtStsRpt>
</Document>
4.7 Payment status report pain.002.001.03 example (rejected)
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.03">
<CstmrPmtStsRpt>
<GrpHdr>
<MsgId>20131101-090903211-1701-13682/10868</MsgId>
<CreDtTm>2013-11-22T13:22:12</CreDtTm>
<InitgPty>
<Id>
<OrgId>
<BICOrBEI>HABAEE2X</BICOrBEI>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<OrgnlGrpInfAndSts>
<OrgnlMsgId>201111251</OrgnlMsgId>
<OrgnlMsgNmId>pain.001.001.03</OrgnlMsgNmId>
<OrgnlNbOfTxs>1</OrgnlNbOfTxs>
<OrgnlCtrlSum>1.5</OrgnlCtrlSum>
<GrpSts>RJCT</GrpSts>
</OrgnlGrpInfAndSts>
<OrgnlPmtInfAndSts>
<OrgnlPmtInfId>PMTID109</OrgnlPmtInfId>
<PmtInfSts>RJCT</PmtInfSts>
<StsRsnInf>
<Rsn>
<Cd>BE01</Cd>
</Rsn>
<AddtlInf>The account number and the name do not coincide!</AddtlInf>
</StsRsnInf>
<TxInfAndSts>
<OrgnlInstrId>1150006</OrgnlInstrId>
<OrgnlEndToEndId>528</OrgnlEndToEndId>
<TxSts>RJCT</TxSts>
<StsRsnInf>
<Rsn>
<Cd>BE01</Cd>
</Rsn>
<AddtlInf>The account number and the name do not coincide!</AddtlInf>
</StsRsnInf>
<OrgnlTxRef>
<Amt>
<InstdAmt Ccy="EUR">1.50</InstdAmt>
</Amt>
<ReqdExctnDt>2013-11-22</ReqdExctnDt>
<Dbtr>
<Nm>ETTEVÕTE AS</Nm>
</Dbtr>
<DbtrAcct>
<Id>
<IBAN>EE942200221017496868</IBAN>
</Id>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<BIC>HABAEE2X</BIC>
</FinInstnId>
</DbtrAgt>
<Cdtr>
</Cdtr>
<CdtrAcct>
</CdtrAcct>
</OrgnlTxRef>
</TxInfAndSts>
</OrgnlPmtInfAndSts>
</CstmrPmtStsRpt>
</Document>
<Nm>WRONGNAME AS</Nm>
<Id>
</Id>
<IBAN>EE572200221017496855</IBAN>