Iso20022

CustomerPaymentStatusReportV11

pain.002.001.11

Scope The CustomerPaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction. Usage The CustomerPaymentStatusReport message is exchanged between an agent and a non-financial institution customer to provide status information on instructions previously sent. Its usage will always be governed by a bilateral agreement between the agent and the non-financial institution customer. The CustomerPaymentStatusReport message can be used to provide information about the status (for example a rejection, an acceptance) of the initiation of a credit transfer, a direct debit, as well as on the initiation of other customer instructions. The CustomerPaymentStatusReport message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentStatusReport message can be used in domestic and cross-border scenarios. The CustomerPaymentStatusReport may also be sent to the receiver of the payment in a real time payment scenario, as both sides of the transactions must be informed of the status of the transaction (that is either the beneficiary is credited, or the transaction is rejected).

Message Construction

Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification

classDiagram
     direction LR
%% CustomerPaymentStatusReportV11 recursion level 0 with max 0
CustomerPaymentStatusReportV11 *-- "1..1" GroupHeader86 : GroupHeader
CustomerPaymentStatusReportV11 *-- "1..1" OriginalGroupHeader17 : OriginalGroupInformationAndStatus
CustomerPaymentStatusReportV11 *-- "0..1" OriginalPaymentInstruction38 : OriginalPaymentInformationAndStatus
CustomerPaymentStatusReportV11 *-- "0..1" SupplementaryData1 : SupplementaryData

Now, we will zero-in one-by-one on each of these building blocks.

GroupHeader building block

Set of characteristics shared by all individual transactions included in the status report message. Provides the characteristics shared by all individual transactions included in the message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% GroupHeader86 recursion level 0 with max 1
class GroupHeader86{
    MessageIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
GroupHeader86 *-- "0..1" PartyIdentification135 : InitiatingParty
GroupHeader86 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : ForwardingAgent
GroupHeader86 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : DebtorAgent
GroupHeader86 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : CreditorAgent
%% PartyIdentification135 recursion level 1 with max 1
class PartyIdentification135{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification135 *-- "0..1" PostalAddress24 : PostalAddress
PartyIdentification135 *-- "0..1" IParty38Choice : Identification
PartyIdentification135 *-- "0..1" Contact4 : ContactDetails
%% BranchAndFinancialInstitutionIdentification6 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification6 *-- "1..1" FinancialInstitutionIdentification18 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification6 *-- "0..1" BranchData3 : BranchIdentification
%% BranchAndFinancialInstitutionIdentification6 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification6 *-- "1..1" FinancialInstitutionIdentification18 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification6 *-- "0..1" BranchData3 : BranchIdentification
%% BranchAndFinancialInstitutionIdentification6 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification6 *-- "1..1" FinancialInstitutionIdentification18 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification6 *-- "0..1" BranchData3 : BranchIdentification

GroupHeader86 members

Member name Description Data Type / Multiplicity
MessageIdentification Point to point reference, as assigned by the instructing party, and sent to the next party in the chain to unambiguously identify the message. Usage: The instructing party has to make sure that ‘MessageIdentification’ is unique per instructed party for a pre-agreed period.
CreationDateTime Date and time at which the message was created. IsoISODateTime - Required 1..1
InitiatingParty Party that initiates the status message. PartyIdentification135 - Optional 0..1
ForwardingAgent Financial institution that receives the instruction from the initiating party and forwards it to the next agent in the payment chain. BranchAndFinancialInstitutionIdentification6 - Optional 0..1
DebtorAgent Financial institution servicing an account for the debtor. BranchAndFinancialInstitutionIdentification6 - Optional 0..1
CreditorAgent Financial institution servicing an account for the creditor. BranchAndFinancialInstitutionIdentification6 - Optional 0..1

OriginalGroupInformationAndStatus building block

Original group information concerning the group of transactions, to which the status report message refers to. Provides details on the original group, to which the message refers. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% OriginalGroupHeader17 recursion level 0 with max 1
class OriginalGroupHeader17{
    OriginalMessageIdentification IsoMax35Text
    OriginalMessageNameIdentification IsoMax35Text
    OriginalCreationDateTime IsoISODateTime
    OriginalNumberOfTransactions IsoMax15NumericText
    OriginalControlSum IsoDecimalNumber
    GroupStatus ExternalPaymentGroupStatus1Code
}
OriginalGroupHeader17 *-- "0..0" StatusReasonInformation12 : StatusReasonInformation
OriginalGroupHeader17 *-- "0..0" NumberOfTransactionsPerStatus5 : NumberOfTransactionsPerStatus
%% StatusReasonInformation12 recursion level 1 with max 1
class StatusReasonInformation12{
    AdditionalInformation IsoMax105Text
}
StatusReasonInformation12 *-- "0..1" PartyIdentification135 : Originator
StatusReasonInformation12 *-- "0..1" IStatusReason6Choice : Reason
%% NumberOfTransactionsPerStatus5 recursion level 1 with max 1
class NumberOfTransactionsPerStatus5{
    DetailedNumberOfTransactions IsoMax15NumericText
    DetailedStatus ExternalPaymentTransactionStatus1Code
    DetailedControlSum IsoDecimalNumber
}

OriginalGroupHeader17 members

Member name Description Data Type / Multiplicity
OriginalMessageIdentification Point to point reference, as assigned by the original instructing party, to unambiguously identify the original message. IsoMax35Text - Required 1..1
OriginalMessageNameIdentification Specifies the original message name identifier to which the message refers. IsoMax35Text - Required 1..1
OriginalCreationDateTime Date and time at which the original message was created. IsoISODateTime - Optional 0..1
OriginalNumberOfTransactions Number of individual transactions contained in the original message. IsoMax15NumericText - Optional 0..1
OriginalControlSum Total of all individual amounts included in the original message, irrespective of currencies. IsoDecimalNumber - Optional 0..1
GroupStatus Specifies the status of a group of transactions. ExternalPaymentGroupStatus1Code - Optional 0..1
StatusReasonInformation Provides detailed information on the status reason. StatusReasonInformation12 - Unknown 0..0
NumberOfTransactionsPerStatus Detailed information on the number of transactions for each identical transaction status. NumberOfTransactionsPerStatus5 - Unknown 0..0

OriginalPaymentInformationAndStatus building block

Information concerning the original payment information, to which the status report message refers. Provides detailed information on the original transaction, to which the status report message refers. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% OriginalPaymentInstruction38 recursion level 0 with max 1
class OriginalPaymentInstruction38{
    OriginalPaymentInformationIdentification IsoMax35Text
    OriginalNumberOfTransactions IsoMax15NumericText
    OriginalControlSum IsoDecimalNumber
    PaymentInformationStatus ExternalPaymentGroupStatus1Code
}
OriginalPaymentInstruction38 *-- "0..0" StatusReasonInformation12 : StatusReasonInformation
OriginalPaymentInstruction38 *-- "0..0" NumberOfTransactionsPerStatus5 : NumberOfTransactionsPerStatus
OriginalPaymentInstruction38 *-- "0..0" PaymentTransaction126 : TransactionInformationAndStatus
%% StatusReasonInformation12 recursion level 1 with max 1
class StatusReasonInformation12{
    AdditionalInformation IsoMax105Text
}
StatusReasonInformation12 *-- "0..1" PartyIdentification135 : Originator
StatusReasonInformation12 *-- "0..1" IStatusReason6Choice : Reason
%% NumberOfTransactionsPerStatus5 recursion level 1 with max 1
class NumberOfTransactionsPerStatus5{
    DetailedNumberOfTransactions IsoMax15NumericText
    DetailedStatus ExternalPaymentTransactionStatus1Code
    DetailedControlSum IsoDecimalNumber
}
%% PaymentTransaction126 recursion level 1 with max 1
class PaymentTransaction126{
    StatusIdentification IsoMax35Text
    OriginalInstructionIdentification IsoMax35Text
    OriginalEndToEndIdentification IsoMax35Text
    OriginalUETR IsoUUIDv4Identifier
    TransactionStatus ExternalPaymentTransactionStatus1Code
    AcceptanceDateTime IsoISODateTime
    AccountServicerReference IsoMax35Text
    ClearingSystemReference IsoMax35Text
}
PaymentTransaction126 *-- "0..0" StatusReasonInformation12 : StatusReasonInformation
PaymentTransaction126 *-- "0..0" Charges7 : ChargesInformation
PaymentTransaction126 *-- "0..1" TrackerData1 : TrackerData
PaymentTransaction126 *-- "0..1" OriginalTransactionReference31 : OriginalTransactionReference
PaymentTransaction126 *-- "0..0" SupplementaryData1 : SupplementaryData

OriginalPaymentInstruction38 members

Member name Description Data Type / Multiplicity
OriginalPaymentInformationIdentification Unique identification, as assigned by the original sending party, to unambiguously identify the original payment information group. IsoMax35Text - Required 1..1
OriginalNumberOfTransactions Number of individual transactions contained in the original payment information group. IsoMax15NumericText - Optional 0..1
OriginalControlSum Total of all individual amounts included in the original payment information group, irrespective of currencies. IsoDecimalNumber - Optional 0..1
PaymentInformationStatus Specifies the status of the payment information group. ExternalPaymentGroupStatus1Code - Optional 0..1
StatusReasonInformation Provides detailed information on the status reason. StatusReasonInformation12 - Unknown 0..0
NumberOfTransactionsPerStatus Detailed information on the number of transactions for each identical transaction status. NumberOfTransactionsPerStatus5 - Unknown 0..0
TransactionInformationAndStatus Provides information on the original transactions to which the status report message refers. PaymentTransaction126 - Unknown 0..0

SupplementaryData building block

Additional information that cannot be captured in the structured elements and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1

SupplementaryData1 members

Member name Description Data Type / Multiplicity
PlaceAndName Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. IsoMax350Text - Optional 0..1
Envelope Technical element wrapping the supplementary data. IsoSupplementaryDataEnvelope1 - Required 1..1

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the CustomerPaymentStatusReportV11 implementation follows a specific implementaiton pattern. First of all, CustomerPaymentStatusReportV11 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, CustomerPaymentStatusReportV11Document implements IOuterDocument. Because CustomerPaymentStatusReportV11 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type CustomerPaymentStatusReportV11.

classDiagram
    class IOuterRecord
    CustomerPaymentStatusReportV11 --|> IOuterRecord : Implements
    CustomerPaymentStatusReportV11Document --|> IOuterDocument~CustomerPaymentStatusReportV11~ : Implements
    class IOuterDocument~CustomerPaymentStatusReportV11~ {
        CustomerPaymentStatusReportV11 Message
     }

Document wrapper for serialization

The only real purpose CustomerPaymentStatusReportV11Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:pain.002.001.11’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using CustomerPaymentStatusReportV11.ToDocument() method. The returned CustomerPaymentStatusReportV11Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    CustomerPaymentStatusReportV11Document *-- CustomerPaymentStatusReportV11 : Document

Sample of message format

This is an abbreviated version of what the message should look like.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.11">
    <CstmrPmtStsRpt>
        <GrpHdr>
            <!-- GroupHeader inner content -->
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <!-- OriginalGroupInformationAndStatus inner content -->
        </OrgnlGrpInfAndSts>
        <OrgnlPmtInfAndSts>
            <!-- OriginalPaymentInformationAndStatus inner content -->
        </OrgnlPmtInfAndSts>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </CstmrPmtStsRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_LwEeP8P_Eemsic1bQcEtLA"
  nextVersions="_rUXmz9cBEeq_l4BJLVUF2Q"
  previousVersion="_eYI_s22PEei3KuUgpx7Xcw"
  name="CustomerPaymentStatusReportV11"
  definition="Scope&#xD;&#xA;The CustomerPaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction.&#xD;&#xA;Usage&#xD;&#xA;The CustomerPaymentStatusReport message is exchanged between an agent and a non-financial institution customer to provide status information on instructions previously sent. Its usage will always be governed by a bilateral agreement between the agent and the non-financial institution customer.&#xD;&#xA;The CustomerPaymentStatusReport message can be used to provide information about the status (for example a rejection, an acceptance) of the initiation of a credit transfer, a direct debit, as well as on the initiation of other customer instructions.&#xD;&#xA;The CustomerPaymentStatusReport message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction.&#xD;&#xA;The CustomerPaymentStatusReport message can be used in domestic and cross-border scenarios.&#xD;&#xA;The CustomerPaymentStatusReport may also be sent to the receiver of the payment in a real time payment scenario, as both sides of the transactions must be informed of the status of the transaction (that is either the beneficiary is credited, or the transaction is rejected)."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="CstmrPmtStsRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_LwEeQcP_Eemsic1bQcEtLA"
    nextVersions="_rUXm0dcBEeq_l4BJLVUF2Q"
    previousVersion="_eYI_tW2PEei3KuUgpx7Xcw"
    name="GroupStatusAcceptedRule"
    definition="If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to ACTC (AcceptedTechnicalValidation), ACCP (AcceptedCustomerProfile), ACSP (AcceptedSettlementInProcess), ACSC (AcceptedSettlementCompleted) or ACWC (AcceptedWithChange), then OriginalPaymentInformationAndStatus/PaymentInformationStatus must be different from RJCT (Rejected)."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition&gt;&lt;ComplexRule xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;NotWithInList&quot;&gt;&lt;leftOperand&gt;/OriginalPaymentInformationAndStatus[*]/PaymentInformationStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRuleRejected1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus/GroupStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;WithInList&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus/GroupStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRuleStatus1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalPaymentInformationAndStatus[*]/PaymentInformationStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;" />
  <constraint
    xmi:id="_LwEeQ8P_Eemsic1bQcEtLA"
    nextVersions="_rUXm09cBEeq_l4BJLVUF2Q"
    previousVersion="_eYI_t22PEei3KuUgpx7Xcw"
    name="GroupStatusPendingRule"
    definition="If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to PDNG (Pending), then OriginalPaymentInformationAndStatus/PaymentInformationStatus must be different from RJCT (Rejected)."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition&gt;&lt;ComplexRule xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;NotWithInList&quot;&gt;&lt;leftOperand&gt;/OriginalPaymentInformationAndStatus[*]/PaymentInformationStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRuleRejected1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus/GroupStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;WithInList&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus/GroupStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRulePending1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalPaymentInformationAndStatus[*]/PaymentInformationStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;" />
  <constraint
    xmi:id="_LwEeRcP_Eemsic1bQcEtLA"
    nextVersions="_rUXm1dcBEeq_l4BJLVUF2Q"
    previousVersion="_eYI_uW2PEei3KuUgpx7Xcw"
    name="GroupStatusRejectedRule"
    definition="If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RJCT (Rejected), then OriginalPaymentInformationAndStatus/PaymentInformationStatus, if present, must be equal to RJCT (Rejected)."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition&gt;&lt;ComplexRule xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;WithInList&quot;&gt;&lt;leftOperand&gt;/OriginalPaymentInformationAndStatus[*]/PaymentInformationStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRuleRejected1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus/GroupStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;WithInList&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus/GroupStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRuleRejected1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalPaymentInformationAndStatus[*]/PaymentInformationStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;" />
  <constraint
    xmi:id="_LwEeR8P_Eemsic1bQcEtLA"
    nextVersions="_rUXm19cBEeq_l4BJLVUF2Q"
    previousVersion="_eYI_u22PEei3KuUgpx7Xcw"
    name="GroupStatusReceivedRule"
    definition="If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RCVD (Received), then OriginalPaymentInformationAndStatus/PaymentInformationStatus is not allowed."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition&gt;&lt;ComplexRule xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/OriginalPaymentInformationAndStatus[*]/PaymentInformationStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus/GroupStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;WithInList&quot;&gt;&lt;leftOperand&gt;/OriginalGroupInformationAndStatus/GroupStatus&lt;/leftOperand&gt;&lt;rightOperand&gt;ValidationRuleReceived1Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/OriginalPaymentInformationAndStatus[1]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;" />
  <constraint
    xmi:id="_LwEeScP_Eemsic1bQcEtLA"
    nextVersions="_rUXm2dcBEeq_l4BJLVUF2Q"
    previousVersion="_eYI_vW2PEei3KuUgpx7Xcw"
    name="SupplementaryDataRule"
    definition="The SupplementaryData building block at message level must not be used to provide additional information about a transaction. The SupplementaryData element at transaction level should be used for that purpose."
    registrationStatus="Provisionally Registered" />
  <messageBuildingBlock
    xmi:id="_LwEeUcP_Eemsic1bQcEtLA"
    nextVersions="_rUXm4dcBEeq_l4BJLVUF2Q"
    previousVersion="_eYI_v22PEei3KuUgpx7Xcw"
    name="GroupHeader"
    definition="Set of characteristics shared by all individual transactions included in the status report message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="GrpHdr"
    complexType="_RILm0W49EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_LwEeU8P_Eemsic1bQcEtLA"
    nextVersions="_rUXm49cBEeq_l4BJLVUF2Q"
    previousVersion="_eYI_wW2PEei3KuUgpx7Xcw"
    name="OriginalGroupInformationAndStatus"
    definition="Original group information concerning the group of transactions, to which the status report message refers to."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="OrgnlGrpInfAndSts"
    complexType="_ZefxgW49EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_LwEeVcP_Eemsic1bQcEtLA"
    nextVersions="_rUXm5dcBEeq_l4BJLVUF2Q"
    previousVersion="_eYI_w22PEei3KuUgpx7Xcw"
    name="OriginalPaymentInformationAndStatus"
    definition="Information concerning the original payment information, to which the status report message refers."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="OrgnlPmtInfAndSts"
    complexType="_y2Vb5cloEem0vqvvoqYsqQ" />
  <messageBuildingBlock
    xmi:id="_LwEeV8P_Eemsic1bQcEtLA"
    nextVersions="_rUXm59cBEeq_l4BJLVUF2Q"
    previousVersion="_eYI_xW2PEei3KuUgpx7Xcw"
    name="SupplementaryData"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="pain"
    messageFunctionality="002"
    flavour="001"
    version="11" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.