Skip to main content
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.
1

Open Customers and select Add customer

Go to Customers in the navigation and select Add customer.
2

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.
3

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.
You can also create a customer and request a verification link programmatically. See the API Reference for the customers and verification-link endpoints.

​
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: 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.
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.

​
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: 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.