What Reap handles
You do not need to build any of the following.- Lookup of the card, the cardholder identity, and the currency, all derived from the transaction
- The review of the dispute and the filing with the card network
- The credit to the cardholder when the dispute reaches
REFUNDED, recorded on the disputed transaction as aDISPUTE_REFUNDevent CARD_DISPUTE_STATUS_UPDATEDon every status change through to resolution
What you build
- A clear reason choice in your UI, so you do not guess what the cardholder is telling you
- The call to
POST /disputeswith the transaction ID and the reason - A handler for
CARD_DISPUTE_STATUS_UPDATEDthat follows the dispute through to resolution - The credit on your own ledger from the
DISPUTE_REFUNDevent, only when you keep the cardholder balance yourself
How it works
- The cardholder tells you what went wrong with the charge
- You pick the matching reason and file the dispute
- Reap reviews the dispute, files it with the card network, and reports each status change
- The card network rules for the cardholder or for the merchant
Core resources
One resource and one webhook, plus a transaction event, carry the whole flow.- A dispute records one challenge against one cleared transaction.
POST /disputescreates it withstatusset toRECEIVED, andGET /disputes/:idreads it back. It carriesreason,category,amount,refundedAmount,cardholder, andresolvedAt.GET /disputesreturns your disputes and acceptscategoryas a filter CARD_DISPUTE_STATUS_UPDATEDreports every status change through to resolution- The
DISPUTE_REFUNDevent on the disputed transaction carries the credit and arrives inCARD_TRANSACTION_UPDATED
Use cases
Unrecognized charge
The cardholder did not authorize the charge. A counterfeit or stolen card was used in person, or the card details were used online, by phone, or by mail.
Charge taken without authorization
The merchant charged the card while it was blocked, after the authorization was declined, or without any authorization.
Wrong amount or duplicate charge
The charge was processed for the wrong amount, in the wrong currency, against the wrong card, or more than once.
Goods or services not received
The cardholder paid but never received the goods, received goods not as described, or was charged after canceling.
Disputes and fraud alerts
A dispute is not a fraud alert. Confirming a fraud alert blocks the card but does not recover the money. A dispute is the path for recovering the money. The two are independent. Neither requires the other, and you can file both against the same transaction.Next steps
File a Dispute
Check the requirements, file the dispute, and track it to resolution.
Dispute Reasons
Every reason by category, and how to pick the closest match.