cbk_*) is a challenge to a card payment you received. It is separate from disputes you file about other transactions.
List cases with GET /chargebacks. Read a case with GET /chargebacks/{chargebackId}. Both require chargebacks.read. The case links to its card payment, payment intent, and receiving customer.
Prepare a response
Natural supplies recorded payment, authentication, delivery-channel, and refund facts.evidenceGuidance explains the applicable response choices and missing information. Supply facts and documents that Natural does not already hold. Customer evidence supplements recorded facts.
- Read the case and its
version. - Upload a file through
POST /chargebacks/{chargebackId}/filesusing multipart form data. - Save evidence and associate uploaded file IDs through
PATCH /chargebacks/{chargebackId}. - Preview the PDF through
POST /chargebacks/{chargebackId}/preview. - Submit with
POST /chargebacks/{chargebackId}/submitusing the reviewed version.
chargebacks.respond to save evidence, upload files, submit, or accept a case. It includes chargebacks.read. PDF preview requires only chargebacks.read.
Accept a case
UsePOST /chargebacks/{chargebackId}/accept with the current version when you choose not to contest it. This is a separate action from submitting evidence.
Status
responseDueAt is the response deadline. submittedAt is null until submission. Accepted and expired cases do not imply a provider loss.
Retry and event behavior
Mutations require anIdempotency-Key. Repeating a completed operation with the same request returns the original response after current authorization is checked. A new operation with an old version is rejected.
Chargeback events contain the case resource without evidence or evidence guidance. chargeback.updated includes acceptance and expiry. chargeback.closed reports provider wins and losses.