MESSAGE acmt.024 Identification Verification Report

The acmt.024 is the response to the acmt.023 proxy resolution or account resolution request.

For further detail on each element in the acmt.023 and acmt.024, please refer to the Message Guidelines (Excel).

Structure of the acmt.024 Identification Verification Response V03

Main blocks of the acmt.024 Identification Verification Request

The acmt.024 is also split into two blocks:

• Similarly to the acmt.023 message, the acmt.024 the Assignment block contains information about who is making the request and providing the response

  • Creator remains the same as the acmt.023, describing the Sender who made the original proxy or account resolution request

  • First Agent remains the same as the acmt.023, describing the Source PSP

  • Assigner changes to the Destination Proxy Directory Operator

  • Assignee changes to the Source PSP (ie is the same as First Agent)

• The Report block contains the information about the Recipient:

  • Verification is either true (if the payment can proceed) or false (if any error means that the payment cannot proceed)

  • Reason will only be filled if Verification is false, and will contain an error code explaining why the verification failed (eg proxy not registered). (See Error codes below).

  • OriginalPartyAndAccountIdentification is an exact copy of the “PartyAndAccountIdentification” from the acmt.023

  • UpdatedPartyAndAccountIdentification is where the updated information (from either the Proxy Directory or the Destination PSP) is provided

acmt.024 for Proxy Resolution

For a proxy resolution request, the Destination PSP should add the following information to the UpdatedPartyAndAccountIdentification block:

• … > Party > Name – this is the verified name of the account holder, in full. It can be used by the Source PSP for sanctions screening.

• … > Account > Identification > IBAN or Account > Identification > Other > Identification - this identifies the specific account of the Recipient/Creditor

• … > Account > Name (in Nexus this is the display name of the Recipient, which can be shown to the Sender)

• … > .Agent > FinancialInstitutionIdentification > BICFI (or Agent > FinancialInstitutionIdentification > ClearingSystemMemberIdentification > MemberIdentification, for non-BIC IDs)

acmt.024 for Account Resolution

For an account resolution, the Destination PSP should add the following information added to the UpdatedPartyAndAccountIdentification block:

• … > Party > Name

• … > Party > PostalAddress

  • At least Country and Town Name should be provided here, to support with sanctions screening and other compliance checks and to ensure alignment with the CPMI’s ISO 20022 harmonization requirements.
• (Optional) Party > Identification > PrivateIdentification > DateAndPlaceOfBirth

  • This is optional but can help to reduce false alerts against sanctions screening lists

• Account > Name

  • To be used as the display name shown to the Sender, to enable confirmation of payee. This display name can be partially masked.

Message transformation by Nexus

When an acmt.024 travels through Nexus, Nexus will update the Assignee to the Id of the Source PSP. This is the only change.

Error codes

If there is an error either with proxy resolution or account resolution, an acmt.024 should be sent:

• The element … > Report > Verification should be set to false

• The element … > Report > Reason > Code should be set to the appropriate error code from the table below

Error codes are taken from the ISO 20022 External Code Set.

The standard acmt.024 Message Guidelines (Excel) specify that error codes must be from the ExternalVerificationReason1Code set, but there are only 3 codes in this set and they are insufficient. For that reason, we propose to also permit codes from the ExternalStatusReason1Code set, with the following limited code set:

Table: ISO 20022 Error Codes for use in Nexus acmt.024

Code Type	Code Value	Code Name	Nexus-specific meaning	Proxy / Account Resolution
ExternalVerificationReason1Code	AC01	Incorrect Account Number	Account number provided does not match any account held by the Creditor Agent	Account
ExternalStatusReason1Code	AC04	Closed Account Number	Account number specified has been closed on the Receiver’s books	Account
ExternalStatusReason1Code	AC06	Blocked Account	Account specified is blocked, prohibiting posting of transactions against it.	Account
ExternalVerificationReason1Code	AGNT	Incorrect Agent	The PSP exists but is not onboarded with Nexus, so cannot receive Nexus payments. Alternative payment rails may work. (Contrast to RC07 Invalid Creditor BIC)	Both
ExternalStatusReason1Code	AB08	Offline Creditor Agent	Creditor Agent is not able to respond to account resolution requests, either permanently (they don’t have the capability) or temporarily (they are offline or have a technical issue).	Account
ExternalStatusReason1Code	BE23	Account Proxy Invalid	Proxy is not registered (No account is associated with the proxy provided)	Proxy
ExternalStatusReason1Code	DUPL	Duplicate Request		Both
ExternalStatusReason1Code	FRAD	Fraudulent Origin	Proxy directory, IPSO or Destination PSP suspects abuse of the proxy resolution service by the Sender and is refusing additional requests from this Sender.	Both
ExternalStatusReason1Code	MD07	End Customer Deceased		Both
ExternalStatusReason1Code	RC06	Invalid Debtor BIC Identifier	BIC provided is not a valid BIC.	Both
ExternalStatusReason1Code	RC07	Invalid Creditor BIC Identifier	The FI ID is not valid or blank. Could be used for account resolution or proxy resolution where the Creditor Agent BIC is required, such as the Philippines. (In contrast to AGNT, RC07 means that the FI ID is incorrect and the PSP is not found.)	Both
ExternalStatusReason1Code	RR01	Missing Debtor Account Or Identification	The Destination Country requires further information about the Sender in order to pre-screen the Sender.	Both
ExternalStatusReason1Code	RR02	Missing Debtor Name Or Address	The Destination Country requires further information about the Sender in order to pre-screen the Sender.	Both