Skip to main content
Sandbox is open to everyone; production is not. Real money movement unlocks only when your Business’s verification (KYB) is approved, and the road there has one step that is yours, one that is Cleff’s, and a final switch that is just configuration.
1

Complete your business profile

In the dashboard, fill in your company’s verification dossier under Settings → Company: legal entity details, registration, and representative information. Do it early. A completed profile is also what provisions your sandbox wallet with test money, so it unblocks sandbox payout testing long before you want production.When the profile is complete, submit it. Your data is held encrypted by Cleff and is not shared with any payment provider at this stage.
2

Cleff reviews, prices, and verifies

A submitted profile moves to review. Cleff confirms your commercial terms with you and runs provider verification. Your dashboard shows the verification status throughout; you will be notified when it reaches approved, the single gate that unlocks production.
3

Switch your integration to production

Going live is a credential swap plus real funding:
  1. Mint a production API key in Settings → API keys. Production keys carry the ck_production_ prefix and see only production data; your sandbox beneficiaries and payouts do not carry over.
  2. Fund your account. There is no top-up endpoint in production; your Cleff Account is funded through the real funding path shown under Accounts in the dashboard.
  3. Re-create your production configuration: register your webhook endpoint with the production key (each environment has its own endpoint and signing secret), and onboard your real beneficiaries.
  4. Send a first small payout and watch it through the lifecycle before opening the volume.

​
Production checklist

  • Verification approved; commercial terms agreed.
  • Production API key minted and stored in your secret manager. The plaintext is shown once, and rotation revokes the old key immediately.
  • Cleff Account funded, with positive headroom for your first payout run; a shortfall surfaces at dispatch, not at creation.
  • Webhook endpoint registered with the production key; signature verification tested against the production signing secret.
  • Beneficiaries onboarded and compliant, each with a payout_usable bank account.
  • Your error handling covers the documented error codes; they are written so the resolving action is always stated.