---
title: Chargeback
description: REST API reference for reporting a chargeback and checking its status in Card Not Present Verification.
canonical: https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/apis/api-reference/chargeback
locale: en
generated_by: markdown-export
---

- [/](/)
- Regional Solutions
- [Card Not Present Verification](/developers/regional-solutions/card-not-present-verification)
- [Integration](/developers/regional-solutions/card-not-present-verification/integration/overview)
- [APIs](/developers/regional-solutions/card-not-present-verification/integration/apis)
- [API Reference](/developers/regional-solutions/card-not-present-verification/integration/apis/api-reference)
- Chargeback

**On this page# Chargeback

### Before you begin​

Your API requests are authenticated using an access token. Any request that does not include a valid access token will return an error. Learn more in [Authentication](/developers/regional-solutions/card-not-present-verification/integration/authentication).
Base URL
**UAT**: `https://transactions.transactional.uat.unico.app/api/public/v1`
**Production**: `https://transactions.transactional.unico.app/api/public/v1`

### Report a chargeback​

`POST /credit/transactions/{transaction_id}/chargeback` — reports to Unico that a chargeback was received for a specified transaction.
Reporting is not a contestationThis endpoint only reports the chargeback. It does not open a chargeback analysis and does not trigger the [liability guarantee](/developers/regional-solutions/card-not-present-verification/about-idpay/chargeback). To have Unico analyze the chargeback, open a contestation for the transaction in the portal.
Headers
HeaderValue`Authorization``Bearer {token}` — a valid access token.
Body
```
{  "datetime": "2023-01-05T03:00:00.000Z",  "requestor": { "key": "cpf", "value": "USER_CPF" },  "name": "USER_NAME",  "reason": "REQUEST_REASON",  "observation": "GENERAL_OBSERVATIONS"}
```

FieldTypeRequiredDescription`datetime`stringyesDate and time the chargeback was received, ISO 8601 format.`requestor`objectyesRequestor's information.`requestor.key`stringyesIdentification key type for the requestor (e.g. `cpf`).`requestor.value`stringyesIdentification key value for the requestor.`name`stringyesName of the requestor.`reason`stringyesReason for the chargeback.`observation`stringnoGeneral observations about the chargeback.
201 Created
```
{  "id": "8263a268-5388-492a-bca2-28e1ff4a69f0"}
```

FieldDescription`id`Chargeback ID.
A transaction has a single chargeback. Reporting a transaction that already has one returns `200 OK` with the `id` of the existing chargeback, and does not change it.
For error responses, see [Errors — Transaction Creation](/developers/regional-solutions/card-not-present-verification/integration/apis/errors#transaction-creation).
### Get chargeback status​

`GET /credit/transactions/{transaction_id}/chargeback/{chargeback_id}` — checks the status of a specific chargeback.
Headers
HeaderValue`Authorization``Bearer {token}` — a valid access token.
200 OK
```
{  "id": "8263a268-5388-492a-bca2-28e1ff4a69f0",  "status": "waiting"}
```

FieldDescription`id`Chargeback ID.`status`Current status of the chargeback.
A reported chargeback stays `waiting`. If the transaction is contested in the portal, the same `id` shows the progress and the result of the analysis. See [Enumerated — Chargeback result](/developers/regional-solutions/card-not-present-verification/integration/apis/enumerated#chargeback-result) for all possible statuses. To optimize performance, implement the [Webhook](/developers/regional-solutions/card-not-present-verification/integration/webhook) instead of polling this endpoint.Last updated on Oct 23, 2026**