Concepts
Disputes
What a business sees when a buyer disputes one of its payments, and who can act on it.
Visibility is not authority
Your business sees a dispute because the disputed payment is bound to one of your intents. Seeing it grants nothing. Responding, adding evidence, withdrawing, conceding, and resolving happen on the case page, authorized only by the payment’s own roles: the buyer, the recipient, and the arbiter.
- A merchant whose wallet is the recipient responds as the recipient, from that wallet, like any party.
- A marketplace or P2P platform that is neither buyer nor recipient follows the dispute but cannot act in it. The seller responds from their own wallet.
Stages
| Stage | Meaning |
|---|---|
awaiting_response | Opened; waiting for the recipient’s response. |
awaiting_review | The recipient responded; review has not started. |
under_review | The arbiter is reviewing the case. |
resolved | The payment settled: outcome is released or refunded. |
resolutionPath says how it ended: arbiter, sender_withdrew (released), or recipient_conceded (refunded). The arbiter can only release the full amount to the recipient or refund it in full to the buyer.
What you never receive
Statements, evidence, the dispute reason, and the arbiter’s notes are never shared with your business through the API, webhooks, or the dashboard.