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, the Verification card asks how you want to verify the customer. With Start a fresh identity verification selected (the default), select Start verification to produce a hosted verification link — it appears in the card as Open hosted verification, ready 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. Start a verification as normal; the issued link is simulated, and a Simulate approval control appears so you can drive an approved outcome and see entitlements granted. This control never appears in production.

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

​
Developer fee

A customer’s Overview tab has a Developer fee card. By default the customer is charged your global developer fee, and the card shows that fee. To charge this one customer something different:
  • Custom fee. Enter a flat AUD amount and/or basis points and select Save customer fee. It replaces your global fee for this customer; it never adds to it.
  • Waive. Leave both fields blank and save. This customer is charged no developer fee.
  • Use global fee. Removes the override, so the customer goes back to your global fee.
Changes apply to conversions made after you save; a conversion already priced keeps its fee. The same caps as the global fee apply, and saving or removing asks for your second factor. Roles without write access see the card read-only. Developers → Fees lists every customer with an override. The same actions are available through the API: GET, PUT and DELETE /v1/customers/{id}/developer-fees, and GET /v1/developer-fees/customers for the list.