Skip to main content

When to Open a Dispute

If the counterparty (merchant) doesn’t fulfill their obligation, you have the right to open a dispute. Common scenarios include:
  • Merchant confirmed payment but you didn’t receive fiat
  • You sent payment but merchant won’t release stablecoins
  • Order stuck in a status with no progress from counterparty
Disputes must be opened within the allowed time window specified in the protocol. After this window expires, you may lose the ability to dispute the order.

Dispute Process

Follow these steps to open and manage a dispute:
1

Open a dispute

Open a dispute within the allowed time window using the dispute button in the app for the specific order.
2

Submit evidence

Submit evidence in-app to support your claim. The more detailed and clear your evidence, the better.Good evidence includes:
  • Payment receipts or transaction confirmations
  • Screenshots of order details and status
  • Communication records with the merchant
  • Bank statements or transaction history
  • Any other relevant documentation
3

Monitor dispute status

Monitor your dispute status in the app. You’ll be notified of any updates or requests for additional information.

How Disputes Are Resolved

Disputes are resolved on-chain by authorized admins under protocol fault rules. The resolution process:
  1. Admins review submitted evidence from both parties
  2. Decision is made based on protocol rules and evidence quality
  3. Resolution is executed on-chain automatically
  4. Both parties are notified of the outcome
Jury-based escalation tiers are planned for a future release, which will provide additional dispute resolution options.

Tips for Successful Disputes

Act Quickly

Open disputes as soon as you identify an issue, within the allowed time window.

Document Everything

Keep records of all transactions, communications, and actions taken.

Be Clear

Provide clear, factual descriptions of what happened and what went wrong.

Submit Evidence

Upload all relevant evidence that supports your claim.

Build docs developers (and LLMs) love