PAIN.001.001.03 -> PAIN.001.001.09

Introduction

Banking Circle supports credit transfer instruction and status reporting using the ISO 20022 PAIN.001 and PAIN.002 message formats.

As part of the industry's ongoing adoption of ISO 20022 standards, Banking Circle is upgrading its payment initiation and status reporting messages to newer ISO 20022 versions, supporting richer payment data and alignment with evolving market practices.

📘
Ahead of upcoming industry-wide changes and to align with ISO 20022 standards, Customer Credit Transfer Initiation messages are being upgraded from PAIN.001.001.03 to PAIN.001.001.09, and Payment Status Report messages from PAIN.002.001.02 to PAIN.002.001.10.

This page describes how to migrate from using PAIN.001.001.03 to PAIN.001.001.09. The focus here are the format differences.

❗️
Support for PAIN.001.001.03 (and PAIN.002.001.02) has been deprecated, along with the current PAIN.001.001.03 API endpoint.
When interacting directly with this endpoint (i.e. not via SFTP), migration is required not only to PAIN.001.001.09, but also to the new Credit Transfer Instruction endpoint.

Field descriptions

The table below describes the PAIN.001.001.09 structure of the fields that Banking Circle are using and supporting. For the full message specification, refer to the official ISO 20022 message archive.

Certain fields may be defined as mandatory by ISO 20022; however, if they are not listed below, they have no practical effect in this context.

Logical Property	Tag Name	Description	PAIN.001.001.09 XPath
Group Header (<GrpHdr>)
Message Identification	<MsgId>	Unique message identifier assigned by the instructing party.	/Document/CstmrCdtTrfInitn/GrpHdr/MsgId
Payment Information (<PmtInf>)
Payment Information Id	<PmtInfId>	Unique identification assigned by the sending party to identify the payment information block.	/Document/CstmrCdtTrfInitn/PmtInf/PmtInfId
Requested Execution Date	<ReqdExctnDt>	Date at which the initiating party requests the clearing agent to process the payment.	/Document/CstmrCdtTrfInitn/PmtInf/ReqdExctnDt/Dt OR
	<DtTm>	Date-time variant of the requested execution date.	/Document/CstmrCdtTrfInitn/PmtInf/ReqdExctnDt/DtTm
Debtor (<Dbtr>)
Debtor Name	<Nm>	Name of the debtor (ordering party).	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/Nm
Debtor Address Line 1	<AdrLine>	Debtor unstructured address line 1.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/AdrLine[1]
Debtor Address Line 2	<AdrLine>	Debtor unstructured address line 2.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/AdrLine[2]
Debtor Address Line 3	<AdrLine>	Debtor unstructured address line 3.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/AdrLine[3]
Debtor Country Code	<Ctry>	Debtor postal address country (ISO 3166 alpha-2).	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/Ctry
Debtor Department	<Dept>	Debtor department within an organisation.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/Dept
Debtor Sub-Department	<SubDept>	Debtor sub-department within an organisation.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/SubDept
Debtor Street Name	<StrtNm>	Debtor street name.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/StrtNm
Debtor Building Number	<BldgNb>	Debtor building number.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/BldgNb
Debtor Building Name	<BldgNm>	Debtor building name.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/BldgNm
Debtor Floor	<Flr>	Debtor floor or storey within a building.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/Flr
Debtor Post Box	<PstBx>	Debtor post office box number.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/PstBx
Debtor Room	<Room>	Debtor room number.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/Room
Debtor Postal Code	<PstCd>	Debtor postal code.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/PstCd
Debtor Town Name	<TwnNm>	Debtor town or city name.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/TwnNm
Debtor Town Location Name	<TwnLctnNm>	Debtor specific location within a town.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/TwnLctnNm
Debtor District Name	<DstrctNm>	Debtor district name.	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/DstrctNm
Debtor Country Sub-Division	<CtrySubDvsn>	Debtor country sub-division (state, province, etc.).	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/PstlAdr/CtrySubDvsn
Debtor Organisation BIC	<AnyBIC>	Debtor organisation identification (AnyBIC).	/Document/CstmrCdtTrfInitn/PmtInf/Dbtr/Id/OrgId/AnyBIC
Debtor Account (<DbtrAcct>)
Debtor Account IBAN	<IBAN>	Debtor account IBAN.	/Document/CstmrCdtTrfInitn/PmtInf/DbtrAcct/Id/IBAN OR
Debtor Account Other Id	<Id>	Debtor account proprietary identifier.	/Document/CstmrCdtTrfInitn/PmtInf/DbtrAcct/Id/Othr/Id
Credit Transfer Transaction (<CdtTrfTxInf>)
Instruction Identification	<InstrId>	Unique identification assigned by the instructing party to identify the instruction.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/PmtId/InstrId
End To End Identification	<EndToEndId>	End-to-end identification assigned by the initiating party.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/PmtId/EndToEndId
Instructed Amount	<InstdAmt>	Amount and currency to be transferred (Ccy attribute carries the ISO 4217 currency code). Either InstdAmt or EqvtAmt must be present.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Amt/InstdAmt OR
Equivalent Amount	<EqvtAmt>	Amount expressed in the debtor's account currency, to be converted into CcyOfTrf. Contains Amt (with Ccy attribute) and CcyOfTrf.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Amt/EqvtAmt/Amt
Currency Of Transfer	<CcyOfTrf>	Target currency the amount should be converted into (only used with EqvtAmt).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Amt/EqvtAmt/CcyOfTrf
Charge Bearer	<ChrgBr>	Specifies which party bears the charges (SHAR, DEBT, CRED, SLEV).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/ChrgBr
Service Level	<Cd>	Agreement under which the transaction is processed (INST, NURG, URGP).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/PmtTpInf/SvcLvl/Cd OR
	<Prtry>	Proprietary service level code.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/PmtTpInf/SvcLvl/Prtry
Category Purpose Code	<Cd>	Category purpose in a coded form.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/PmtTpInf/CtgyPurp/Cd OR
	<Prtry>	Proprietary category purpose code (EPI).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/PmtTpInf/CtgyPurp/Prtry
Purpose Code	<Cd>	Underlying reason for the payment (REFU,IPRT,PENS,SALA,SUPP,RENT).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Purp/Cd OR
	<Prtry>	Proprietary purpose code (GOD,STR,CTF,OTF).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Purp/Prtry
Instruction For Debtor Agent	<InstrForDbtrAgt>	Instruction for the debtor's agent.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/InstrForDbtrAgt
Remittance Information	<Ustrd>	Unstructured remittance information.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/RmtInf/Ustrd[1]
Creditor (<Cdtr>)
Creditor Name	<Nm>	Name of the creditor (beneficiary).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/Nm
Creditor Address Line 1	<AdrLine>	Creditor unstructured address line 1.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/AdrLine[1]
Creditor Address Line 2	<AdrLine>	Creditor unstructured address line 2.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/AdrLine[2]
Creditor Address Line 3	<AdrLine>	Creditor unstructured address line 3.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/AdrLine[3]
Creditor Country Code	<Ctry>	Creditor postal address country (ISO 3166 alpha-2).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/Ctry
Creditor Department	<Dept>	Creditor department within an organisation.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/Dept
Creditor Sub-Department	<SubDept>	Creditor sub-department within an organisation.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/SubDept
Creditor Street Name	<StrtNm>	Creditor street name.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/StrtNm
Creditor Building Number	<BldgNb>	Creditor building number.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/BldgNb
Creditor Building Name	<BldgNm>	Creditor building name.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/BldgNm
Creditor Floor	<Flr>	Creditor floor or storey within a building.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/Flr
Creditor Post Box	<PstBx>	Creditor post office box number.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/PstBx
Creditor Room	<Room>	Creditor room number.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/Room
Creditor Postal Code	<PstCd>	Creditor postal code.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/PstCd
Creditor Town Name	<TwnNm>	Creditor town or city name.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/TwnNm
Creditor Town Location Name	<TwnLctnNm>	Creditor specific location within a town.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/TwnLctnNm
Creditor District Name	<DstrctNm>	Creditor district name.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/DstrctNm
Creditor Country Sub-Division	<CtrySubDvsn>	Creditor country sub-division (state, province, etc.).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/Cdtr/PstlAdr/CtrySubDvsn
Creditor Account (<CdtrAcct>)
Creditor Account IBAN	<IBAN>	Creditor account IBAN.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/CdtrAcct/Id/IBAN OR
Creditor Account Other Id	<Id>	Creditor account proprietary identifier.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/CdtrAcct/Id/Othr/Id
Creditor Agent (<CdtrAgt>)
Creditor Agent BIC	<BICFI>	Creditor agent BIC (financial institution).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/CdtrAgt/FinInstnId/BICFI OR
Creditor Agent NCC	<MmbId>	Creditor agent national clearing code (member ID).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/CdtrAgt/FinInstnId/ClrSysMmbId/MmbId
Creditor Agent Clearing System	<Cd>	Creditor agent clearing system identification code (first 2 chars used as country code).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/CdtrAgt/FinInstnId/ClrSysMmbId/ClrSysId/Cd OR
	<Prtry>	Proprietary clearing system identification.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/CdtrAgt/FinInstnId/ClrSysMmbId/ClrSysId/Prtry
Ultimate Debtor (<UltmtDbtr>)
Ultimate Debtor Name	<Nm>	Name of the ultimate debtor (original ordering party if different from debtor).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/Nm
Ultimate Debtor Address Line 1	<AdrLine>	Ultimate debtor unstructured address line 1.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/AdrLine[1]
Ultimate Debtor Address Line 2	<AdrLine>	Ultimate debtor unstructured address line 2.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/AdrLine[2]
Ultimate Debtor Address Line 3	<AdrLine>	Ultimate debtor unstructured address line 3.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/AdrLine[3]
Ultimate Debtor Country Code	<Ctry>	Ultimate debtor postal address country (ISO 3166 alpha-2).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/Ctry
Ultimate Debtor Department	<Dept>	Ultimate debtor department within an organisation.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/Dept
Ultimate Debtor Sub-Department	<SubDept>	Ultimate debtor sub-department within an organisation.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/SubDept
Ultimate Debtor Street Name	<StrtNm>	Ultimate debtor street name.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/StrtNm
Ultimate Debtor Building Number	<BldgNb>	Ultimate debtor building number.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/BldgNb
Ultimate Debtor Building Name	<BldgNm>	Ultimate debtor building name.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/BldgNm
Ultimate Debtor Floor	<Flr>	Ultimate debtor floor or storey within a building.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/Flr
Ultimate Debtor Post Box	<PstBx>	Ultimate debtor post office box number.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/PstBx
Ultimate Debtor Room	<Room>	Ultimate debtor room number.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/Room
Ultimate Debtor Postal Code	<PstCd>	Ultimate debtor postal code.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/PstCd
Ultimate Debtor Town Name	<TwnNm>	Ultimate debtor town or city name.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/TwnNm
Ultimate Debtor Town Location Name	<TwnLctnNm>	Ultimate debtor specific location within a town.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/TwnLctnNm
Ultimate Debtor District Name	<DstrctNm>	Ultimate debtor district name.	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/DstrctNm
Ultimate Debtor Country Sub-Division	<CtrySubDvsn>	Ultimate debtor country sub-division (state, province, etc.).	/Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/UltmtDbtr/PstlAdr/CtrySubDvsn

Breaking Changes

ClearingNetwork selection replaced

ClearingNetwork capabilities are no longer supported and is replaced by Service Levels. This also means that <LclInstrm> is no longer used.

In PAIN.001.001.09 it is now allowed to provide multiple service levels under <PmtTpInf>/<SvcLvl>, which introduces the ability to provide a prioritized list of service levels (replacing clearing network capability).

Only allowed values in SvcLvl: INST, NURG, URGP

See NEW Payment Routing Controls for more information.

Disallowed tags on PaymentInformation level

The following fields are no longer allowed to be set on PaymentInformation (<PmtInf>) level and must be set on CreditTransferTransactionInformation (<CdtTrfTxInf>) level instead. If any of the below fields appear directly under <PmtInf> it will cause a validation failure.

ChargeBearer (<ChrgBr>)
UltimateDebtor (<UltmtDbtr>)
PaymentTypeInformation (<PmtTpInf>)
InstructionForDebtorAgent (<InstrForDbtrAgt>)

Require Payment Method = TRF

The only supported value in <PmtMtd> is TRF. While the field is not actively used, any value other than TRF (Credit Transfer) will result in a validation failure.

Remittance Information

Only the first <Ustrd> element under <RmtInf> is used; any additional entries are ignored. Each <Ustrd> element supports a maximum of 140 characters, as defined by ISO.

Internally, this single line is split into RemittanceInformationLine1, RemittanceInformationLine2, RemittanceInformationLine3, and RemittanceInformationLine4, each with a maximum length of 35 characters

Stricter field length validation

Stricter field length validation will be applied to a range of fields, replacing the current behaviour of truncation. Continued truncation can be enabled via an explicit opt-in.

See more details at the new Credit Transfer Instruction Endpoint.

📘
A PAIN.001.001.09 sent via SFTP will always use the truncation logic

Field Mappings

Below sections show examples of how fields/content is now mapped/shown differently.

PAIN.001.001.09

<!-- OLD: pain.001.001.03 -->
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03">
  <CstmrCdtTrfInitn>...</CstmrCdtTrfInitn>
</Document>
 
<!-- NEW: pain.001.001.09 -->
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.09">
  <CstmrCdtTrfInitn>...</CstmrCdtTrfInitn>
</Document>

<!-- OLD: pain.001.001.03 — plain date -->
<ReqdExctnDt>2026-06-15</ReqdExctnDt>
 
<!-- NEW: pain.001.001.09 — wrapped in a choice element -->
<ReqdExctnDt>
  <Dt>2026-06-15</Dt>
</ReqdExctnDt>

<!-- OLD: pain.001.001.03 -->
<FinInstnId>
  <BIC>SXPYDKKKXXX</BIC>
</FinInstnId>
 
<!-- NEW: pain.001.001.09 -->
<FinInstnId>
  <BICFI>SXPYDKKKXXX</BICFI>
</FinInstnId>

<!-- OLD: pain.001.001.03 (only one SvcLvl allowed)-->
<PmtTpInf>
  <SvcLvl>
    <Cd>INST</Cd>
  </SvcLvl>
</PmtTpInf>
 
<!-- NEW: pain.001.001.09 (multiple SvcLvls allowed)-->
<PmtTpInf>
  <SvcLvl>
    <Cd>INST</Cd>
  </SvcLvl>
  <SvcLvl>
    <Cd>NURG</Cd>
  </SvcLvl>
</PmtTpInf>

<!-- OLD: pain.001.001.03 — PmtTpInf, InstrForDbtrAgt, UltmtDbtr and ChrgBr at PmtInf level (applied to all transactions) -->
<PmtInf>
  <PmtTpInf>...</PmtTpInf>
  <InstrForDbtrAgt>...</InstrForDbtrAgt>
  <UltmtDbtr>...</UltmtDbtr>
  <ChrgBr>...</ChrgBr>
  <CdtTrfTxInf>
    <!-- Transaction inherits PmtTpInf, InstrForDbtrAgt, UltmtDbtr and ChrgBr from PmtInf -->
  </CdtTrfTxInf>
  <CdtTrfTxInf>
    <!-- This transaction also inherits PmtTpInf, InstrForDbtrAgt, UltmtDbtr and ChrgBr from PmtInf -->
  </CdtTrfTxInf>
</PmtInf>
 
<!-- NEW: pain.001.001.09 — PmtTpInf, InstrForDbtrAgt, UltmtDbtr and ChrgBr must be on each CdtTrfTxInf -->
<PmtInf>
  <!-- NO PmtTpInf, InstrForDbtrAgt, UltmtDbtr and ChrgBr here -->
  <CdtTrfTxInf>
    <PmtTpInf>...</PmtTpInf>
    <InstrForDbtrAgt>...</InstrForDbtrAgt>
    <UltmtDbtr>...</UltmtDbtr>
    <ChrgBr>...</ChrgBr>
    <!-- ... -->
  </CdtTrfTxInf>
  <CdtTrfTxInf>
    <PmtTpInf>...</PmtTpInf>
    <InstrForDbtrAgt>...</InstrForDbtrAgt>
    <UltmtDbtr>...</UltmtDbtr>
    <ChrgBr>...</ChrgBr> 
    <!-- ... -->
  </CdtTrfTxInf>
</PmtInf>

PAIN.002.001.10

<!-- OLD: pain.002.001.03 -->
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.03">
  <CstmrPmtStsRpt>...</CstmrPmtStsRpt>
</Document>
 
<!-- NEW: pain.002.001.10 -->
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.10">
  <CstmrPmtStsRpt>...</CstmrPmtStsRpt>
</Document>

<!-- OLD: pain.002.001.03 -->
<GrpHdr>
  <MsgId>...</MsgId>
  <CreDtTm>...</CreDtTm>
  <InitgPty>
    <Id>
      <OrgId>
        <BICOrBEI>SXPYDKKKXXX</BICOrBEI>
      </OrgId>
    </Id>
  </InitgPty>
</GrpHdr>
 
<!-- NEW: pain.002.001.10 -->
<GrpHdr>
  <MsgId>...</MsgId>
  <CreDtTm>...</CreDtTm>
  <InitgPty>
    <Id>
      <OrgId>
        <AnyBIC>SXPYDKKKXXX</AnyBIC>
      </OrgId>
    </Id>
  </InitgPty>
</GrpHdr>

PAIN.002.001.10 Response

Partially processed not supported

As partial processing is no longer supported (see the Credit Transfer Instruction Endpoint), all instructions in a PAIN.001.001.09 file are either ACCEPTED or REJECTED. A single error in any instruction results in a full rejection of the file.

Statuses

If GrpSts = ACCP it means all instructions in the file was accepted for processing. If GrpSts = RJCT it means all instructions in the file was rejected and none sent for processing.

<!-- OLD: pain.002.001.03 when all instructions are accepted (GrpSts = ACCP) all instructions are returned with ACCP as well -->
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.03">
  <CstmrPmtStsRpt>
    <GrpHdr>
      ...
    </GrpHdr>
    <OrgnlGrpInfAndSts>
      <OrgnlMsgId>...</OrgnlMsgId>
      <OrgnlMsgNmId>...</OrgnlMsgNmId>
      <GrpSts>ACCP</GrpSts>
    </OrgnlGrpInfAndSts>
    <OrgnlPmtInfAndSts>
      <OrgnlPmtInfId>...</OrgnlPmtInfId>
      <TxInfAndSts>
        <OrgnlEndToEndId>...</OrgnlEndToEndId>
        <TxSts>ACCP</TxSts>
      </TxInfAndSts>
    </OrgnlPmtInfAndSts>
    <OrgnlPmtInfAndSts>
      <OrgnlPmtInfId>...</OrgnlPmtInfId>
      <TxInfAndSts>
        <OrgnlEndToEndId>...</OrgnlEndToEndId>
        <TxSts>ACCP</TxSts>
      </TxInfAndSts>
    </OrgnlPmtInfAndSts>
  </CstmrPmtStsRpt>
</Document>
 
<!-- NEW: pain.002.001.10 when all instructions are accepted (GrpSts = ACCP) no instructions are returned. If GrpSts = ACCP then all instructions was accepted -->
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.10">
  <CstmrPmtStsRpt>
    <GrpHdr>
      ...
    </GrpHdr>
    <OrgnlGrpInfAndSts>
      <OrgnlMsgId>...</OrgnlMsgId>
      <OrgnlMsgNmId>...</OrgnlMsgNmId>
      <GrpSts>ACCP</GrpSts>
    </OrgnlGrpInfAndSts>
  </CstmrPmtStsRpt>
</Document>

<!-- OLD: pain.002.001.03 when any instruction are rejected (GrpSts = RJCT) all instructions are returned with RJCT as well -->
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.03">
  <CstmrPmtStsRpt>
    <GrpHdr>
      ...
    </GrpHdr>
    <OrgnlGrpInfAndSts>
      <OrgnlMsgId>...</OrgnlMsgId>
      <OrgnlMsgNmId>...</OrgnlMsgNmId>
      <GrpSts>RJCT</GrpSts>
    </OrgnlGrpInfAndSts>
    <OrgnlPmtInfAndSts>
      <OrgnlPmtInfId>...</OrgnlPmtInfId>
      <TxInfAndSts>
        <OrgnlEndToEndId>...</OrgnlEndToEndId>
        <TxSts>RJCT</TxSts>
        <StsRsnInf>
          <Rsn>
            <Cd>AM12</Cd>
          </Rsn>
          <AddtlInf>BC Amount decimal not allowed or amount is missing</AddtlInf>
          <AddtlInf>../PmtInf/CdtTrfTxInf/Amt/InstdAmt</AddtlInf>
        </StsRsnInf>
      </TxInfAndSts>
    </OrgnlPmtInfAndSts>
    <OrgnlPmtInfAndSts>
      <OrgnlPmtInfId>...</OrgnlPmtInfId>
      <TxInfAndSts>
        <OrgnlEndToEndId>...</OrgnlEndToEndId>
        <TxSts>RJCT</TxSts>
        <!-- This instruction has no error, but is still returned with a StsRsn -->
        <StsRsnInf>
          <Rsn>
            <Cd>NARR</Cd>
          </Rsn>
          <AddtlInf>Error on other payment</AddtlInf>
        </StsRsnInf>
      </TxInfAndSts>
    </OrgnlPmtInfAndSts>
  </CstmrPmtStsRpt>
</Document>
 
<!-- NEW: pain.002.001.10 when any instruction are rejected(GrpSts = RJCT) only instructions with errors are returned. If GrpSts = RJCT then all instructions was rejected. -->
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.10">
  <CstmrPmtStsRpt>
    <GrpHdr>
      ...
    </GrpHdr>
    <OrgnlGrpInfAndSts>
      <OrgnlMsgId>...</OrgnlMsgId>
      <OrgnlMsgNmId>...</OrgnlMsgNmId>
      <GrpSts>RJCT</GrpSts>
    </OrgnlGrpInfAndSts>
    <OrgnlPmtInfAndSts>
      <OrgnlPmtInfId>...</OrgnlPmtInfId>
      <TxInfAndSts>
        <OrgnlEndToEndId>...</OrgnlEndToEndId>
        <TxSts>RJCT</TxSts>
        <StsRsnInf>
          <Rsn>
            <Cd>CH20</Cd>
          </Rsn>
          <AddtlInf>Number of amount decimals not supported by amount currency</AddtlInf>
          <AddtlInf>/Document/CstmrCdtTrfInitn/PmtInf[1]/CdtTrfTxInf[1]/Amt</AddtlInf>
        </StsRsnInf>
      </TxInfAndSts>
    </OrgnlPmtInfAndSts>
  </CstmrPmtStsRpt>
</Document>

SFTP

Clients using SFTP to instruct PAIN.001.001.03 can continue to deliver PAIN.001.001.09 files in the same way. The message version is determined based on the namespace tag, identifying whether the file is PAIN.001 version 3 or version 9.

Do note however that the response file is delivered in the same location as for v3 files, meaning that you can expect to receive both PAIN.002.001.03 and PAIN.002.001.10 - of course depending on what you send.