1
Finish your sandbox integration
Before you ask for live access, make sure the sandbox integration does all of this:
- Sends an
Idempotency-Keyon every payout, pay-in and conversion, and reuses it on a retry. - Verifies the webhook signature and rejects a request that fails.
- Records each event
idand ignores one it has seen. - Handles a
failedpayout. Use the test account numbers to produce one.
2
Verify your business
In the dashboard, open Settings and complete the verification section. Payve reviews what you submit. Money endpoints refuse an unverified business with
403 kyc_tier_insufficient.The dashboard lets you switch to Live once your business is approved.3
Create live keys
Switch the dashboard to Live, then create a key under Settings → API keys. It starts with
sk_live_.Give the key only the scopes production needs.4
Add live webhook endpoints
Webhook endpoints belong to one environment. The endpoint you added in Sandbox does not receive live events.Still in Live, open Settings → Webhooks and add your production URL. It must be
https and publicly reachable. Copy the new signing secret. It is different from your sandbox secret and is also shown once.5
Switch your configuration
Set the live values in production:
6
Fund your wallet
Live wallets start empty. Fund the wallet you will pay out from before you send the first payout.
See Wallets.
7
Send one small real payout
Pay a small amount to an account you control. Confirm three things: the payout reaches
successful, the money arrives, and your server receives and verifies payout.successful.What changes in live
Pre-launch checklist
Keys and secrets
Keys and secrets
- Live key is in a secret manager, not in code or CI logs. - [ ] Live key has only the scopes production uses. - [ ] No key is present in any browser or mobile build. - [ ] Sandbox keys are not deployed to production. - [ ] You know who can revoke a key, and how.
Idempotency
Idempotency
- Every payout, bulk payout, pay-in and conversion sends an
Idempotency-Key. - [ ] The key is created once per operation and stored before the request is sent. - [ ] A retry after a timeout or a5xxreuses the stored key. - [ ] A409 idempotency_conflictwaits and retries with the same key. - [ ] A422 idempotency_key_reusedis treated as a bug, not retried.
Webhooks
Webhooks
- A live endpoint exists and uses the live signing secret. - [ ] The signature is checked
against the raw request body. - [ ] Events older than five minutes are rejected. - [ ] Each
event
idis stored and a repeat is ignored. - [ ] The handler answers2xxwithin a few seconds and does slow work afterwards. - [ ] Unknown event types are answered with2xxand ignored.
Money handling
Money handling
- Amounts are integers in minor units everywhere. No floats. - [ ] A name check runs before
the first payout to a new recipient. - [ ] Your code treats
pendingandprocessingas “not finished”, never as success. - [ ] Afailedpayout is shown to your user and is not retried blindly. - [ ] You reconcile daily against a statement.
Operations
Operations
- Errors are logged with
error.requestId. - [ ]429responses back off usingRetry-After. - [ ] Someone is alerted when webhook deliveries start failing. - [ ] Your team knows how to reach support.

