Skip to main content
Short answers to common questions, each with a link to the page that holds the full detail.
No. Only a CLEARED transaction can be disputed, because the money has already moved. PENDING and VOID transactions cannot be disputed, and neither can a standalone refund. File a Dispute lists every requirement.
The window runs from the day the transaction first cleared and is the same for every reason. File a Dispute states the number of days and the earlier date to aim for. Past the window, POST /disputes returns CARD_DISPUTE_FILING_WINDOW_EXPIRED.
Yes. Send amount to dispute part of the charge, up to the cleared cardholder amount net of refunds. A partly refunded transaction can still be disputed for the remainder. Omit amount to dispute the full cleared cardholder amount.
Only when the earlier dispute reached CANCELED or DECLINED, which means it never reached the card network. While a dispute is live, a second one returns CARD_DISPUTE_ALREADY_EXISTS.
No. Disputes and fraud alerts are independent. Neither requires the other, and you can file both against the same transaction. Disputes and fraud alerts explains what each one does.
No. Subscribe to CARD_DISPUTE_STATUS_UPDATED, which you receive on every status change through to resolution. A dispute can take weeks to resolve, so treat the webhook as the source of truth. GET /disputes/:id returns the current dispute whenever you need it.
Retry POST /disputes with the same Idempotency-Key. Reap replays the original response, so the timeout does not turn into an error on the retry. A retry without the key returns CARD_DISPUTE_ALREADY_EXISTS when the first request already succeeded.
DECLINED means Reap did not file the dispute, so it never reached the card network. LOST means it was filed and the card network ruled for the merchant. Lifecycle and Statuses covers every value.
The credit includes a proportional share of the FX markup and the ATM variable fee, but the per-withdrawal ATM fee stays charged, the same way a merchant refund leaves it charged. How a refund is calculated walks through an example.
From the DISPUTE_REFUND event on the transaction, the same way you apply a merchant REFUND. Do not also credit from the dispute webhook, or the refund is booked twice. How a refund is calculated covers the credit and the event.

Next steps

File a Dispute

Check the requirements, file the dispute, and track it to resolution.

Lifecycle and Statuses

Every status value and what to do about it.