pain.001.001.09 format

LHV is using custom version of pain.001.011.xsd

60KB

pain.001.001.09.lhv.xsd.xml

XML rules

Multiplicity (MULT.) Informs how many times an element can or must be used, as defined by ISO standard.

1. 1..1 One occurrence (required)

2. 1..n One or several occurrences (value for “n” represents total number of occurrences)

3. 1..3 Minimum one occurrence must be used and maximum 3 occurrences can be used. Note: True value of “n” represents unlimited number of occurrences.

4. 0..1 None or one occurrence to be used (optional)

5. 0..n None or several occurrences can be used (value for “n” represents total number of occurrences). Note: True value of “n” represents unlimited number of occurrences.

Message structure

Group Header – mandatory, occurs once. Payment Information – mandatory and repetitive. Contains information related to mostly the debit side of the payment. Credit Transfer Transaction Information – mandatory and repetitive. Contains information related to the payment(s) included in the message.

Message root

MULT.	MESSAGE ELEMENT	XML TAG
[1..1]	+MessageRoot	<CstmrCdtTrfInitn>

Group header

MULT.	OR	MESSAGE ELEMENT	XML TAG	LHV REQUIREMENT
[1..1]		+GroupHeader	<GrpHdr>
[1..1]		++MessageIdentification	<MsgId>
[1..1]		++CreationDateTime	<CreDtTm>
[1..1]		++NumberOfTransactions	<NbOfTxs>	Number of payments in all Payment Information blocks included in this message. If this number is not correct, the file upload will be cancelled.
[1..1]		++ControlSum	<CtrlSum>	Control sum of all individual amounts for all Payment Information blocks included in this message, irrespective of currencies. If this number is not correct, the file upload will be cancelled.
[1..1]		++InitiatingParty	<InitgPty>	Party initiating the payment to an agent
[0..1]		+++Name	<Nm>	Initiating party name.
[0..1]		+++PostalAddress	<PstlAdr>	See address structure and details here.
[0..1]		+++Identification	<Id>
	{Or	++++OrganisationIdentification	<OrgId>
[0..1]		+++++AnyBic	<AnyBIC>	Initiating party BIC code.
[0..1]		+++++LEI	<LEI>	LEI code. Not supported, values ignored
[0..n]		+++++Other	<Othr>	Other identifier. Not supported, values ignored
	Or}	++++PrivateIdentification	<PrvtId>	Not supported
[0..1]		+++CountryOfResidence	<CtryOfRes>	Initiating party country of residence
[0..1]		++ForwardingAgent	<FwdgAgt>	Financial institution that receives the instruction from the initiating party and forwards it to the next agent in the payment chain for execution.
[1..1]		+++FinancialInstitutionIdentification	<FinInstnId>
[0..1]		++++BICFI	<BICFI>	Forwarding agent BIC code.
[0..1]		++++LEI	<LEI>	LEI code. Not supported, values ignored
[0..1]		++++Other	<Othr>	Other identifier. Not supported, values ignored
[0..1]		++++Name	<Nm>	Forwarding agent name.
[0..1]		++++PostalAddress	<PstlAdr>	See address structure and details here.

Payment information

MULT.	OR	MESSAGE ELEMENT	XML TAG	LHV REQUIREMENT
[1..n]		+PaymentInformation	<PmtInf>
[1..1]		++PaymentInformationIdentification	<PmtInfId>	Uniquely identifies the payment information group within this message.
[1..1]		++PaymentMethod	<PmtMtd>	Only the value TRF (credit transfer) is allowed here. If any other value is entered, it will be ignored.
[0..1]		++BatchBooking	<BtchBookg>	Not used.
[1..1]		++NumberOfTransactions	<NbOfTxs>	Number of payment included in the current Payment Information block. If this number is not correct, the file upload will be cancelled.
[1..1]		++ControlSum	<CtrlSum>	Control sum of all individual amounts in the current Payment Information block, irrespective of currencies. If this number is not correct, the file upload will be cancelled.
[0..1]		++PaymentTypeInformation	<PmtTpInf>
[0..1]		+++InstructionPriority	<InstrPrty>
[0..1]		+++ServiceLevel	<SvcLvl>
[1..1]		++++Code	<Cd>
[0..1]		+++LocalInstrument	<LclInstrm>
	{Or	++++Code	<Cd>
	Or}	++++Proprietary	<Prtry>	Payment priority information. The value here applies to all payments included in the current Payment Information block. See the supported values in Code Set: Payment Priority.
[0..1]		+++CategoryPurpose	<CtgyPurp>
[1..1]		++++Code	<Cd>	See the supported values in Code Set: Category Purpose.
[1..1]		++Requested Execution Date	<ReqdExctnDt><Dt>	Date on which the debtor’s account is debited.
[1..1]		++Debtor	<Dbtr>	Party from whose account the amount of payment is to be debited. If a different party’s information is entered, it will be ignored.
[1..1]		+++Name	<Nm>	Debtor’s name. For Virtual IBAN or indirect agent - the holder name (not the master account owner). Debtor name is mandatory if payment is initiated from indirect agent's existing accounts.
[0..1]		+++PostalAddress	<PstlAdr>	See address structure and details here. If payment is initiated with indirect agent's existing accounts, following rule applies: (Town Name and Country) or (Country and Address Line) are required.
[0..1]		+++Identification	<Id>	For Virtual IBAN - do not use
	{Or	++++OrganisationIdentification	<OrgId>
[0..1]		+++++AnyBic	<AnyBIC>	Debtor BIC code.
[0..1]		+++++LEI	<LEI>	Debtor LEI code.
[0..n]		+++++Other	<Othr>	Other identifier.
[1..1]		++++++Identification	<Id>	Organisation’s identification code.
[0..1]		++++++SchemeName	<SchmeNm>
[1..1]		+++++++Code	<Cd>	See the supported values in Code Set: Organisation Identification.
	Or}	++++PrivateIdentification	<PrvtId>
	{Or	+++++DateAndPlaceOfBirth	<DtAndPlcOfBirth>
[1..1]		++++++BirthDate	<BirthDt>	Debtor’s birth date.
[1..1]		++++++CityOfBirth	<CityOfBirth>	Debtor’s city of birth.
[1..1]		++++++CountryOfBirth	<CtryOfBirth>	Debtor’s birth country ISO code.
	Or}	+++++Other	<Othr>
[1..1]		++++++Identification	<Id>	Debtor’s identification code.
[0..1]		++++++SchemeName	<SchmeNm>
[1..1]		+++++++Code	<Cd>	See the supported values in Code Set: Private Person Identification.
[1..1]		++DebtorAccount	<DbtrAcct>	Debtor’s account. Can be client account where payment amount is debited, Virtual IBAN, or Indirect Agency account (both LHV and client generated accounts).
[1..1]		+++Identification	<Id>
{Or		++++IBAN	<IBAN>	Debtor’s IBAN or Virtual IBAN.
{Or		++++Other	<Othr>	Debtor's non-IBAN account number (for example, UK account number).
Or}}		+++++Identification	<Id>	Account number.
[0..1]		+++Currency	<Ccy>	Not required to be filled in. The payment will be made in the currency of the payment amount. If there are not enough funds available on the account, a relevant error message will appear.
[1..1]		++DebtorAgent	<DbtrAgt>	Debtor’s bank information. Not supported and ignored
[0..1]		++UltimateDebtor	<UltmtDbtr>	Used for SEPA payments or Faster Payments Payments Originated Overseas (FPSPOO). Third party acting as the actual owner of the funds or initiating the payment. If ultimate debtor information is filled in at the Payment Information level, it will apply to all payments included in this block. Usage rule: Only to be used if different from the debtor.
[0..1]		+++Name	<Nm>	Ultimate debtor’s name.
[0..1]		+++PostalAddress	<PstlAdr>	See address structure and details here. Ultimate debtor's postal address. In case of FPSPOO, either ultimate debtor town name and country, or country and address line is mandatory.
[0..1]		+++Identification	<Id>
	{Or	++++OrganisationIdentification	<OrgId>
[0..1]		+++++AnyBic	<AnyBIC>	Ultimate debtor's BIC code. BIC is mandatory in case of FPSPOO - must be owned by the institution which provides the account to the Ultimate debtor and must be a non GB BIC
[0..1]		+++++LEI	<LEI>	Organisation LEI code.
[0..n]		+++++Other	<Othr>	Other identifier.
[1..1]		++++++Identification	<Id>	Organisation’s identification code. Mandatory in case of FPSPOO - referring to Ultimate debtor’s account number and can be in IBAN or in other format.
[0..1]		++++++SchemeName	<SchmeNm>
[1..1]		+++++++Code	<Cd>	See the supported values in Code Set: Organisation Identification
	Or}	++++PrivateIdentification	<PrvtId>
	{Or	+++++DateAndPlaceOfBirth	<DtAndPlcOfBirth>
[1..1]		++++++BirthDate	<BirthDt>	Ultimate debtor’s birth date.
[0..1]		++++++ProvinceOfBirth	<PrvcOfBirth>	Ultimate debtor’s province of birth.
[1..1]		++++++CityOfBirth	<CityOfBirth>	Ultimate debtor’s city of birth.
[1..1]		++++++CountryOfBirth	<CtryOfBirth>	Ultimate debtor’s birth country ISO code.
	Or}	+++++Other	<Othr>
[1..1]		++++++Identification	<Id>	Ultimate debtor’s identification code.
[0..1]		++++++SchemeName	<SchmeNm>
[1..1]		+++++++Code	<Cd>	See the supported values in Code Set: Private Person Identification.
[0..1]		+++CountryOfResidence	<CtryOfRes>	Ultimate debtor’s country of residence.
[0..1]		++ChargesBearer	<ChrgBr>	See the supported values in Code Set: Charges Bearer.
[0..1]		++ChargesAccount	<ChrgsAcct>	LHV does not support charge debiting from other than debtor’s account.
[1..1]		+++Identification	<Id>
[1..1]		++++IBAN	<IBAN>
[0..1]		+++Currency	<Ccy>
[1..n]		++CreditTransferTransactionInformation	<CdtTrfTxInf>	This block contains a set of elements providing information on the payment(s) included in the message.
[1..1]		+++PaymentIdentification	<PmtId>
[0..1]		++++InstructionIdentification	<InstrId>	Unique identification, as assigned by an instructing party for an instructed party, to unambiguously identify the instruction.
[1..1]		++++EndToEndIdentification	<EndToEndId>	Unique identification assigned by the initiating party to unumbiguously identify the transaction.
[0..1]		++++UETR	<UETR>	Unique End-to-end Transaction Reference in UUIDv4 format. Details on Swift page
[1..1]		+++PaymentTypeInformation	<PmtTpInf>	Set of elements used to specify the type of payment.
[1..1]		++++ServiceLevel	<SvcLvl>	Agreement of rules according to which the payment must be processed. Pre-agreed customer-to-bank conditions apply.
[1..1]		+++++Prtry	<Prtry>	Specifies a pre-agreed service or level of service between the parties, as a proprietary code. Allowed values: INST, SEPA, FAST, ALL - equals as uploaded without interface type. Other values return validation error.
[0..1]		++++LocalInstrument	<LclInstrm>
	{Or	+++++Code	<Cd>
	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	<CtgyPurp>
[1..1]		+++++Code	<Cd>	See the supported values in Code Set: Category Purpose.
[1..1]		+++Amount	<Amt>
	{Or	++++InstructedAmount	<InstdAmt>	Payment amount and the currency ordered by the initiating party. All currencies accepted by the bank for payment services are allowed. If there are not enough funds available on the account in a given currency, a relevant error message will appear.
	Or}	++++EquivalentAmount	<EqvtAmt>	Not used.
[0..1]		+++ChargeBearer	<ChrgBr>	See the supported values in Code Set: Charges Bearer.
[0..1]		+++UltimateDebtor	<UltmtDbtr>	Third party acting as the actual owner of the funds or initiating the payment. If ultimate debtor information is filled in at the Payment Information level, it will apply to all payments included in this block. Usage rule: Only to be used if different from the debtor. Transferred to the respective payment scheme only in cases of SEPA Payments, SEPA Instant Payments or Faster Payments whose payer's payment service provider is not located in the United Kingdom (Payments Originated Overseas -FPSPOO).
[0..1]		++++Name	<Nm>	Ultimate debtor’s name. Mandatory in case of FPSPOO.
[0..1]		++++PostalAddress	<PstlAdr>	See address structure and details here Ultimate debtor's postal address. In case of FPSPOO, either ultimate debtor town name and country, or country and address line is mandatory.
[0..1]		++++Identification	<Id>
	{Or	+++++OrganisationIdentification	<OrgId>
[0..1]		++++++AnyBic	<AnyBIC>	Ultimate debtor's BIC code. BIC is mandatory in case of FPSPOO - must be owned by the institution which provides the account to the Ultimate debtor and must be a non GB BIC
[0..1]		++++++LEI	<LEI>	Organisation LEI code.
[0..n]		++++++Other	<Othr>
[1..1]		+++++++Identification	<Id>	Organisation’s identification code. Mandatory in case of FPSPOO - referring to Ultimate debtor’s account number and can be in IBAN or in other format.
[0..1]		+++++++SchemeName	<SchmeNm>
[1..1]		++++++++Code	<Cd>	See the supported values in Code Set: Organisation Identification.
	Or}	+++++PrivateIdentification	<PrvtId>
	{Or	++++++DateAndPlaceOfBirth	<DtAndPlcOfBirth>
[1..1]		+++++++BirthDate	<BirthDt>	Ultimate debtor’s birth date.
[0..1]		+++++++ProvinceOfBirth	<PrvcOfBirth>
[1..1]		+++++++CityOfBirth	<CityOfBirth>	Ultimate debtor’s city of birth.
[1..1]		+++++++CountryOfBirth	<CtryOfBirth>	Ultimate debtor’s birth country ISO code.
	Or}	++++++Other	<Othr>
[1..1]		+++++++Identification	<Id>	Ultimate debtor’s identification code.
[0..1]		+++++++SchemeName	<SchmeNm>
[1..1]		++++++++Code	<Cd>	See the supported values in Code Set: Private Person Identification.
[0..1]		++++CountryOfResidence	<CtryOfRes>	Ultimate debtor’s country of residence.
[0..1]		+++IntermediaryAgent1..3	<IntrmyAgt1..3>	Ignored. Information about the creditor’s bank’s correspondent bank.
[0..1]		+++CreditorAgent	<CdtrAgt>	Creditor agent’s information is required for SWIFT payments.
[1..1]		++++FinancialInstitutionIdentification	<FinInstnId>
[0..1]		+++++BICFI	<BICFI>	Creditor’s bank’s BIC.
[0..1]		+++++LEI	<LEI>	LEI code. Not supported, values ignored
[0..n]		+++++Othr	<Othr>	Other identifier. Not supported, values ignored
[0..1]		+++++ClearingSystemMemberIdentification	<ClrSysMmbId>
[0..1]		++++++ClearingSystemIdentification	<ClrSysId>
[1..1]		+++++++Code	<Cd>	For the clearing system’s identification code see the External Code Sets spreadsheet on the ISO website. Use GBDSC when using UK sort code and domestic account nr separately.
[1..1]		++++++MemberIdentification	<MmbId>	Creditor’s bank identification in a clearing system. Use UK sort code when using UK sort code and domestic account nr separately.
[0..1]		+++++Name	<Nm>	Creditor's bank name. Usage rule: The name is limited to 70 characters in length. Used when the BIC or the clearing system’s member identification is not known to the initiating party.
[0..1]		+++++PostalAddress	<PstlAdr>	See address structure and details here
[0..1]		+++CreditorAgentAccount	<CdtrAgtAcct>	Creditor’s bank account at its correspondent bank. Not supported, values ignored.
[1..1]		+++Creditor	<Cdtr>	Creditor’s information.
[1..1]		++++Name	<Nm>	Creditor’s name.
[0..1]		++++PostalAddress	<PstlAdr>	See address structure and details here
[0..1]		++++Identification	<Id>	Creditor’s identification.
	{Or	+++++OrganisationIdentification	<OrgId>
[0..1]		++++++AnyBic	<AnyBIC>	Creditor's BIC code.
[0..1]		++++++LEI	<LEI>	Organisation LEI code.
[0..n]		++++++Other	<Othr>	Other identifier.
[1..1]		+++++++Identification	<Id>	Organisation’s identification code.
[0..1]		+++++++SchemeName	<SchmeNm>
	[1..1]	++++++++Code	<Cd>	See the supported values in Code Set: Organisation Identification.
	Or}	+++++PrivateIdentification	<PrvtId>
	{Or	++++++DateAndPlaceOfBirth	<DtAndPlcOfBirth>
[1..1]		+++++++BirthDate	<BirthDt>	Creditor’s birth date.
[1..1]		+++++++CityOfBirth	<CityOfBirth>	Creditor’s city of birth.
[1..1]		+++++++CountryOfBirth	<CtryOfBirth>	Creditor’s birth country ISO code.
	Or}	++++++Other	<Othr>
[1..1]		+++++++Identification	<Id>	Creditor’s identification.
[0..1]		+++++++SchemeName	<SchmeNm>
[1..1]		++++++++Code	<Cd>	See the supported values in Code Set: Private Person Identification.
[1..1]		+++CreditorAccount	<CdtrAcct>	Creditor’s account.
[1..1]		++++Identification	<Id>
	{Or	+++++IBAN	<IBAN>	Creditor’s IBAN. Omit for Faster Payments when using UK domestic account nr.
	Or}	+++++Other	<Othr>
[1..1]		++++++Identification	<Id>	Creditor’s account number. Use for domestic UK account nr - separate from sort code (8 char) or concatenated (14 char)
[0..1]		++++++SchemeName	<SchmeNm>
[1..1]		+++++++Code	<Cd>	Use BBAN when using concatenated UK domestic accountr nr (14 characters), omit when using UK account nr and UK sort code separately.
[0..1]		+++UltimateCreditor	<UltmtCdtr>	SEPA specific information. Ultimate creditor is the ultimate creditor of the payment.
[0..1]		++++Name	<Nm>	Ultimate creditor’s name.
[0..1]		++++Identification	<Id>
	{Or	+++++OrganisationIdentification	<OrgId>
[0..1]		++++++AnyBic	<AnyBIC>	Ultimate creditor's BIC code.
[0..1]		++++++LEI	<LEI>	Organisation LEI code.
[0..1]		++++++Other	<Othr>	Other identifier.
[1..1]		+++++++Identification	<Id>	Ultimate creditor’s organisation identification.
[0..1]		+++++++SchemeName	<SchmeNm>
[1..1]		++++++++Code	<Cd>	See the supported values in Code Set: Organisation Identification.
	Or}	+++++PrivateIdentification	<PrvtId>
	{Or	++++++DateAndPlaceOfBirth	<DtAndPlcOfBirth>
[1..1]		+++++++BirthDate	<BirthDt>	Ultimate creditor’s birth date.
[1..1]		+++++++CityOfBirth	<CityOfBirth>	Ultimate creditor’s city of birth.
[1..1]		+++++++CountryOfBirth	<CtryOfBirth>	Ultimate creditor’s birth country ISO code.
	Or}	++++++Other	<Othr>
[1..1]		+++++++Identification	<Id>	Ultimate creditor’s identification.
[0..1]		+++++++SchemeName	<SchmeNm>
[1..1]		++++++++Code	<Cd>	See the supported values in Code Set: Private Person Identification.
[0..1]		+++InstructionForDebtorAgent>	<InstrForDbtrAgt	Used for referencing return payment for FPS or SEPA (Inst). Format: 'RTRN:00000002:12345678' where RTRN is code for return; 00000002 is Payment Scheme Return Code; 12345678 is Account Servicer Reference of original incoming payment to be returned.
[0..1]		+++Purpose	<Purp>	SEPA specific information. Reason for the payment.
[1..1]		++++Code	<Cd>	See the supported codes in Code Set: Purpose.
[0..10]		+++RegulatoryReporting	<RgltryRptg>	Information about the declaration of payments. Not supported, values ignored.
[0..1]		+++RemittanceInformation	<RmtInf>	Used to enter the payment description (unstructured) and the reference number (structured). It is mandatory to provide one or the other. Estonia: Unstructured or structured remittance information is mandatory. If Debtor´s bank locates in Estonia both can be present. If both structured and unstructured information are filled in, only 140 characters of combined length is accepted. UK: Structured remittance information is mandatory for FPS. Reference number (structured) must comply with Estonian reference standard or Creditor reference
[0..1]		++++Unstructured	<Ustrd>	Payment description is entered here. The bank will deliver only the first 140 characters of the remittance information.
[0..1]		++++Structured	<Strd>
[0..1]		+++++CreditorReferenceInformation	<CdtrRefInf>
[0..1]		++++++Type	<Tp>
[1..1]		+++++++CodeOrProprietary	<CdOrPrtry>
[1..1]		++++++++Code	<Cd>	Only the value SCOR is allowed here. If any other value is entered, it will be ignored.
[0..1]		+++++++Issuer	<Issr>
[0..1]		++++++Reference	<Ref>	Payment reference number is entered here. Estonia: If Debtor´s bank locates in Estonia then reference number must comply with Estonian reference standard or Creditor reference UK: Mandatory for FPS - text value up to 18 symbols long.
[0..n]		+++Supplementary Data	<SplmtryData>	See details in supplementary data section.
[0..1]		++++Place and Name	<PlcAndNm>	Field ignored
[1..1]		++++Data Envelope	<Envlp>
[1..1]		+++++Document	<Document>
[0..n]		++++++Party Data	<PartyData>	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. If PostalAddress is used then minimum Country and Town Name must be present. Some additional requirements apply:

• Debtor address - For Virtual IBAN or agency banking account - the holder country

• Ultimate debtor address - In case of FPSPOO and address line is filled, country must be filled

• Ultimate debtor address - In case of FPSPOO and town name is filled, then country must be filled.

• If creditor´s bank locates outside EEA address information is mandatory from 23.11.2024. The rule applies to all parties (debtor, ultimate debtor, creditor etc).

• If creditor´s bank locates in EEA but the currency is not official currency in any EEA country (for example USD) - address information is mandatory from 23.11.2024. The rule applies to all parties (debtor, ultimate debtor, creditor etc).

• If payment is processed as TARGET2 (See https://partners.lhv.ee/en/connect/#code-set-payment-scheme) - address information is mandatory from 01.03.2024. The rule applies to all parties (debtor, ultimate debtor, creditor etc).

MULT.	OR	MESSAGE ELEMENT	XML TAG	LHV REQUIREMENT
[0..1]		Department	<Dept>
[0..1]		Sub-department name	<SubDebt>
[0..1]		Street name	<StrtNm>
[0..1]		Building number	<BldgNb>
[0..1]		Building name	<BldgNm>
[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	<TwnLctnNm>
[0..1]		District name	<DstrctNm>
[0..1]		Country sub-division	<CtrySubDvsn>
[0..1]		ISO 2 letter country code	<Ctry>
[0..2]		Address line	<AdrLine>

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.

1. party - party that given data element is related to (e.g. CREDITOR, DEBTOR)

2. key - data element key (see below for supported values)

3. value - value for given data element (e.g. 1986-02-05)

Supllementary 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>
...