ISO Message Implementation Guide for Payment Initiation

Transcription

1 ISO Message Implementation Guide for Payment Initiation Pain001 Pain002 Version: 1.7 Issue date: 12 January 2017 Author: Swedbank

2 Table of Contents 1. Introduction 2. Customer Credit Transfer Initiation V3 pain Customer Payment Status Report pain Statuses in Pain 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 example (accepted) 4.7 Payment status report pain example (rejected)

3 Revision history Version Changes Date 1.0 First version of the MIG, main focus on EE local Banking Association MIG Revision history added Allowed characters and file encoding described in more detail. InstructionIdentification will become optional starting from , 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 Pain.002 GroupStatus, PaymentInformationStatus and TransactionStatus updated 1.2 Express payment currencies list updated InstructionIdentification remains mandatory for Consolidated Payment 1.3 Payment type definition page added to Introduction Payment type detection rules explained in detail

4 Version Changes Date 1.4 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 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 site Possibility to provide structured details for consolidated payments will appear in December, Complemented list of countries where SEPA payments can be made

5 Version Changes Date 1.6 Originator added to pain002 in transaction level when payment is rejected Instruction ID is excluded from character validation Link replacement for regulatory reporting codes in Latvia Replaced example 4.3 with Latvian SCT example (regulatory reporting tags) General wording corrections

6 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 used to initiate a credit transfer -Pain used to report on the status of a credit transfer initiation This document should be read together with the ISO 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 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: 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 / -? : ( )., ' + 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 & < replaced with < " replaced with " > replaced with > ' replaced with &apos; Characters for domestic payments references, identifications and identifiers 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

7 Description on the columns: ISO Index NO Number that refers to the corresponding description in the ISO XML Message Definition Report. This report can be found at under Catalogue of ISO messages Or indicates that only one of several elements may be presented Message Item - Element name used in ISO XML Message Definition Report. Tag Name - Name that identifies an element within an XML message. Is based on the ISO 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.

8 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 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 Kingdom. Payments within one Baltic country are considered as domestic payments.

9 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 Domestic*, European payment International non- European (express currency) International non- European (other currency) STEP1 Local Instrument/Proprietary=NORM NORMAL NORMAL NORMAL NORMAL STEP2 Local Instrument/Proprietary=HIGH NORMAL URGENT URGENT URGENT STEP3 Local Instrument/Proprietary=EXPR NORMAL URGENT EXPRESS URGENT STEP4 Service Level/Code=SEPA NORMAL NORMAL NORMAL NORMAL STEP5 Service Level/Code=SEPA& Local Instrument/Code=ONCL NORMAL NORMAL NORMAL NORMAL STEP6 Service Level/Code=SEPA& Local Instrument/Code=SDCL NORMAL URGENT NORMAL NORMAL STEP7 Service Level/Code=NURG NORMAL NORMAL NORMAL NORMAL STEP8 Service Level/Code=URGP NORMAL URGENT URGENT URGENT STEP9 Service Level/Code=SDVA NORMAL URGENT EXPRESS URGENT 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 There should be taken Intrabank payment rules in 2015.

10 2. Customer Credit Transfer Initiation V3 pain ISO Index No. Or Message Item Tag Name Structural Sequence ISO Type Mult. Customer RULES Customer Credit Transfer Initiation <CstmrCdtTrfInitn GroupHeader <GrpHdr> + [1..1] 1.1 MessageIdentification <MsgId> ++ Text [1..1] This Id will be stored for 90 days and will be used for duplicate control. Will be returned in status report 1.2 CreationDateTime <CreDtTm> ++ DateTime [1..1] 1.6 NumberOfTransactions <NbOfTxs> ++ Text [1..1] Swedbank checks the given value with the total number of transactions in the entire message. 1.7 ControlSum <CtrlSum> ++ Quantity [0..1] If given, Swedbank checks the given value with the total amount of all individual transactions in the entire message. 1.8 InitiatingParty <InitgPty> ++ [1..1] Name <Nm> +++ Text [0..1] Limited to 70 characters in length. Ignored if it's the same as Debtor Identification +++ [0..1] Accepted but not used at the moment {Or OrganisationIdentification <OrgId> ++++ [1..1] Other <Othr> [1..1] Only one occurence is allowed, rest will be ignored Identification Text [1..1] SchemeName <SchmeNm> [0..1] Code <Cd> Code [1..1] Accepted code: BANK Other code values will be set to 'Bank' Or} PrivateIdentification <PrvtId> ++++ [1..1] Either DateAndPlaceOfBirth or one occurence of Other is allowed {{Or DateAndPlaceOfBirth <DtAndPlcOfBirth> [1..1] BirthDate <BirthDt> DateTime [1..1] CityOfBirth <CityOfBirth> Text [1..1] CountryOfBirth <CtryOfBirth> Code [1..1] Or}} Other <Othr> [1..1] Only one occurence is allowed, rest will be ignored Identification Text [1..1] SchemeName <SchmeNm> [0..1] Code <Cd> Code [1..1] 2.0 PaymentInformation <PmtInf> + [1..n] 2.1 PaymentInformationIdentification <PmtInfId> ++ Text [1..1] Recommended to be unique. Will be returned in status report. 2.2 PaymentMethod <PmtMtd> ++ Code [1..1] Accepted code: TRF Other code values will be set to 'TRF' Swedbank Page 10 of 45

11 ISO Index No. Or Message Item Tag Name Structural Sequence ISO Type Mult. Customer RULES 2.6 PaymentTypeInformation <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.8 ServiceLevel <SvcLvl> +++ [0..1] 2.9 Code <Cd> ++++ Code [1..1] Accepted codes: NURG 2.11 LocalInstrument <LclInstrm> +++ [0..1] 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.12 {Or Code <Cd> ++++ 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 11 of 45

12 ISO Index No. Or Message Item Tag Name Structural Sequence ISO Type Mult. Customer RULES 2.13 Or} Proprietary <Prtry> ++++ Text [1..1] 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 CategoryPurpose <CtgyPurp> +++ [0..1] Other values will be set to NORM 2.15 Code <Cd> ++++ Code [1..1] 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 started in December, On camt messages Consolidated payment indicator is <BkTxCd><Prtry><Cd>MP 2,17 RequestedExecutionDate <ReqdExctnDt> ++ DateTime [1..1] Cannot be more than 365 days in future. Yesterday's date is converted to Current Date, older dates are not accepted Debtor <Dbtr> ++ [1..1] Name <Nm> +++ 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 PostalAddress <PstlAdr> +++ [0..1] Accepted but not used. The Debtor's postal address will be taken from Swedbank's customer database Country <Ctry> ++++ Code [0..1] Accepted but not used AddressLine <AdrLine> ++++ Text [0..2] Accepted but not used. Only 2 occurences allowed, the rest will be ignored Identification +++ [0..1] {Or OrganisationIdentification <OrgId> ++++ [1..1] 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 {{Or BICOrBEI <BICOrBEI> Identifier [1..1] Either BIC or BEI or one occurence of "Other" is allowed Or}} Other <Othr> [1..1] Only one occurence is allowed, rest will be ignored Identification Text [1..1] SchemeName <SchmeNm> [0..1] Page 12 of 45

13 ISO Index No. Or Message Item Tag Name Structural Sequence ISO Type Mult Code <Cd> Code [1..1] Customer RULES Or} PrivateIdentification <PrvtId> ++++ [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 {{Or DateAndPlaceOfBirth <DtAndPlcOfBirth> [1..1] BirthDate <BirthDt> DateTime [1..1] CityOfBirth <CityOfBirth> Text [1..1] CountryOfBirth <CtryOfBirth> Code [1..1] Or}} Other <Othr> [1..1] Only one occurence is allowed, rest will be ignored Identification Text [1..1] SchemeName <SchmeNm> [0..1] Code <Cd> Code [1..1] 2.20 DebtorAccount <DbtrAcct> ++ [1..1] Only IBAN is allowed Identification +++ [1..1] IBAN <IBAN> ++++ Identifier [1..1] Currency <Ccy> +++ Code [0..1] Accepted but not used DebtorAgent <DbtrAgt> ++ [1..1] FinancialInstitutionIdentification <FinInstnId> +++ [1..1] BIC <BIC> ++++ Identifier [0..1] 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 Name <Nm> ++++ Text [0..1] 2.23 UltimateDebtor <UltmtDbtr> ++ [0..1] Accepted but not used. Forward to Beneficiary Bank when it's possible Name <Nm> +++ Text [0..1] Limited to 70 characters in length Identification +++ [0..1] {Or OrganisationIdentification <OrgId> ++++ [1..1] Either "BIC" or "BEI" or one occurence of "other" is allowed {{Or BICOrBEI <BICOrBEI> Identifier [1..1] Or}} Other <Othr> [1..1] Identification Text [1..1] SchemeName <SchmeNm> [0..1] Either Code or Proprietary must be filled {{Or 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. Page 13 of 45

14 ISO Index No. Or Message Item Tag Name Structural Sequence ISO Type Mult. Customer RULES Or}} Proprietary <Prtry> Text [1..1] Might be used for European cross-border payments. It is ignored in case of domestic payments Or} PrivateIdentification <PrvtId> ++++ [1..1] Either DateAndPlaceOfBirth or one occurence of Other is allowed {{Or DateAndPlaceOfBirth <DtAndPlcOfBirth> [1..1] BirthDate <BirthDt> DateTime [1..1] CityOfBirth <CityOfBirth> Text [1..1] CountryOfBirth <CtryOfBirth> Code [1..1] Or}} Other <Othr> [1..1] Identification Text [1..1] SchemeName <SchmeNm> [0..1] Either Code or Proprietary must be filled {{Or 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 Or}} Proprietary <Prtry> Text [1..1] Might be used for European cross-border payments. It is ignored in case of domestic payments ChargeBearer <ChrgBr> ++ Code [0..1] Strongly recommended to use at this PaymentInformation (PmtInf) level CreditTransferTransactionInformation <CdtTrfTxInf> ++ [1..n] 2.28 PaymentIdentification <PmtId> +++ [1..1] 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.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 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 PaymentTypeInformation <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. Page 14 of 45

15 ISO Index No. Or Message Item Tag Name Structural Sequence ISO Type Mult ServiceLevel <SvcLvl> ++++ [0..1] Customer RULES 2.34 Code <Cd> 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 LocalInstrument <LclInstrm> ++++ [0..1] 2.37 {Or Code <Cd> 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 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 CategoryPurpose <CtgyPurp> ++++ [0..1] 2.40 Code <Cd> Code [1..1] Indicator for Consolidated payment functionality should only be set at Payment information level, see 2.14<CategoryPurpose><Cd> 2.42 Amount <Amt> +++ [1..1] Page 15 of 45

16 ISO Index No. Or Message Item Tag Name Structural Sequence 2.43 InstructedAmount <InstdAmt Ccy="AAA"> ISO Type Mult. Customer RULES ++++ 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 ChargeBearer <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 2.70 UltimateDebtor <UltmtDbtr> +++ [0..1] Only used at PmtInf level. If missing or not valid code, will be treated as SHAR Name <Nm> ++++ Text [0..1] Limited to 70 characters in length Identification ++++ [0..1] {Or OrganisationIdentification <OrgId> [1..1] Either "BIC" or "BEI" or one occurence of "other" is allowed {{Or BICOrBEI <BICOrBEI> Identifier [1..1] Or}} Other <Othr> [1..1] Identification Text [1..1] SchemeName <SchmeNm> [0..1] Either Code or Proprietary must be filled {{Or 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 Or}} Proprietary <Prtry> Text [1..1] Might be used for European cross-border payments. It is ignored in case of domestic payments Or} PrivateIdentification <PrvtId> [1..1] Either "DateAndPlaceOfBirth" or one occurence of "Other is allowed" {{Or DateAndPlaceOfBirth <DtAndPlcOfBirth> [1..1] BirthDate <BirthDt> DateTime [1..1] CityOfBirth <CityOfBirth> Text [1..1] CountryOfBirth <CtryOfBirth> Code [1..1] Or}} Other <Othr> [1..1] Identification Text [1..1] SchemeName <SchmeNm> [0..1] Either Code or Proprietary must be filled Page 16 of 45

17 ISO Index No. Or Message Item Tag Name Structural Sequence ISO Type Mult. Customer RULES {{Or 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 Or}} Proprietary <Prtry> Text [1..1] Might be used for European cross-border payments. It is ignored in case of domestic payments IntermediaryAgent1 <IntrmyAgt1> +++ [0..1] Only valid for for International non-european Payments, when applicable. Used to indicate correspondent bank of Creditor Agent FinancialInstitutionIdentification <FinInstnId> ++++ [1..1] BIC <BIC> Identifier [0..1] Name <Nm> Text [0..1] 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) PostalAddress <PstlAdr> [0..1] Country <Ctry> Code [0..1] AddressLine <AdrLine> Text [0..2] Only two occurences accepted 2.72 IntermediaryAgent1Account <IntrmyAgt1Acct> +++ [0..1] Identification ++++ [1..1] {Or IBAN <IBAN> Identifier [1..1] Or} Other <Othr> [1..1] Identification Text [1..1] 2.73 IntermediaryAgent2 <IntrmyAgt2> +++ [0..1] Only valid for for International non-european payments, when applicable FinancialInstitutionIdentification <FinInstnId> ++++ [1..1] BIC <BIC> Identifier [0..1] Name <Nm> Text [0..1] Only 70 characters PostalAddress <PstlAdr> [0..1] Country <Ctry> Code [0..1] AddressLine <AdrLine> Text [0..2] Only two occurences accepted 2.74 IntermediaryAgent2Account <IntrmyAgt2Acct> +++ [0..1] Identification ++++ [1..1] {Or IBAN <IBAN> Identifier [1..1] Or} Other <Othr> [1..1] Identification Text [1..1] 2.77 CreditorAgent <CdtrAgt> +++ [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 was mandatory untill Page 17 of 45

18 ISO Index No. Or Message Item Tag Name Structural Sequence ISO Type Mult. Customer RULES FinancialInstitutionIdentification <FinInstnId> ++++ [1..1] BIC <BIC> Identifier [0..1] In case of European payments BIC was mandatory until ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] Accepted but not used. Currently not supported in Swedbank ClearingSystemIdentification <ClrSysId> [0..1] Code <Cd> Code [1..1] MemberIdentification <MmbId> Text [1..1] Name <Nm> Text [0..1] 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 PostalAddress <PstlAdr> [0..1] Country <Ctry> Code [0..1] AddressLine <AdrLine> Text [0..2] Only two occurences accepted 2.78 CreditorAgentAccount <CdtrAgtAcct> +++ [0..1] Identification ++++ [1..1] {Or IBAN <IBAN> Identifier [1..1] Or} Other <Othr> [1..1] Identification Text [1..1] 2.79 Creditor <Cdtr> +++ [1..1] Name <Nm> ++++ Text [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) PostalAddress <PstlAdr> ++++ [0..1] Forward if possible Country <Ctry> Code [0..1] AddressLine <AdrLine> Text [0..2] Only two occurences accepted, total length max 70 characters Identification ++++ [0..1] {Or OrganisationIdentification <OrgId> [1..1] {{Or BICOrBEI <BICOrBEI> Identifier [1..1] Either BIC or BEI or one occurence of "Other" is allowed Or}} Other <Othr> [1..1] Identification Text [1..1] SchemeName <SchmeNm> [0..1] Either Code or Proprietary must be filled Page 18 of 45

19 ISO Index No. Or Message Item Tag Name Structural Sequence ISO Type Mult. Customer RULES {{Or 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 Or}} Proprietary <Prtry> Text [1..1] Might be used for European cross-border payments. It is ignored in case of domestic payments Or} PrivateIdentification <PrvtId> [1..1] Either DateAndPlaceOfBirth or one occurence of "Other" is allowed {{Or DateAndPlaceOfBirth <DtAndPlcOfBirth> [1..1] BirthDate <BirthDt> DateTime [1..1] CityOfBirth <CityOfBirth> Text [1..1] CountryOfBirth <CtryOfBirth> Code [1..1] Or}} Other <Othr> [1..1] Identification Text [1..1] SchemeName <SchmeNm> [0..1] Either Code or Proprietary must be filled {{Or Code <Cd> Code [1..1] 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 Or}} Proprietary <Prtry> Text [1..1] Might be used for European cross-border payments. It is ignored in case of domestic payments CountryOfResidence <CtryOfRes> ++++ Code [0..1] 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 2.80 CreditorAccount <CdtrAcct> +++ [1..1] Identification ++++ [1..1] {Or IBAN <IBAN> Identifier [1..1] In case of Domestic and European payment IBAN is mandatory Or} Other <Othr> [1..1] Identification Text [1..1] RUB payment - a 20-digit number, the digits 6-8 of which are UltimateCreditor <UltmtCdtr> +++ [0..1] Only forwarded with Domestic and European payment (except payment with type urgent) Name <Nm> ++++ Text [0..1] Only 70 character Identification ++++ [0..1] {Or OrganisationIdentification <OrgId> [1..1] Either "BIC" or "BEI" or one occurence of "other" is allowed {{Or BICOrBEI <BICOrBEI> Identifier [1..1] Or}} Other <Othr> [1..1] Only one occurence is allowed, rest will be ignored Identification Text [1..1] SchemeName <SchmeNm> [0..1] Either Code or Proprietary must be filled Page 19 of 45

20 ISO Index No. Or Message Item Tag Name Structural Sequence ISO Type Mult. Customer RULES {{Or 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 Or}} Proprietary <Prtry> Text [1..1] Might be used for European cross-border payments. It is ignored in case of domestic payments Or} PrivateIdentification <PrvtId> [1..1] Either "DateAndPlaceOfBirth" or one occurence of "Other is allowed" {{O DateAndPlaceOfBirth <DtAndPlcOfBirth> [1..1] BirthDate <BirthDt> DateTime [1..1] CityOfBirth <CityOfBirth> Text [1..1] CountryOfBirth <CtryOfBirth> Code [1..1] Or}} Other <Othr> [1..1] Identification Text [1..1] SchemeName <SchmeNm> [0..1] Either Code or Proprietary must be filled {{O 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 Or}} Proprietary <Prtry> Text [1..1] Might be used for European cross-border payments. It is ignored in case of domestic payments Purpose <Purp> +++ [0..1] 2.87 Code <Cd> ++++ Code [1..1] Code according to ISO20022 external code set RegulatoryReporting <RgltryRptg> +++ 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 Details <Dtls> ++++ [0..2] Latvia: Only two occurences are valid the rest are ignored Type <Tp> Text [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) Country <Ctry> Code [0..1] Country ISO code (ISO 3166, Alpha-2 code), see nts.htm Page 20 of 45

21 ISO Index No. Or Message Item Tag Name Structural Sequence ISO Type Mult. Customer RULES Code <Cd> Text [1..1] Latvia: Code of the balance of payment. For appropriate code see: ttp://likumi.lv/doc.php?id=258772#piel Information <Inf> Text [0..1] If tag <Tp> (11.1.5) contains code EKK then the code value should contain budget income code 2.98 RemittanceInformation <RmtInf> +++ [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. 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 21 of 45

22 ISO Index No. Or Message Item Tag Name Structural Sequence ISO Type Mult. Customer RULES 2.99 Unstructured <Ustrd> ++++ Text [0..1] Only 1 occurence allowed with maximum 140 Characters Structured <Strd> ++++ [0..1] Only 1 occurence of "Structured" is allowed CreditorReferenceInformation <CdtrRefInf> [1..1] Type <Tp> [1..1] CodeOrProprietary <CdOrPrtry> [1..1] Code <Cd> Code [1..1] Accepted values is SCOR. All other values will be set to SCOR Issuer <Issr> Text [0..1] ISO in case of ISO11649 reference number Estonia: If unstructured and structured references are both used the maximum accepted combined length is 130. 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 Reference <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 ISO11649 reference number is accepted and the correctness validated Latvia, Lithuania: No validations are performed on the value currently Page 22 of 45

23 3. Customer Payment Status Report pain ISO Index No. Or Message Item Tag Name Structural Sequence Type Mult. RULES 0.0 Customer Payment Status Report <CstmrPmtStsRpt> - [1..1] 1.0 GroupHeader <GrpHdr> + [1..1] 1.1 MessageIdentification <MsgId> ++ Text [1..1] 1.2 CreationDateTime <CreDtTm> ++ DateTime [1..1] 1.3 InitiatingParty <InitgPty> ++ [1..1] Identification +++ [1..1] OrganisationIdentification <OrgId> ++++ [1..1] BICOrBEI <BICOrBEI> Identifier [1..1] 2.0 OriginalGroupInformationAndStatus <OrgnlGrpInfAndSts> + [1..1] 2.1 OriginalMessageIdentification <OrgnlMsgId> ++ Text [1..1] <GrpHdr> +<MsgId> value from corresponding C2B pain.001 file 2.2 OriginalMessageNameIdentification <OrgnlMsgNmId> ++ Text [1..1] Specifies the original message name identifier to which the message refers, e.g. pain OriginalNumberOfTransactions <OrgnlNbOfTxs> ++ Text [1..1] NumberOfTransactions from the Credit Transfer file (pain ) 2.5 OriginalControlSum <OrgnlCtrlSum> ++ Quantity [0..1] ControlSum from the Credit Transfer file (pain ) 2.6 GroupStatus <GrpSts> ++ Code [0..1] 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 StatusReasonInformation <StsRsnInf> ++ [0..n] 2.8 Originator <Orgtr> +++ [0..1] Identification ++++ [0..1] OrganisationIdentification <OrgId> [1..1] BICOrBEI <BICOrBEI> Identifier [0..1] 2.9 Reason <Rsn> +++ [1..1] Specifies the reason for the status report 2.10 Code <Cd> ++++ Code [1..1] 2.12 AdditionalInformation <AddtlInf> +++ Text [0..n] Swedbank Gateway error description. 3.0 OriginalPaymentInformationAndStatus <OrgnlPmtInfAndSts> + [0..n] 3.1 OriginalPaymentInformationIdentification <OrgnlPmtInfId> ++ Text [1..1] <PmtInfId> value from corresponding C2B pain.001 file 3.4 PaymentInformationStatus <PmtInfSts> ++ Code [0..1] Status codes used by Swedbank: Swedbank 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 23 of 45

24 ISO Index No. Or Message Item Tag Name Structural Sequence Type Mult. RULES 3.5 StatusReasonInformation <StsRsnInf> ++ [0..n] 3.6 Originator <Orgtr> +++ [0..1] Identification ++++ [0..1] OrganisationIdentification <OrgId> [1..1] BICOrBEI <BICOrBEI> Identifier [0..1] 3.7 Reason <Rsn> +++ [1..1] Specifies the reason for the status report 3.8 Code <Cd> ++++ Code [1..1] 3.10 AdditionalInformation <AddtlInf> +++ Text [0..n] Swedbank Gateway error description TransactionInformationAndStatus <TxInfAndSts> ++ [0..n] 3.17 OriginalInstructionIdentification <OrgnlInstrId> +++ Text [1..1] 3.18 OriginalEndToEndIdentification <OrgnlEndToEndId> +++ Text [1..1] 3.19 TransactionStatus <TxSts> +++ Code [1..1] 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 StatusReasonInformation <StsRsnInf> +++ [1..1] 3.21 Originator <Orgtr> ++++ [0..1] Identification of the Type of Party that initiated the reject. Limited to BIC to identify the bank or CSM originating the status or Name to indicate a CSM when it has no BIC. Name is limited to 70 characters in length. Party that issues the status Identification [0..1] OrganisationIdentification <OrgId> [1..1] BICOrBEI <BICOrBEI> Identifier [0..1] 3.22 Reason <Rsn> ++++ [1..1] Specifies the reason for the status report 3.23 Code <Cd> Code [1..1] 3.25 AdditionalInformation <AddtlInf> ++++ Text [1..1] Swedbank Gateway error description AccountServicerReference <AcctSvcrRef> +++ Text [0..1] 3.32 OriginalTransactionReference <OrgnlTxRef> +++ [0..1] 3.34 Amount <Amt> ++++ [0..1] Not reported for Consolidated payments 3.35 InstructedAmount <InstdAmt Ccy="AAA"> Amount [1..1] 3.41 RequestedExecutionDate <ReqdExctnDt> ++++ DateTime [1..1] Debtor <Dbtr> ++++ [1..1] Name <Nm> Text [1..1] DebtorAccount <DbtrAcct> ++++ [1..1] Identification [1..1] IBAN <IBAN> Identifier [1..1] Currency <Ccy> Code [1..1] DebtorAgent <DbtrAgt> ++++ [1..1] FinancialInstitutionIdentification <FinInstnId> [1..1] BIC <BIC> Identifier [1..1] CreditorAgent <CdtrAgt> ++++ [0..1] FinancialInstitutionIdentification <FinInstnId> [1..1] {Or BIC <BIC> Identifier [1..1] Page 24 of 45

25 ISO Index No. Or Message Item Tag Name Structural Sequence Type Mult. RULES Or} ClearingSystemMemberIdentifi<ClrSysMmbId> [1..1] ClearingSystemIdentification<ClrSysId> [0..1] Code <Cd> Code [1..1] MemberIdentification <MmbId> Text [1..1] Creditor <Cdtr> ++++ [1..1] Name <Nm> Text [1..1] CreditorAccount <CdtrAcct> ++++ [1..1] Identification [1..1] {Or IBAN <IBAN> Identifier [1..1] Or} Other <Othr> [1..1] Identification Text [1..1] Page 25 of 45

26 3.1 Statuses in Pain002

27 4. Examples 4.1 Domestic Payment Estonia, 2 payments: <?xml version="1.0" encoding="utf-8"?> <Document xmlns:xsi=" xmlns="urn:iso:std:iso:20022:tech:xsd:pain "> <CstmrCdtTrfInitn> <GrpHdr> <MsgId> </MsgId> <CreDtTm> T11: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> </ReqdExctnDt> <Dbtr> <Nm>ETTEVÕTE AS</Nm> <PstlAdr> <Ctry>EE</Ctry> <AdrLine>Metsa 8, Tallinn</AdrLine> </PstlAdr> <OrgId> <Othr> </Othr> </OrgId>

28 </Dbtr> <DbtrAcct> <IBAN>EE </IBAN> <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> <OrgId> <Othr> </Othr> </OrgId> </Cdtr> <CdtrAcct> <IBAN>EE </IBAN>

29 </CdtrAcct> <RmtInf> </RmtInf> </CdtTrfTxInf> <CdtTrfTxInf> <PmtId> </PmtId> <Amt> </Amt> <Cdtr> </Cdtr> <CdtrAcct> <Strd> </Strd> <CdtrRefInf> <Tp> <CdOrPrtry> <Cd>SCOR</Cd> </CdOrPrtry> </Tp> <Ref> </Ref> </CdtrRefInf> <InstrId>116</InstrId> <EndToEndId>328</EndToEndId> <InstdAmt Ccy="EUR">0.85</InstdAmt> <Nm>Mari Ööbik</Nm> <PstlAdr> <Ctry>EE</Ctry> <AdrLine>Pronksi 12, Tallinn</AdrLine> </PstlAdr> <PrvtId> <Othr> </Othr> </PrvtId>

30 </PmtInf> </CstmrCdtTrfInitn> </Document> </CdtrAcct> <RmtInf> </RmtInf> </CdtTrfTxInf> <IBAN>EE </IBAN> <Ustrd>Here enter payment details</ustrd> <Strd> <CdtrRefInf> <Tp> <CdOrPrtry> <Cd>SCOR</Cd> </CdOrPrtry> </Tp> <Ref> </Ref> </CdtrRefInf> </Strd> 4.2 International Payment example (express payment in USD, via correspondent bank): <?xml version="1.0" encoding="utf-8"?> <Document xmlns:xsi=" xmlns="urn:iso:std:iso:20022:tech:xsd:pain "> <CstmrCdtTrfInitn> <GrpHdr> <MsgId> </MsgId> <CreDtTm> T11: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>

31 <PmtTpInf> <SvcLvl> <Cd>SDVA</Cd> </SvcLvl> </PmtTpInf> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm>ETTEVÕTE AS</Nm> <PstlAdr> <Ctry>EE</Ctry> <AdrLine>Metsa 2, Tallinn</AdrLine> </PstlAdr> </Dbtr> <DbtrAcct> <IBAN>EE </IBAN> <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>

32 </PstlAdr> </FinInstnId> </IntrmyAgt1> <IntrmyAgt1Acct> <Othr> </Othr> </IntrmyAgt1Acct> <CdtrAgt> <FinInstnId> <BIC>SWEDSESS</BIC> <Nm>Swedbank AB Sweden</Nm> <PstlAdr> <AdrLine>Stockholm Brunkebergstorg 8</AdrLine> </PstlAdr> </FinInstnId> </CdtrAgt> <CdtrAgtAcct> <Othr> </Othr> </CdtrAgtAcct> <Cdtr> <Nm>Beneficiary Test1</Nm> <PstlAdr> <Ctry>SE</Ctry> <AdrLine>Stockholm Ridmansgatan 3F</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Othr> </Othr>

33 </PmtInf> </CstmrCdtTrfInitn> </Document> </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> 4.3 European Payment example (Sepa Credit Transfer, LAT example with regulatory reporting) <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain "> <CstmrCdtTrfInitn> <GrpHdr> <MsgId> </MsgId> <CreDtTm> T12:00:32</CreDtTm> <NbOfTxs>1</NbOfTxs> <CtrlSum>10000</CtrlSum> <InitgPty> <Nm>FIRMALV AS</Nm> <OrgId> <Othr> </GrpHdr> <PmtInf> </InitgPty> </OrgId> </Othr> <SchmeNm> <Cd>TXID</Cd> </SchmeNm>

34 <PmtInfId>PMTID </PmtInfId> <PmtMtd>TRF</PmtMtd> <BtchBookg>false</BtchBookg> <NbOfTxs>1</NbOfTxs> <PmtTpInf> <SvcLvl> <Cd>SEPA</Cd> </SvcLvl> <LclInstrm> <Prtry>NORM</Prtry> </LclInstrm> </PmtTpInf> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm>FIRMALV AS</Nm> <PstlAdr> <Ctry>LV</Ctry> <AdrLine>Adrese, Rīga, Latvija, LV-1000</AdrLine> </PstlAdr> <OrgId> <Othr> <SchmeNm> <Cd>TXID</Cd> </SchmeNm> </Othr> </OrgId> </Dbtr> <DbtrAcct> <IBAN>LV45HABA </IBAN> <Ccy>EUR</Ccy> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>HABALV22</BIC> </FinInstnId> </DbtrAgt> <ChrgBr>SHAR</ChrgBr> <CdtTrfTxInf> <PmtId>