The differences described in pacs.008 Differences from CPMI Harmonisation Requirements also apply when the same fields are used in pacs.002.
In addition, for the pacs.002
confirmation message, the Nexus message guidelines have the following differences from the CBPR+ guidelines:
The Original Group Information (OrgnlGrpInf) is optional in Nexus in line with the CPMI recommendations, while this is mandatory in CBPR+.
The Original End-to-End Identification (OrgnlEndToEndId) is optional in Nexus in line with the CPMI recommendations, while this is mandatory in CBPR+.
The Status Reason Information is mandatory (in case the transaction status is RJCT
) in Nexus in line with the CPMI recommendations, while this is optional in CBPR+.
The pacs.002
message is the response to the pacs.008
payment instruction.
For further detail on each element in the pacs.002
, please refer to the Message Guidelines (Excel).
The pacs.002
message is used to respond to a pacs.008
. A pacs.002
message can indicate either the acceptance or the rejection of a payment.
The pacs.002
must reference the original pacs.008
by including the original in the section Transaction Information and Status.
A pacs.002
message can indicate either the acceptance or the rejection of a payment.
The Destination PSP must include the transaction status .
In the case the status is RJCT
(reject) the pacs.002
must include a correct ISO 20022 Status Reason
code, as listed below, in the element … >Transaction Status > Status Reason Information.
The Instructing Agent and Instructed Agent need to be filled in the Transaction Information and Status
section, not in the Group Header
, in line with the CPMI guidelines.
The Instructing Agent and Instructed Agent must be filled
Reason codes are taken from the ISO 20022 External Code Set. The code set to be used for errors is the ExternalStatusReason1Code.
Translation of error codes: Nexus does not prescribe a specific message format for the interaction between the IPS and its Participants. Where an IPS uses a different error code list domestically, it is the responsibility of the IPSO to map their domestic error codes onto the ISO 20022 codes while keeping the highest level of detail. See Translation To/From Domestic Message Formats
ExternalStatusReason1Code
AB01
AbortedClearingTimeout
Clearing process aborted due to timeout.
AB02
AbortedClearingFatalError
Clearing process aborted due to a fatal error.
AB03
AbortedSettlementTimeout
Settlement aborted due to timeout.
AB04
AbortedSettlementFatalError
Settlement process aborted due to a fatal error.
AB05
TimeoutCreditorAgent
Transaction stopped due to timeout at the Creditor Agent.
AB06
TimeoutInstructedAgent
Transaction stopped due to timeout at the Instructed Agent (the Destination SAP).
AB08
OfflineCreditorAgent
Creditor Agent is not online.
AB09
ErrorCreditorAgent
Transaction stopped due to error at the Creditor Agent.
AB10
ErrorInstructedAgent
Transaction stopped due to error at the Instructed Agent.
AC04
ClosedAccountNumber
Account number specified has been closed on the bank of account's books.
AC06
BlockedAccount
Account specified is blocked, prohibiting posting of transactions against it.
AC07
ClosedCreditorAccountNumber
Creditor account number closed
AC14
InvalidCreditorAccountType
Creditor Account type not allowed (f.e. savings account)
AG01
TransactionForbidden
Transaction forbidden on this type of account (formerly NoAgreement)
AG03
TransactionNotSupported
Transaction type not supported/authorized on this account
AG11
CreditorAgentSuspended
Creditor Agent of message is suspended from the Real Time Payment system.
AGNT
IncorrectAgent
Agent in the payment workflow is incorrect
AM02
NotAllowedAmount
Specific transaction/message amount is greater than allowed maximum
AM03
NotAllowedCurrency
Specified message amount is an non processable currency outside of existing agreement
AM04
InsufficientFunds
Amount of funds available to cover specified message amount is insufficient. This would be the case for the FXP account at the D-PSP.
AM05
Duplication
Duplication
AM06
TooLowAmount
Specified transaction amount is less than agreed minimum.
AM07
BlockedAmount
Amount specified in message has been blocked by regulatory authorities.
AM13
AmountExceedsClearingSystemLimit
Transaction amount exceeds limits set by clearing system
AM14
AmountExceedsAgreedLimit
Transaction amount exceeds limits agreed between bank and client
AM15
AmountBelowClearingSystemMinimum
Transaction amount below minimum set by clearing system
AM21
LimitExceeded
Transaction amount exceeds limits agreed between bank and client.
AM23
AmountExceedsSettlementLimit
Transaction amount exceeds settlement limit.
BE01
InconsistenWithEndCustomer
Identification of end customer is not consistent with associated account number. (formerly CreditorConsistency).
BE04
MissingCreditorAddress
Specification of creditor's address, which is required for payment, is missing/not correct (formerly IncorrectCreditorAddress).
BE05
UnrecognisedInitiatingParty
Party who initiated the message is not recognised by the end customer
BE06
UnknownEndCustomer
End customer specified is not known at associated Sort/National Bank Code or does no longer exist in the books
BE07
MissingDebtorAddress
Specification of debtor's address, which is required for payment, is missing/not correct.
CH11
CreditorIdentifierIncorrect
Value in Creditor Identifier is incorrect
CH20
DecimalPointsNotCompatibleWithCurrency
Number of decimal points not compatible with the currency
CH21
RequiredCompulsoryElementMissing
Mandatory element is missing
CNOR
CreditorBankIsNotRegistered
Creditor bank is not registered under this BIC in the CSM
CURR
IncorrectCurrency
Currency of the payment is incorrect
DU01
DuplicateMessageID
Message Identification is not unique.
DU02
DuplicatePaymentInformationID
Payment Information Block is not unique.
DU03
DuplicateTransaction
Transaction is not unique.
DU04
DuplicateEndToEndID
End To End ID is not unique.
DU05
DuplicateInstructionID
Instruction ID is not unique.
DUPL
DuplicatePayment
Payment is a duplicate of another payment
ED05
SettlementFailed
Settlement of the transaction has failed.
ED06
SettlementSystemNotAvailable
Interbank settlement system not available.
FF10
BankSystemProcessingError
File or transaction cannot be processed due to technical issues at the bank side
FR01
Fraud
Returned as a result of fraud.
MD07
EndCustomerDeceased
End customer is deceased.
MS02
NotSpecifiedReasonCustomerGenerated
Reason has not been specified by end customer
MS03
NotSpecifiedReasonAgentGenerated
Reason has not been specified by agent.
NARR
Narrative
Reason is provided as narrative information in the additional reason information.
RC04
InvalidCreditorBankIdentifier
Creditor bank identifier is invalid or missing
RC07
InvalidCreditorBICIdentifier
Creditor BIC identifier is invalid or missing
RC10
InvalidCreditorClearingSystemMemberIdentifier
Creditor ClearingSystemMember identifier is invalid or missing
RC11
InvalidIntermediaryAgent
Intermediary Agent is invalid or missing
RR02
MissingDebtorNameOrAddress
Specification of the debtor’s name and/or address needed for regulatory requirements is insufficient or missing.
RR03
MissingCreditorNameOrAddress
Specification of the creditor’s name and/or address needed for regulatory requirements is insufficient or missing.
RR04
RegulatoryReason
Regulatory Reason
TM01
InvalidCutOffTime
Associated message, payment information block, or transaction was received after agreed processing cut-off time.
UCRD
UnknownCreditor
Unknown Creditor.
Which error code is to be used in which situation is defined in the following diagram:
Please see the pacs.002
Nexus Message Usage Guidelines for details of the limited transformations made to this message.