Usage

The pacs.002.001.10 message is the Financial Institution to Financial Institution Payment Status Report. It provides the status of a (set of) payment(s) at a certain point of time during its processing.

It is possible to send or receive multiple pacs.002.001.10 messages for the same payment but they must be ordered and obey a certain logic (e.g. a payment cannot be rejected and then accepted).

To lift any ambiguity and possible interpretation of a Payment Status Report file, the additional definitions and business rules below will be applied by Mambu Payments.

Definitions

Group level statuses

The Group Level Status is located under the Original Group Information and Status tag OrgnlGrpInfAndSts.GrpSts. Accepted values are the following:

Status	Definition
`RCVD`	Received: the message has been received by the instructed agent but has not been processed nor validated yet.
`ACCP`	Accepted: the message has been accepted for processing by the bank.
`RJCT`	Rejected: the entire group of transactions has been rejected.
`PART`	Partially accepted: The group has been processed, but a subset of the transactions were rejected. This status is typically followed by detailed transaction status reports indicating which payments failed.

Transaction level statuses

The Transaction Level Status is located under the Transaction Information and Status tag TxInfAndSts.TxSts. Accepted values are the following:

Status	Definition
`ACCP`	Accepted: the individual payment has been successfully processed by the instructed agent and is on its way for settlement or has been booked/credited.
`RJCT`	Rejected: the individual payment has failed a validation check (technical, regulatory, or business rule check) and will not be processed. The money has not been moved.
`ACSP`	Accepted settlement in process: the individual payment has been accepted and is currently undergoing the final clearing and settlement process.
`ACSC`	Accepted settlement completed: the individual payment has been settled on the debtor's account, meaning that the funds has successfully left the debtor account and delivered to the CSM or the next agent in the payment chain.
`PDNG`	Pending: the individual payment is currently waiting for validation, verification (e.g., compliance check), or a further process decision.

Business rules

Outgoing payment messages acknowledge

Mambu Payments determines whether a message has been correctly received by the user by analysing the status code of the outgoing request: either the HTTP status code for API or Webhook request or the SFTP status code for SFTP request.

Happy path

The happy path is characterised by an HTTP 2xx status code for API or Webhook request or the SFTP ACK for SFTP request.

Outgoing Message ID	Message name	Payment status transition
pacs.008.001.08	FIToFICustomerCreditTransferV08	`processing` > `sent`
pain.001.001.03	CustomerCreditTransferInitiationV03	`processing` > `sent`
pacs.003.001.08	FIToFICustomerDirectDebitV08	`processing` > `sent`
pain.008.001.02	CustomerDirectDebitInitiationV02	`processing` > `sent`
pacs.002.001.10	FIToFIPaymentStatusReportV10	No effect
pain.002.001.10	CustomerPaymentStatusReportV10	No effect
camt.053.001.02	BankToCustomerStatementV02	No effect
pacs.004.001.09	PaymentReturnV09	The outgoing return transitions from `processing` > `sent` The underlying incoming payment transitions from `received` > `pending_return` if it was not already in `pending_return` status
camt.029.001.09	ResolutionOfInvestigationV09	The status of the incoming return request related to this camt.029 transitions from `received` > `denied` The underlying incoming payment transitions from `pending_return` > `received`
camt.056.001.08	FIToFIPaymentCancellationRequestV08	The outgoing return request status transitions from `processing` > `sent` The underlying outgoing payment transitions from `executed` > `pending_return`
pacs.007.001.09	FIToFIPaymentReversalV09	The outgoing return transitions from `processing` > `sent` The underlying incoming payment transitions from `received` > `pending_return` if it was not already in `pending_return` status
pacs.028.001.03	FIToFIPaymentStatusRequestV03	No effect
camt.027.001.07	ClaimNonReceiptV07	No effect
camt.087.001.06	RequestToModifyPaymentV06	No effect

Errors

SFTP error

HTTP 400

HTTP 404

HTTP 409

HTTP 401 / 403

HTTP 5xx

Identification of original payment

Priority level	Combination
1	`OrgnlMsgId` + `OrgnlTxId` `OrgnlMsgId` + `OrgnlUETR`
2	`OrgnlMsgId` + `OrgnlEndToEndId`
3	`OrgnlMsgId` + `OrgnlInstrId`
4	`OrgnlTxId` `OrgnlUETR`
5	`OrgnlEndToEndId`
6	`OrgnlInstrId`
7	`OrgnlMsgId`

Status priority processing

Business rule order	Description
BR1	If `TxInfAndSts` is present at least once, then the status of the individual payment referenced by `TxInfAndSts` is updated as follows : `RJCT`: the individual payment is `rejected` `PDNG`: the individual payment is `pending` `ACCP`, `ACSP` or `ACSC`: the individual payment is `executed`
BR2	If `TxInfAndSts` is absent, then the status of the group of payments referenced by `GrpInfAndSts` are updated as follows: `RJCT`: all payments in the group are `rejected` `RCVD`: no change in the status `ACCP`: either no change in the status or all payments in the group are `executed` (*) `PART`: should not happen as transaction level detail is expected
BR3	If BR1 is verified, then the status of the group of payments referenced by `GrpInfAndSts` are updated as follows: `RJCT` or `ACCP`: no impact as it has already been handled at transaction level `RCVD`: not expected `PART`: all remaining payments in the group that were not explicitly mentioned in BR1 are either unchanged or `executed` (*)

Business rule order

Description

BR1

If TxInfAndSts is present at least once, then the status of the individual payment referenced by TxInfAndSts is updated as follows :

RJCT: the individual payment is rejected
PDNG: the individual payment is pending
ACCP, ACSP or ACSC: the individual payment is executed

BR2

If TxInfAndSts is absent, then the status of the group of payments referenced by GrpInfAndSts are updated as follows:

RJCT: all payments in the group are rejected
RCVD: no change in the status
ACCP: either no change in the status or all payments in the group are executed (*)
PART: should not happen as transaction level detail is expected

BR3

If BR1 is verified, then the status of the group of payments referenced by GrpInfAndSts are updated as follows:

RJCT or ACCP: no impact as it has already been handled at transaction level
RCVD: not expected
PART: all remaining payments in the group that were not explicitly mentioned in BR1 are either unchanged or executed (*)

pacs.002.001.10 XSD schema and business logic