> 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-1-sender-inputs-proxy-or-account-details.md).

# Step 1: Sender inputs proxy or account details

{% hint style="info" %}
Note: The process below is shown with demonstration screens in [*Sending Payments > Steps 7-9 Addressing, Proxy and Confirmation of Payee*](/payment-setup/steps-7-9-addressing-proxy-resolution-and-confirmation-of-payee.md).
{% endhint %}

<figure><img src="/files/Mhsp44EWa4fLW5PdaMY6" alt=""><figcaption><p>Flow diagram for setup of the addressing form in the Source PSP's app</p></figcaption></figure>

1. When the Sender selects the Destination Country for a payment in their PSP’s app, the Source PSP will call the `GET /countries/{countrycode}/addressTypes` API operation, specifying the country code. Nexus will respond with a full list of address types for that country, including any proxy types, Account Identification formats and/or IBAN. (See [*Address Types*](/addressing-and-proxy-resolution/address-types-and-inputs/address-types.md) for details.)
2. The Source PSP will show the Sender a form allowing them to select one of the possible address types, according to the details they were given by the Recipient.
3. The Sender selects an address type (eg the “Mobile” option on the form; in the case of a payment to Singapore, this would select the address type with the ID “*SGMBNO”*).
4. The Source PSP will call the `GET /addressTypes/{addressTypeId}/inputs` API operation to retrieve the input fields that are required for this address type.

{% hint style="info" %}
The Source PSP could retrieve the address inputs for all address types in a single API call by using\
`GET /countries/{countryCode}/addressTypesAndInputs/`\
\
instead of\
\
`GET /countries/{countryCode}/addressTypes/`
{% endhint %}

5. The Source PSP’s app will use the address inputs to generate the app form to enter the address details
6. The Sender will enter the details that they were given by the Recipient (eg “+6580001234”).
7. The Source PSP’s app must validate that the address details entered by the Sender are in the correct format. These validation rules will be provided as regular expressions (regex) in the address inputs information provided by Nexus. This allows the PSP to validate the format of the data in-app, prior to any communication with Nexus or the proxy scheme.
8. If the Sender entered **proxy details**, the Source PSP will prepare an ISO 20022 [`acmt.023`](/messaging-and-translation/message-acmt.023-identification-verification-request.md) message, following the **usage guidelines for** **proxy resolution.** The Source PSP will send the `acmt.023` (or equivalent API request) to Nexus.
   1. **See** [**Step 2**](/addressing-and-proxy-resolution/proxy-and-account-resolution-process/step-2-proxy-resolution-messaging-sequence.md) for further steps on proxy resolution.
9. If the Sender entered account details, the Source PSP will prepare an **ISO 20022** [**acmt.023**](/messaging-and-translation/message-acmt.023-identification-verification-request.md) message, following the **usage guidelines for** **account resolution.** The Source PSP will send the `acmt.023` (or equivalent API request) to Nexus.
   1. **See** [**Step 3**](/addressing-and-proxy-resolution/proxy-and-account-resolution-process/step-3-account-resolution-messaging-sequence.md) for further steps on account resolution.


---

# 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-1-sender-inputs-proxy-or-account-details.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.