CustomerPaymentStatusReportV15pain.002.001.15

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 may be governed by a bilateral or multilateral 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).

Outline

The CustomerPaymentStatusReportV15 MessageDefinition is composed of 4 MessageBuildingBlocks:

  • Group Header — Set of characteristics shared by all individual transactions included in the status report message.
  • Original Group Information And Status — Original group information concerning the group of transactions, to which the status report message refers to.
  • Original Payment Information And Status — Information concerning the original payment information, to which the status report message refers.
  • Supplementary Data — Additional information that cannot be captured in the structured elements and/or any other specific block.

CustomerPaymentStatusReportV15

CstmrPmtStsRpt
Mandatory

Type: CustomerPaymentStatusReportV15

GrpHdr
Mandatory
Mandatory
Repetition (0..n)
SplmtryData
Repetition (0..n)
Instructed AgentPrevious Party In The Payment ChainCustomerPaymentStatusReportV15
We use cookies to personalize content and ads, as well as to analyze our traffic. We also share information about your use of our site with our advertising and analytics partners who may combine it with other information that you've provided to them or that they've collected from your use of their services.
DenyAllow