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

# Get help

> How to reach Payve, and what to send so we can help quickly.

Email **[support@payvehq.com](mailto:support@payvehq.com)**.

## What to include

The more of this you send, the faster we can find the problem.

| Send | Where to find it |
| - | - |
| The transaction's public id | `publicId`, such as `pyt_9c2e41b7a05d3f68` |
| The request id | `error.requestId` in the error response |
| The environment | Sandbox or live |
| The endpoint and HTTP status | For example `POST /v1/payouts`, `422` |
| The error code and message | `error.code` and `error.message` |
| The time it happened, with time zone | Your logs |
| Your `Idempotency-Key` | Your logs |
| For webhooks, the event id | `id` in the event, such as `evt_5d0a...` |

> [!WARNING]
>
> **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](/get-started/api-keys.md#revoke-a-key) now.

## Try this first

> [accordion] 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](/get-started/authentication.md#401-responses).

> [accordion] I get 403 when I create a payout
>
> The key lacks the `payouts:write` scope, or your business is not verified yet. See
> [Authentication](/get-started/authentication.md#403-responses).

> [accordion] 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`.

> [accordion] 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](/webhooks/delivery-and-retries.md).

> [accordion] 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](/webhooks/verify-signatures.md#common-mistakes).

> [accordion] I think a payment was sent twice
>
> Stop sending. Collect both public ids and the idempotency keys you used, then email us. See
> [Idempotency](/essentials/idempotency.md).

> [accordion] 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](mailto:support@payvehq.com) with the time you think it leaked.

## Useful links

> [card] [Dashboard](https://app.payvehq.com)
>
> Keys, webhooks, statements and the payment simulator.

> [card] [Errors](/essentials/errors.md)
>
> Every error code and what to do about it.
