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

# Merchant onboarding

> Merchants are provisioned by SohoPay, registered on-chain, and then given a facilitator credential.

A merchant cannot self-serve an API key from the public app and skip verification. SohoPay creates the merchant account, and the on-chain registry must list that merchant as `ACTIVE` before `settleBatch` will pay them.

## What you need

1. A legal entity SohoPay can verify. Email `support@sohopay.ai` to start KYB. See [KYB](/compliance/kyb.md).
2. A payout address that will be stored in `SohoMerchantRegistry` on Base Sepolia for staging.
3. Either a merchant user (JWT) or an `sk_live_` API key bound to your merchant UUID. Staging keys use the `sk_live_` prefix.

Until those exist, facilitator calls that require `x402:settle:read` or `x402:settle:create` will not succeed for your account.

## After you are provisioned

* Confirm `GET /api/v1/facilitator/supported` shows `eip155:84532` and the staging USDC asset from [Environment setup](/environment-setup.md).
* Point your resource server at that network in the 402 challenge.
* Run one capture in staging and poll to `CONFIRMED` before you depend on the integration. See [Testing](/guides/testing.md).

> [!NOTE]
>
> Build and test on staging. Production hosts and payout addresses are issued when your merchant is cut over.

## Next steps

> [card] [Merchant integration](/guides/merchant-integration.md)
>
> Verify and capture.

> [card] [Allowlist and registry](/guides/allowlist-management.md)
>
> Registry states versus the agent's grant.
