> 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/addressing-and-proxy-resolution/proxy-and-account-resolution-process/step-4-source-psp-processes-the-results.md).

# Step 4: Source PSP processes the results

The Source PSP will now receive an `acmt.024` response message from Nexus.

1. The Source PSP will check the `acmt.024` to see if the proxy or account resolution has been successful.
   * If the proxy or account resolution has **failed**, the Source PSP will display the reason to the Sender, based on the *Reason Code* provided. (For example: “*This proxy is not associated with any account.”*)
2. If the proxy resolution is **successful**, the Source PSP must:
   1. Check if the display name is provided in the `acmt.024` response message (in the `Account > Name` element):
      1. **If a display name is provide**, the Source PSP should the display name to the Sender and ask them to confirm that this is the name they’re expecting to see (see [Step 9 of the User Journey](/payment-setup/steps-7-9-addressing-proxy-resolution-and-confirmation-of-payee.md#toc116457922)).
      2. **If no display name is provided**, the app should show the Sender a warning to the effect of “We were unable to check the name of the account holder. Please double-check the account details are correct before sending the payment.” The Sender may proceed with the payment at their own discretion.

{% hint style="danger" %}
If no real name was provided in *`Party > Name`,* the Source PSP does not have sufficient information about the Recipient to complete the necessary compliance and sanctions screening checks.

In this case, the Source PSP **must** ask the Sender to provide this information. (This is the least preferred outcome as it relies on potentially inaccurate information from the Sender, rather than verified information from the Destination PSP or Proxy Directory.)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexusglobalpayments.org/addressing-and-proxy-resolution/proxy-and-account-resolution-process/step-4-source-psp-processes-the-results.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.