Pain.001.001.09

The ISO 20022 Customer Credit Transfer Initiation to initiate outgoing payments from client accounts.

XML Format and Rules

LHV Bank is using custom version of pain.001.001.09.xsd

XML rules

Multiplicity (MULT.) defines the required or allowed number of occurrences of an element:

1..1 Exactly one occurrence (mandatory).
1..n At least one, up to “n.” Depending on the specification, “n” can be a fixed integer (e.g., 3) or can be “unbounded” (∞). If it is unbounded, there’s no upper limit.
1..3 At least one, at most three. (When “n” is explicitly the integer 3, then just 1 to 3 occurrences.)
0..1 Optional—can appear zero or one time.
0..n Zero to “n” times. Again, “n” can be a fixed integer or unbounded.

Message structure

MULT.

MESSAGE ELEMENT

XML TAG

COMMENT

[1..1]

+GroupHeader

Mandatory, occurs once.

[1..n]

+PaymentInformation

Mandatory, repeatable

[0..n]

+SupplementaryData

Optional, repeatable

Message root

MULT.

MESSAGE ELEMENT

XML TAG

COMMENT

[1..1]

+MessageRoot

Mandatory, occurs once.

Group header

MULT.

MESSAGE ELEMENT

XML TAG

COMMENT

[1..1]

+GroupHeader

[1..1]

++MessageIdentification

<MsgId>

Unique message ID created by PSP. See Payments Service Idempotency for details.

[1..1]

++CreationDateTime

Date and time at which the message was created.

[1..1]

++NumberOfTransactions

Total number of transactions in all Payment Information sections in this message. If the number is incorrect, the file upload will be rejected.

[1..1]

++ControlSum

The control sum of all individual amounts across all Payment Information blocks in this message, regardless of currency. If the sum is incorrect, the file upload will be rejected.

[1..1]

++InitiatingParty

Party initiating the payment.

[0..1]

+++Name

<Nm>

Initiating party name.

[0..1]

+++PostalAddress

See Address structure for more details.

[0..1]

+++Identification

<Id>

Unique and unambiguous identification of a initiating party. See Party Identification Structure for details. For initiating party only OrgId.AnyBIC value is used. Other options are not supported and values are ignored.

[0..1]

+++CountryOfResidence

Initiating party country of residence (country code).

[0..1]

++ForwardingAgent

Financial institution that receives the instruction from the initiating party and forwards it to the next agent in the payment chain for execution.

[0..1]

+++FinancialInstitutionIdentification

See Agent's financial institution block for details. For FwdgAgt, BICFI and postal address elements are saved if present.

Payment information

MULT.

MESSAGE ELEMENT

XML TAG

COMMENT

[1..n]

+PaymentInformation

[1..1]

++PaymentInformationIdentification

Uniquely identifies the payment information group within this message.

[1..1]

++PaymentMethod

Only the value "TRF" (Credit Transfer) is allowed. If any other value is provided, the file will fail XML schema validation and be rejected.

[0..1]

++BatchBooking

Not supported, value ignored.

[1..1]

++NumberOfTransactions

Total number of individual transactions contained in the payment information group. If the number is incorrect, the file upload will be rejected.

[1..1]

++ControlSum

The control sum of all individual amounts in the current Payment Information block, regardless of currency. If the sum is incorrect, the file upload will be rejected.

[0..1]

++PaymentTypeInformation

Set of elements used to further specify the type of transaction. PmtTpInf must be present either here or under ‘Credit Transfer Transaction Information’.

If PmtTpInf is provided at both levels, the transaction-level values take precedence. If omitted at the transaction level, the PmtInf-level values apply.

[0..1]

+++InstructionPriority

Not supported, value ignored.

[0..1]

+++ServiceLevel

Agreement of rules according to which the payment must be processed. Pre-agreed customer-to-bank conditions apply.

{Or

++++Code

<Cd>

Not supported, value ignored.

{Or

++++Proprietary

<Prtry>

Allowed values: INST, SEPA, FAST, ALL - equals as submitted without type. If other value is used, the file upload will be rejected. See Payment Scheme Selection for more details.

[0..1]

+++LocalInstrument

Element to specify a local instrument, local clearing option and/or further qualify the service or service level.

{Or

++++Code

<Cd>

Not supported, value ignored.

Or}

++++Proprietary

<Prtry>

Payment priority information. The value here applies to all transactions included in the current Payment Information block. See the supported values in Code Set: Payment Priority.

[0..1]

+++CategoryPurpose

Specifies the high level purpose of the instruction based on a set of pre-defined categories.

{Or

++++Code

<Cd>

See the supported values in Code Set: Category Purpose. The value here applies to all transactions included in the current Payment Information block. If an unrecognised value is provided, it will be replaced with OTHR.

Or}

++++Proprietary

<Prtry>

Not supported, value ignored.

[1..1]

++RequestedExecutionDate

Date on which the debtor's account is to be debited. Either date or date-time must be provided, but not both. If date-time is provided, only the date portion is considered. The preferred format for date is YYYY-MM-DD.

The date applies to all transactions (CdtTrfTxInf) within the same PmtInf block.

[1..1]

++Debtor

<Dbtr>

Party whose account is debited.

[0..1]

+++Name

<Nm>

Debtor’s name.

Indirect Scheme Participant: Debtor’s name is mandatory. Use the actual account holder’s name, not the master account owner’s name.
VIBAN: Debtor’s name is mandatory and must match the account holder’s name. Use the actual account holder’s name, not the master account owner’s name. If name doesn't match, transactions in this PmtInf block will be rejected.

[0..1]

+++PostalAddress

See Address structure for more details.

Indirect Scheme Participant: Debtor’s address is mandatory.

[0..1]

+++Identification

<Id>

Unique and unambiguous identification of a debtor. See Party Identification Structure for details.

[1..1]

++DebtorAccount

Debtor’s account.

This can be the client’s own account, a VIBAN, or an Indirect Scheme Participant account

[1..1]

+++Identification

<Id>

{Or

++++IBAN

<IBAN>

IBAN or VIBAN. If the provided IBAN or VIBAN is invalid (due to incorrect length, structure, checksum validation, or status in the system), the entire PmtInf block will be rejected.

Or}

++++Other

<Othr>

Debtor's non-IBAN account number.

[1..1]

+++++Identification

<Id>

Account number value. For UK local accounts: sort code + account number.

[0..1]

++++++SchemeName

Not supported, values ignored.

{Or

+++++++Code

Or}

+++++++Proprietary

[0..1]

++++++Issuer

Not supported, value ignored.

[0..1]

+++Type

<Type>

Not supported, value ignored.

[0..1]

+++Currency

<Ccy>

Not supported, value ignored.

[0..1]

+++Name

<Nm>

Not supported, value ignored.

[0..1]

+++Proxy

<Prxy>

Not supported, value ignored.

[1..1]

++DebtorAgent

Financial institution servicing an account for the debtor.

[1..1]

+++FinancialInstitutionIdentification

See Agent's financial institution block for details. For DbtrAgt, BICFI and postal address elements are saved if present.

[0..1]

++DebtorAgentAccount

Not supported, value ignored.

[0..1]

++InstructionForDebtorAgent

Not supported, value ignored.

[0..1]

++UltimateDebtor

A third party who is the true owner of the funds or the effective initiator of the payment. If Ultimate Debtor information is provided at the Payment Information level, it applies to every payment within that block. Used in SEPA, SEPA Instant, and Faster Payments (Payments Originated Overseas, FPSPOO). Use this field only when the Ultimate Debtor is different from the Debtor.

[0..1]

+++Name

<Nm>

Ultimate debtor’s name.

[0..1]

+++PostalAddress

See Address structure for more details.

[0..1]

+++Identification

<Id>

Unique and unambiguous identification of a debtor. See Party Identification Structure for details. In case of FPSPOO OrgId.AnyBIC must be owned by the institution that provides the account to the ultimate debtor and must be a non-GB BIC.

[0..1]

+++CountryOfResidence

Ultimate debtor’s country of residence.

[0..1]

+++ContactDetails

Not supported, values ignored.

[0..1]

++ChargesBearer

Specifies which party/parties will bear the charges associated with the processing of the payment. See the supported values in Code Set: Charges Bearer.

[0..1]

++ChargesAccount

Not supported, values ignored.

[0..1]

++ChargesAccountAgent

Not supported, values ignored.

[1..n]

++CreditTransferTransactionInformation

<CdtTrfTxInf>

This block contains a set of elements providing information on the individual payment(s) included in the message.

[1..1]

+++PaymentIdentification

<PmtId>

Set of elements used to reference a payment instruction.

[0..1]

++++InstructionIdentification

Unique identification, as assigned by an instructing party for an instructed party, to unambiguously identify the instruction.

[1..1]

++++EndToEndIdentification

Unique identification assigned by the initiating party to unambiguously identify the transaction.

[0..1]

++++UETR

<UETR>

Unique End-to-end Transaction Reference in UUIDv4 format.

[1..1]

+++PaymentTypeInformation

Set of elements used to specify the type of payment. PmtTpInf must be present either here or under PmtInf.

If PmtTpInf is provided at both levels, the transaction-level value takes precedence. If omitted at the transaction level, the PmtInf-level values applies.

[0..1]

++++InstructionPriority

Not supported, value ignored.

[0..1]

++++ServiceLevel

Agreement of rules according to which the payment must be processed. Pre-agreed customer-to-bank conditions apply.

{Or

+++++Code

<Cd>

Not supported, value ignored.

Or}

+++++Prtry

<Prtry>

Allowed values: INST, SEPA, FAST, ALL - equals as submitted without type. If other value is used, the transaction will be rejected. See Payment Scheme Selection for more details.

[0..1]

++++LocalInstrument

Element to specify a local instrument, local clearing option and/or further qualify the service or service level.

{Or

+++++Code

<Cd>

Not supported, value ignored.

Or}

+++++Proprietary

<Prtry>

Payment priority information. The value here applies to the payment included in the current Credit Transfer Transaction Information block. See the supported values in Code Set: Payment Priority.

[0..1]

++++CategoryPurpose

Specifies the high level purpose of the instruction based on a set of pre-defined categories.

{Or

+++++Code

<Cd>

See the supported values in Code Set: Category Purpose. The value here applies to the payment included in the current Credit Transfer Transaction Information block. If an unrecognised value is provided, it will be replaced with OTHR.

Or}

+++++Proprietary

<Prtry>

Not supported, value ignored.

[1..1]

+++Amount

<Amt>

{Or

++++InstructedAmount

Payment amount and the currency ordered by the initiating party. All currencies accepted by the bank for payment services are allowed. Amount must be greater than 0.

Or}

++++EquivalentAmount

Not supported, value ignored.

[0..1]

+++ExchangeRateInformation

Not supported, value ignored.

[0..1]

+++ChargeBearer

Specifies which party/parties will bear the charges associated with the processing of the payment. See the supported values in Code Set: Charges Bearer.

[0..1]

+++ChequeInstruction

Not supported, value ignored.

[0..1]

+++UltimateDebtor

A third party who is the true owner of the funds or the effective initiator of the payment. If Ultimate Debtor information provided here applies to the payment included in the current Credit Transfer Transaction Information block. Used in SEPA, SEPA Instant, and Faster Payments (Payments Originated Overseas, FPSPOO). Use this field only when the Ultimate Debtor is different from the Debtor.

[0..1]

++++Name

<Nm>

Ultimate debtor’s name.

[0..1]

++++PostalAddress

See Address structure for more details.

[0..1]

++++Identification

<Id>

[0..1]

++++CountryOfResidence

Ultimate debtor’s country of residence.

[0..1]

++++ContactDetails

Not supported, values ignored.

[0..1]

+++IntermediaryAgent1

Block containing the correspondent bank details for the creditor’s bank.

[0..1]

++++FinancialInstitutionIdentification

See Agent's financial institution block for details. For IntrmyAgt1, BICFI or ClrSysMmbId/MmbId + name and postal address elements are saved.

[0..1]

+++IntermediaryAgent2..3

<IntrmyAgt2..3>

Not supported, values ignored.

[0..1]

+++CreditorAgent

Creditor agent’s information.

[1..1]

++++FinancialInstitutionIdentification

See Agent's financial institution block for details. For CdtrAgt, BICFI or ClrSysMmbId/MmbId + name, and postal address elements are saved if present. ClrSysId.Cd = 'GBDSC' when using UK sort code and account number separately. MmbId = 'sort code' when using UK sort code and domestic account number separately.

[0..1]

+++CreditorAgentAccount

Not supported, value ignored.

[1..1]

+++Creditor

<Cdtr>

Party to which an amount of money is due.

[1..1]

++++Name

<Nm>

Creditor’s name.

[0..1]

++++PostalAddress

See Address structure for more details.

[0..1]

++++Identification

<Id>

Unique and unambiguous identification of a debtor. See Party Identification Structure for details.

[0..1]

++++CountryOfResidence

Not supported, value ignored.

[0..1]

++++ContactDetails

Not supported, value ignored.

[1..1]

+++CreditorAccount

Creditor’s account.

[1..1]

++++Identification

<Id>

{Or

+++++IBAN

<IBAN>

Creditor’s IBAN. If the provided IBAN is invalid (due to incorrect length, structure, or checksum validation), the transaction will be rejected.

Or}

+++++Other

<Othr>

Creditor’s non-IBAN account number.

[1..1]

++++++Identification

<Id>

Account number value. For UK local accounts: sort code + account number.

[0..1]

++++++SchemeName

Name of the identification scheme.

{Or

+++++++Code

<Cd>

Scheme Name Code:

Use code BBAN when providing a concatenated UK Sort Code + Account Number (14 characters).

Omit this field when the UK Sort Code and Account Number are provided separately.

Or}

+++++++Proprietary

<Prtry>

Not supported, value ignored.

[0..1]

++++++Issuer

<Issr>

Not supported, value ignored.

[0..1]

++++Type

<Tp>

Not supported, value ignored.

[0..1]

++++Currency

<Ccy>

Not supported, value ignored.

[0..1]

++++Name

<Nm>

Not supported, value ignored.

[0..1]

++++Proxy

<Prxy>

Not supported, value ignored.

[0..1]

+++UltimateCreditor

Ultimate party to which an amount of money is due.

[0..1]

++++Name

<Nm>

Ultimate creditor’s name.

[0..1]

++++PostalAddress

See Address structure for more details.

[0..1]

++++Identification

<Id>

Unique and unambiguous identification of a debtor. See Party Identification Structure for details.

[0..1]

++++CountryOfResidence

Not supported, value ignored.

[0..1]

++++ContactDetails

Not supported, value ignored.

[0..1]

+++InstructionForCreditorAgent

Not supported, value ignored.

[0..1]

+++InstructionForDebtorAgent>

See Initiating Return Payments. Format: RTRN:RETURNCODE:ACCOUNTSERVICERREFERENCE

[0..1]

+++Purpose

<Purp>

Underlying reason for the payment transaction.

{Or

++++Code

<Cd>

See the supported codes in Code Set: Purpose. If an unrecognised value is provided, it will be replaced with OTHR.

Or}

++++Proprietary

<Prtry>

Not supported, value ignored.

[0..10]

+++RegulatoryReporting

Not supported, values ignored.

[0..1]

+++Tax

<Tax>

Not supported, values ignored.

[0..10]

+++RelatedRemittanceInformation

Not supported, values ignored.

[0..1]

+++RemittanceInformation

This field provides details to match the payment entry with the corresponding transaction or invoice. It can contain either unstructured remittance information (payment description) or structured remittance information (reference number).

At least one of these fields must be provided.

For Faster Payments (FPS), structured remittance information is mandatory.

[0..1]

++++Unstructured

<Ustrd>

Payment description.

[0..1]

++++Structured

<Strd>

[0..n]

+++++ReferredDocumentInformation

Not supported, values ignored.

[0..1]

+++++ReferredDocumentAmount

Not supported, value ignored.

[0..1]

+++++CreditorReferenceInformation

[0..1]

++++++Type

<Tp>

Specifies the type of creditor reference.

[1..1]

+++++++CodeOrProprietary

[1..1]

++++++++Code

<Cd>

[0..1]

+++++++Issuer

<Issr>

[0..1]

++++++Reference

<Ref>

Reference number. For Faster Payments (FPS), reference number is mandatory, the value must be up to 18 characters.

[0..1]

+++++Invoicer

<Invcr>

Not supported, value ignored.

[0..1]

+++++Invoicee

Not supported, value ignored.

[0..1]

+++++TaxRemittance

Not supported, value ignored.

[0..1]

+++++GarnishmentRemittance

Not supported, value ignored.

[0..1]

+++++AdditionalRemittanceInformation

Not supported, value ignored.

[0..n]

+++Supplementary Data

See details in supplementary data section.

[0..1]

++++Place and Name

Not supported, value ignored.

[1..1]

++++Data Envelope

<Envlp>

[1..1]

+++++Document

[0..n]

++++++Party Data

Additional data block

[1..1]

+++++++Party Code

<Party>

Defines which party this data is related to. Possible values: DEBTOR, CREDITOR, ULTIMATE_DEBTOR, ULTIMATE_CREDITOR

[1..1]

+++++++Data Key

<Key>

Additional data element being sent. Possible values: DATE_OF_BIRTH, MCC, PSP_SCENARIO.

[1..1]

+++++++Data Value

<Value>

Additional data element value

Address structure (PostalAddress)

Common address structure is used throughout the payment initiation message.

Guidance for Postal Address use

Non-agent parties (Debtor*, Creditor, Ultimate Debtor/Creditor), provide the following elements:

• Building number (BldgNb)

• Street name (StrtNm)

• Town name (TwnNm)

• Postal code (PstCd)

• Country (Ctry)

*Indirect Scheme Participant: if Debtor is an indirect scheme participant, then address details should be included in the payment initiation message as LHV does not store them.

Agent parties (Creditor Agent, Initiating Party, Forwarding Agent, Intermediary Agent etc.) provide the following elements:

• Town name (TwnNm)

• Country (Ctry)

MULT.

MESSAGE ELEMENT

XML TAG

COMMENT

[0..1]

Department

<Dept>

[0..1]

Sub-department name

[0..1]

Street name

[0..1]

Building number

[0..1]

Building name

[0..1]

Floor number

<Flr>

[0..1]

Post box

<PstBx>

[0..1]

Room name

<Room>

[0..1]

Postal code

<PstCd>

[0..1]

Town name

<TwnNm>

[0..1]

Town location name

[0..1]

District name

[0..1]

Country sub-division

[0..1]

ISO 2 letter country code

<Ctry>

[0..2]

Address line

Party Identification Structure

The Party Identification Code block is used to uniquely identify various parties involved in a payment instruction, including the initiating party, debtor, creditor, and ultimate parties. Identification can be provided as an Organisation ID (OrgId) for businesses or a Private ID (PrvtId) for individuals.

MULT.

MESSAGE ELEMENT

XML TAG

COMMENT

[0..1]

+++Identification

<Id>

Unique and unambiguous identification of a party

{Or

++++OrganisationIdentification

<OrgId>

Unique and unambiguous way to identify an organisation. Either ‘AnyBIC', 'LEI’ or one occurrence of ‘Other’ is allowed.

[0..1]

+++++AnyBic

[0..1]

+++++LEI

<LEI>

[0..n]

+++++Other

<Othr>

[1..1]

++++++Id

<Id>

Code value, for example company registration number.

[0..1]

++++++SchemeName

{Or

+++++++Code

<Cd>

See Code set: Organisation Identification Type Codes

Or}

+++++++Proprietary

<Prtry>

Not supported, values ignored.

[0..1]

++++++Issuer

<Issr>

Or}

++++PersonIdentification

Unique and unambiguous identification of a person. Either ‘Date and Place of Birth’ or one occurrence of ‘Other’ is allowed.

{Or

+++++DateAndPlaceOfBirth

[1..1]

++++++BirthDate

The date of birth, in ISO date format (YYYY-MM-DD).

[0..1]

++++++ProvinceOfBirth

The province or region where the person was born.

[1..1]

++++++CityOfBirth

The city where the person was born.

[1..1]

++++++CountryOfBirth

The country where the person was born (ISO 3166-1 alpha-2 country code).

Or}

+++++Other

<Othr>

[1..1]

+++++++Id

<Id>

Code value, for example passport number.

[0..1]

+++++++SchemeName

{Or

++++++++Code

<Cd>

See Code set: Private Person Identification Codes

Or}

++++++++Proprietary

<Prtry>

Not supported, values ignored.

[0..1]

+++++++Issuer

<Issr>

Agent's Branch and Financial Institution Identification Structure

The Branch and Financial Institution Identification structure is used to define financial institutions involved in a payment transaction, including the Debtor Agent, Creditor Agent, Intermediary Agent1 , and Forwarding Agent.

MULT.

MESSAGE ELEMENT

XML TAG

COMMENT

[0..1]

++++FinancialInstitutionIdentification

Financial Institution Identification.

[0..1]

+++++BICFI

<BICFI>

The SWIFT/BIC code of the agent.

[0..1]

+++++ClearingSystemMemberIdentification

Clearing system member identification, used to identify a financial institution using a clearing system instead of a BIC. Agents this element applies to: Creditor Agent and Intermediary Agent 1. If ClrSysMmbId/MmbId data is provided, it takes priority over BICFI.

[0..1]

++++++ClearingSystemIdentification

{Or

+++++++Code

<Cd>

Specifies a predefined clearing system code from the ISO 20022 external code list (e.g., CHAPS, Fedwire).

Or}

+++++++Proprietary

<Prtry>

Not supported, value ignored.

[1..1]

++++++MemberIdentification

<MmbId>

Identifies the financial institution's membership ID within the clearing system (e.g., bank ID in CHAPS)

[0..1]

+++++LEI

<LEI>

Not supported, value ignored.

[0..1]

+++++Name

<Nm>

The name of the agent.

[0..1]

+++++PostalAddress

See Address structure for more details. Address details are saved for Debtor Agent, Creditor Agent, Intermediary Agent, and Forwarding Agent if present.

[0..1]

+++++Other

<Othr>

Other institution identifier. Not supported, values ignored.

[1..1]

++++++Identification

<Id>

[0..1]

++++++SchemeName

{Or

+++++++Code

<Cd>

Or}

+++++++Proprietary

<Prtry>

[0..1]

++++++Issuer

<Issr>

[0..1]

++++BranchIdentification

Branch Identification.

[0..1]

+++++Identification

<Id>

Unique identifier for the branch. Not supported, value ignored.

[0..1]

+++++LEI

<LEI>

Not supported, value ignored.

[0..1]

+++++Name

<Nm>

Name of the branch. Not supported, value ignored.

[0..1]

+++++PostalAddress

See Address structure for more details. Address details are saved for Debtor Agent, Creditor Agent, and Forwarding Agent if present.

Supplementary data

Additional data can be added to the payment using SplmtryData element. Supplementary data block is encapsulated in XSD envelope (field Envlp) which may contain any additional structure of data.

   <xs:complexType name="SupplementaryDataEnvelope1">
       <xs:sequence>
           <xs:any namespace="##any" processContents="lax"/>
       </xs:sequence>
   </xs:complexType>

LHV uses additional structure defined in supl.001.001.01.xsd. For proper XML validation the schema reference should be provided in pain.001.001.09 XML message header. For example:

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.09"
	xmlns:ext="urn:iso:std:iso:20022:tech:xsd:supl.001.001.01"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:iso:std:iso:20022:tech:xsd:pain.001.001.09 ../../XSD/pain.001.001.09.xsd urn:iso:std:iso:20022:tech:xsd:supl.001.001.01 ../../XSD/supl.001.001.01.xsd">

Supplementary data includes additional data elements defined in 3 fields.

party - party that given data element is related to (e.g. CREDITOR, DEBTOR)
key - data element key (see below for supported values)
value - value for given data element (e.g. 1986-02-05)

Suplementary data key's:

Key

Value/format

Usage description

DATE_OF_BIRTH

yyyy-mm-dd (date)

Must be filled for if there is no information about the party's city of birth or country and therefore it is not possible to add complete data under the message element date and place of birth (DateAndPlaceOfBirth).

MCC

nnnn (4 digit number)

MCC code is used to classify a business by the types of goods or services it provides. ISO 18245 is an ISO standard concerning the assignment of Merchant Category Codes (MCC) in retail financial services. Allowed values: List of Merchant Category Codes (https://classification.codes/classifications/industry/mcc/)

PSP_SCENARIO

string

Fixed value: "COMBINED_PAYMENT" - Two or more payments are combined into a single payment.

pain.001 supplementary data example:

...
<SplmtryData>
    <Envlp>
        <ext:Document>
            <ext:partyData>
                <ext:party>DEBTOR</ext:party>
                <ext:key>DATE_OF_BIRTH</ext:key>
                <ext:value>1980-09-24</ext:value>
            </ext:partyData>
            <ext:partyData>
                <ext:party>DEBTOR</ext:party>
                <ext:key>MCC</ext:key>
                <ext:value>0763</ext:value>
            </ext:partyData>
            <ext:partyData>
                <ext:party>DEBTOR</ext:party>
                <ext:key>PSP_SCENARIO</ext:key>
                <ext:value>COMBINED_PAYMENT</ext:value>
            </ext:partyData>
        </ext:Document>
    </Envlp>
</SplmtryData>
...

PreviousPayment Initiation Services NextPain.002.001.10

Last updated 3 months ago

Was this helpful?