# Common problems

> Index by symptom of the most common integration problems, with the likely cause and the page that solves each one.

Página: https://doc.rapidchargeback.com/en/referencia/problemas-comuns/

Found your symptom? The likely cause is in one line, and the detail is on the linked page.

## Credentials and access

### Every call returns `401`

The `Authorization` header does not match: wrong credentials, credentials regenerated in the dashboard (the previous ones stop working immediately), or base64 built over something other than `client_id:client_secret`. See [Authentication](https://doc.rapidchargeback.com/en/referencia/autenticacao/).

### The API returns `403 COMPANY_BLOCKED`

The company is blocked at Rapid. Credential-based calls stop; webhooks keep arriving. See [Blocked companies](https://doc.rapidchargeback.com/en/canais/webhook/retries-e-logs/#blocked-companies).

### I get `429`

You went over the request limit. Wait the time in the `Retry-After` header and, for volume, use batch upload. See [Rate limit](https://doc.rapidchargeback.com/en/referencia/codigos-de-resposta/#rate-limit).

### I get `404 NOT_FOUND` on an endpoint that exists

The path differs: an extra trailing slash, missing `/api/v1` or a typo. See [Response codes](https://doc.rapidchargeback.com/en/referencia/codigos-de-resposta/).

## Webhook

### No webhook arrives

First check that the webhook is registered and active under **Settings › Webhook**: without that there is no delivery and nothing in the log. Then check the reason for each attempt in the dashboard's delivery log, under **Activity**, **Webhooks** tab: it starts with `[https]`, `[destino]`, `[redirecionamento]` or `[assinatura]` when the failure was not a response from your server. See [Retries and logs](https://doc.rapidchargeback.com/en/canais/webhook/retries-e-logs/#delivery-logs).

### The signature never matches

Almost always the body was parsed as JSON before validating: the signature covers the raw body, byte for byte. Other causes: a key that was already rotated, and a timestamp outside the window. Test it with the [signature checker](https://doc.rapidchargeback.com/en/canais/webhook/autenticacao/#signature-checker) and compare with the examples in [Webhook authentication](https://doc.rapidchargeback.com/en/canais/webhook/autenticacao/).

### The log shows a failure, but my server received it

Your server answered outside `2xx` or took longer than the time limit. See [What counts as success](https://doc.rapidchargeback.com/en/canais/webhook/retries-e-logs/#what-counts-as-success).

### The same alert arrived twice

It is a retry or a redelivery, with the same `alert_id`. See [Idempotency](https://doc.rapidchargeback.com/en/canais/webhook/boas-praticas/#idempotency).

## Alerts

### `422 ALERT_INVALID_STATUS` when responding to an alert

The deadline passed or the alert already has a final status. The message says which case it is. See [Transition not allowed](https://doc.rapidchargeback.com/en/callback/atualizar-status/#transition-not-allowed).

### I do not know the alert `id`, only the provider's

Search by `provider_alert_id`. See [Search by your own ID](https://doc.rapidchargeback.com/en/callback/consultar-alertas/#search-by-your-own-id-the-providers).

## Transactions

### `409 TRANSACTION_DUPLICATE`

You already have a transaction with the same `external_source` and `external_id`. See [Error codes](https://doc.rapidchargeback.com/en/canais/transactions/codigos-de-erro/).

### `409 TRANSACTION_IMMUTABLE`

The transaction was already used by a product and can no longer be changed or deleted. See [Immutability protection](https://doc.rapidchargeback.com/en/canais/transactions/visao-geral/#immutability-protection).

### `404 MERCHANT_NOT_FOUND`

The `merchant_id` is not one of your company's merchants. See [List merchants](https://doc.rapidchargeback.com/en/canais/merchants/listar-merchants/).

### I lost the transaction `id`

Find it by the identifier you sent. See [By your system's ID](https://doc.rapidchargeback.com/en/canais/transactions/consultar-transacao/#by-your-systems-id).

### `413 PAYLOAD_TOO_LARGE` in batch upload

The body went over the maximum size. Split it into smaller batches. See [Batch upload](https://doc.rapidchargeback.com/en/canais/transactions/envio-em-lote/).

### The response has `warnings`

The transaction was created, but fields that improve protection are missing. See [Warnings](https://doc.rapidchargeback.com/en/canais/transactions/criar-transacao/#warnings).

### A dispute arrived without the associated transaction

The transaction does not have the charge identifier in the gateway. See [Note on `transaction_id`](https://doc.rapidchargeback.com/en/canais/transactions/criar-transacao/#note-on-transaction_id).