> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rails.wayex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Onboarding customers

> Add end customers by email, track verification, and unlock entitlements on approval.

A **customer** is an end user you onboard and act for. Before a customer can transact, they complete
identity verification. When verification is approved, the customer is granted **entitlements** — the
specific things they are allowed to do.

## Add a customer by email

Onboarding is **email-only**. You enter just the customer's email address; the customer completes their
own identity verification, so you do not need to collect their personal or business details up front.

<Steps>
  <Step title="Open Customers and select Add customer">
    Go to **Customers** in the navigation and select **Add customer**.
  </Step>

  <Step title="Enter the customer's email">
    Enter the email address where the verification link should go. You can optionally add a **name** as a
    label for your own records — it is not required.
  </Step>

  <Step title="Add & get verification link">
    Select **Add & get verification link**. The customer is created and you are taken to their detail page,
    where you can generate the link to send them.
  </Step>
</Steps>

<Note>
  You can also create a customer and request a verification link programmatically. See the
  **API Reference** for the customers and verification-link endpoints.
</Note>

## Verification

On the customer's detail page, select **Get verification link** to produce a hosted verification page to
send to the customer. The customer opens it and completes the identity checks themselves.

### What the verification states mean

Each customer shows a verification status. It moves through these states:

| Status              | What it means                                                                    |
| ------------------- | -------------------------------------------------------------------------------- |
| **In progress**     | Verification has started and is being assessed. No entitlements yet.             |
| **Requires action** | The customer needs to provide or correct something before assessment can finish. |
| **Approved**        | Identity checks passed. Entitlements are granted and the customer can transact.  |
| **Rejected**        | Verification did not pass. The customer cannot transact.                         |

The console reflects the current status as the API reports it. Customers awaiting verification, or whose
verification needs action or was rejected, surface in **Needs your attention** on the Home dashboard.

<Note>
  In the sandbox, identity verification is simulated — there is no external vendor page to complete. The
  customer detail page includes a **Simulate approval** control so you can drive an approved outcome and see
  entitlements granted. This control exists only in the sandbox.
</Note>

## Entitlements

Entitlements are listed on the customer's detail page. They are granted **only on an approved verification**
— nothing is unlocked before then. The entitlements you will see include:

| Entitlement     | Unlocks                                                               |
| --------------- | --------------------------------------------------------------------- |
| `payment_route` | Creating [payment routes](/console/payment-routes) for this customer. |
| `aud_onramp`    | On-ramp transfers — AUD in, stablecoin out.                           |
| `aud_offramp`   | Off-ramp transfers — stablecoin in, AUD out.                          |

Until a customer is approved and holds the relevant entitlement, the matching actions are blocked. For
example, you cannot create a payment route for an unverified customer — the console disables the action and
tells you verification is required first.