Chargebacks are not created via the API. They originate from an acquirer webhook. Through the
public API you can only retrieve cases and manage dispute documents. Status transitions
(won / lost) are decided by the acquirer and applied internally.
x-api-key header (see Authentication).
Chargeback statuses
| Status | Meaning | What you can do |
|---|---|---|
opened | Chargeback just created from the acquirer webhook. | Wait — the system moves it to under_review automatically. |
under_review | Under review. Window is open for submitting evidence. | Submit dispute documents (up to the deadlineAt deadline). |
submitted | Evidence sent to the acquirer; awaiting decision. | Monitor the case. |
won | Dispute won. | Case closed. |
lost | Dispute lost. | Case closed. |
Effect on the payment and wallet:
- When moving to
under_review, the associated payment enters a disputed state (in_protest) and the chargeback amount is debited from your wallet (reserve), along with the applicable chargeback fee. - If the chargeback is
won, the payment returns topaidand the reserved amount is reversed (credited back), including the fee. - If the chargeback is
lost, the payment moves tochargebackand a configurable penalty may be applied per company.
Endpoints
| Method | Route | Description |
|---|---|---|
| GET | /chargebacks | List chargebacks with pagination and filters. |
| GET | /chargebacks/{id} | Retrieve a chargeback by ID. |
| GET | /chargebacks/transaction/{transactionId} | List chargebacks for a transaction. |
| GET | /chargebacks/payment/{paymentId} | List chargebacks for a payment. |
| GET | /chargebacks/{id}/documents | List submitted dispute documents. |
| GET | /chargebacks/{id}/documents/{documentId}/download | Generate a signed URL to download a document. |
| POST | /chargebacks/{id}/documents | Submit a dispute document. |
List chargebacks
Filter by status. Accepts multiple comma-separated values (e.g.,
opened,under_review).
Valid values: opened, under_review, submitted, won, lost.Filter chargebacks by a specific transaction.
Filter chargebacks by a specific payment.
Free-text search.
Start of the date range, in ISO 8601 with timezone (e.g.,
2026-06-01T00:00:00-03:00). The
date field being filtered is defined by dateField.End of the date range, in ISO 8601 with timezone (e.g.,
2026-06-30T23:59:59-03:00).Date field used by the
startDate/endDate filter. Values: openedAt or deadlineAt.Sort field. Values:
openedAt, amount, status, deadlineAt.Sort direction. Values:
asc or desc.Page number (positive integer).
Items per page (positive integer, maximum
100).List of chargebacks on the current page.
Chargeback ID (prefix
cbk_).Associated transaction (prefix
txn_).Associated payment (prefix
pay_).Chargeback identifier at the acquirer. May be
null.Disputed amount in cents (e.g.,
14990 = $149.90).Currency of the amount. Default
BRL.Current status:
opened, under_review, submitted, won, or lost.Reason code provided by the acquirer. May be
null.Reason description. May be
null.Deadline for submitting evidence, in ISO 8601. May be
null. After this point, document
uploads are blocked.When the chargeback was opened, in ISO 8601. May be
null.When the case was resolved (won/lost), in ISO 8601.
null while still unresolved.Pagination metadata:
page, limit, total, and totalPages.Retrieve chargeback by ID
Chargeback ID (prefix
cbk_).404 if the chargeback does not exist or does not belong to your company. See Errors.
Chargebacks for a transaction
Transaction ID (prefix
txn_).Page number (positive integer).
Items per page (positive integer, maximum
100).Chargebacks for a payment
Payment ID (prefix
pay_).Page number (positive integer).
Items per page (positive integer, maximum
100).List chargeback documents
Chargeback ID (prefix
cbk_).List of documents.
Document ID (prefix
cbkd_).Document type:
invoice, delivery_proof, signed_contract, screenshot, or other.Detected MIME type:
application/pdf, image/jpeg, image/png, or image/webp.File size in bytes.
Description provided at upload time. May be
null.Identifier of who uploaded the document.
404 if the chargeback does not exist or does not belong to your company.
Download a document
Chargeback ID (prefix
cbk_).Document ID (prefix
cbkd_).Signed URL for direct file download. Valid for a limited time.
404 if the document does not exist or does not belong to your company.
Upload a document
201 and the created
document.
This endpoint is idempotent. Send the Idempotency-Key header with a unique value per
request to prevent duplicate uploads on retry. See Conventions.
Path parameters
Chargeback ID (prefix
cbk_).Request body
Document type. Values:
invoice, delivery_proof, signed_contract, screenshot, or other.File content encoded as base64. Accepts the data URI prefix (e.g.,
data:application/pdf;base64,...) or plain base64. Accepted types: PDF, JPEG, PNG, and
WebP (detected by binary content, not file extension). Maximum size: 10 MB.Optional description for the document. Maximum 500 characters. May be omitted or sent as
null.Status codes and errors
| Code | When it occurs |
|---|---|
201 | Document submitted successfully. |
400 | Invalid file: empty, exceeds 10 MB, or unsupported type (only PDF/JPEG/PNG/WebP). |
404 | Chargeback not found. |
409 | Upload not allowed in the current status (not under_review) or deadline has passed. |
Testing in the Sandbox
Since chargebacks only originate from acquirer webhooks, use the Sandbox simulator to trigger a case and then exercise retrieval and document uploads.Create a test payment
Generate an approved transaction/payment by following the Quickstart.
Simulate the chargeback
Use the Simulate events page to trigger a chargeback on the payment
you created. The case enters
under_review automatically.See also
Payments
Payment statuses, including the disputed state.
Wallets
Debits, reversals, and penalties generated by chargebacks.
Fees
Chargeback fee and penalty configuration.
Simulate events
Trigger chargebacks in the Sandbox environment.

