What to include
The more of this you send, the faster we can find the problem.Try this first
I get 401 on every request
I get 401 on every request
Check that the key is in the
x-api-key header, not Authorization: Bearer. Check that the key
belongs to the environment you are calling. See
Authentication.I get 403 when I create a payout
I get 403 when I create a payout
The key lacks the
payouts:write scope, or your business is not verified yet. See
Authentication.My payout is still processing
My payout is still processing
Fetch it with
GET /v1/payouts/{id} and read status and events. Do not send it again. If it
has not finished after the time you expect, send us its publicId.I am not receiving webhooks
I am not receiving webhooks
Look at the delivery under Settings → Webhooks, or call
GET /v1/webhooks/events. Check
that the endpoint is in the right environment, uses https, is publicly reachable and does not
redirect. See Delivery and retries.The webhook signature never matches
The webhook signature never matches
Sign the raw request body, not parsed JSON, and use the secret for that endpoint and
environment. See Verify signatures.
I think a payment was sent twice
I think a payment was sent twice
Stop sending. Collect both public ids and the idempotency keys you used, then email us. See
Idempotency.
I lost my API key or signing secret
I lost my API key or signing secret
Neither can be shown again. Revoke the key and create a new one. For a signing secret, add a new
webhook endpoint.
Report a security problem
If you believe a key has leaked, revoke it in the dashboard first, then email support@payvehq.com with the time you think it leaked.Useful links
Dashboard
Keys, webhooks, statements and the payment simulator.
Errors
Every error code and what to do about it.

