Email support@payvehq.com.

What to include

The more of this you send, the faster we can find the problem.
Never send a secret. Do not put an API key, a webhook signing secret, a card number, a PIN or a one-time code in an email or a screenshot. We will never ask for them. If you have already sent a key, revoke it now.

Try this first

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.
The key lacks the payouts:write scope, or your business is not verified yet. See Authentication.
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.
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.
Sign the raw request body, not parsed JSON, and use the secret for that endpoint and environment. See Verify signatures.
Stop sending. Collect both public ids and the idempotency keys you used, then email us. See Idempotency.
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.

Dashboard

Keys, webhooks, statements and the payment simulator.

Errors

Every error code and what to do about it.