> For the complete documentation index, see [llms.txt](https://docs.nexusglobalpayments.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexusglobalpayments.org/messaging-and-translation/message-acmt.024-identification-verification-report.md).

# 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)](/messaging-and-translation/message-guidelines-excel.md).

### Structure of the acmt.024 Identification Verification Response V03 <a href="#toc159257084" id="toc159257084"></a>

<figure><img src="https://260996932-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdlTzGEXDmi664xppppmm%2Fuploads%2Fgit-blob-90bde8db4085ce363dc563194ab9faa6d966bb98%2Facmt024_main_blocks.png?alt=media" alt=""><figcaption><p>Main blocks of the acmt.024 Identification Verification Request</p></figcaption></figure>

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 [#toc143525641](#toc143525641 "mention") *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 <a href="#toc143525638" id="toc143525638"></a>

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 <a href="#toc143525639" id="toc143525639"></a>

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](https://www.bis.org/cpmi/publ/d218.htm).
* (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 <a href="#toc143525640" id="toc143525640"></a>

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 <a href="#toc143525641" id="toc143525641"></a>

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](https://www.iso20022.org/catalogue/additional-content-messages/external-code-sets), which specify that `acmt.024`  error codes must be from the **ExternalVerificationReason1Code** set.

#### Table: ISO 20022 Error Codes for use in Nexus acmt.024 <a href="#toc143525642" id="toc143525642"></a>

<table><thead><tr><th>Code Type</th><th width="75">Code Value</th><th width="143">Code Name</th><th width="283">Nexus-specific meaning</th><th>Proxy / Account Resolution</th></tr></thead><tbody><tr><td>ExternalVerificationReason1Code</td><td>FF01</td><td>InvalidFileFormat</td><td>The acmt.023 is structurally invalid or fails schema/usage-rule validation (e.g. mandatory element missing, malformed proxy or account identifier). The Source PSP must correct and resubmit.</td><td>Both</td></tr><tr><td>ExternalVerificationReason1Code</td><td>DUPL</td><td>DuplicateRequest</td><td>The acmt.023 repeats a request already received (same Assignment Id / Verification Id). The original response stands; no new resolution is performed.</td><td>Both</td></tr><tr><td>ExternalVerificationReason1Code</td><td>TM01</td><td>InvalidCutOffTime</td><td>The request was received outside the Destination IPS / Proxy Directory or Destination PSP's resolution service hours. Retry when the service window reopens.</td><td>Both</td></tr><tr><td>ExternalVerificationReason1Code</td><td>AGNT</td><td>IncorrectAgent</td><td>An agent identifier in the request is inconsistent with the Nexus routing context (e.g. First Agent or Assignee does not match the requesting Source PSP, or the agent named is not the party expected for this request).</td><td>Both</td></tr><tr><td>ExternalVerificationReason1Code</td><td>BNOR</td><td>AccountHoldingBankNotRegistered</td><td>The Destination PSP exists but is not onboarded with Nexus and cannot receive Nexus payments. Alternative payment rails may work. (Contrast to <code>RC04</code>: here the PSP is found but not participating.)</td><td>Both</td></tr><tr><td>ExternalVerificationReason1Code</td><td>RC03</td><td>InvalidDebtorBankIdentifier</td><td>The Source PSP identifier (BIC or ClearingSystemMemberId) in the request is invalid, unrecognised or missing.</td><td>Both</td></tr><tr><td>ExternalVerificationReason1Code</td><td>RC04</td><td>InvalidCreditorBankIdentifier</td><td>The Destination PSP identifier (BIC or ClearingSystemMemberId) is invalid, unrecognised or blank, so no PSP can be found. Applies where the Creditor Agent ID is mandatory for resolution.(Contrast to <code>BNOR</code>.)</td><td>Both</td></tr><tr><td>ExternalVerificationReason1Code</td><td>AC01</td><td>IncorrectAccountNumber</td><td>For account resolution: the account number does not match any account held by the Destination PSP. For proxy resolution: the proxy is not registered in the Destination Proxy Directory, or the account linked to it cannot be found.</td><td>Both</td></tr><tr><td>ExternalVerificationReason1Code</td><td>AG01</td><td>TransactionForbiddenOnThisAccount</td><td>The account was found but cannot receive a Nexus payment (closed, blocked, dormant, not open for inbound credits, or restricted by account type). </td><td>Both</td></tr><tr><td>ExternalVerificationReason1Code</td><td>PN01</td><td>AccountOwnerNameDoNotMatch</td><td>The account holder name supplied in the acmt.023 does not match the name held by the Destination PSP for that account. Used only where the Destination Country operates name-match confirmation of payee.</td><td>Account</td></tr><tr><td>ExternalVerificationReason1Code</td><td>PN02</td><td>AccountOwnerNameCloseMatch</td><td>The account holder name supplied is a close but not exact match to the name held by the Destination PSP. </td><td>Account</td></tr><tr><td>ExternalVerificationReason1Code</td><td>PI01</td><td>AccountOwnerIdentificationDoNotMatch</td><td>The account holder identification supplied does not match the identification held by the Destination PSP for that account.</td><td>Account</td></tr><tr><td>ExternalVerificationReason1Code</td><td>NORR</td><td>NoReportRecieved</td><td>The Destination PSP (or Proxy Directory) did not respond within the resolution timeout. The Source PSP may retry. The Destination IPSO returns this on behalf of the non-responding party.</td><td>Both</td></tr><tr><td>ExternalVerificationReason1Code</td><td>DS28</td><td>ReturnForTechnicalReason</td><td>A technical failure at the Destination IPS, Proxy Directory or Destination PSP prevented the request from being processed. The Source PSP may retry.</td><td>Both</td></tr><tr><td>ExternalVerificationReason1Code</td><td>NR01</td><td>NoReasonPossible</td><td>The Destination PSP declines to confirm the account and will not disclose why, typically for regulatory, fraud-prevention or privacy reasons (e.g. deceased holder, suspected abuse of the resolution service, sanctions hit). The Source PSP must not retry or infer a reason.</td><td>Both</td></tr></tbody></table>