P2P Crypto — disputes
When the parties do not agree, or a deadline expires mid-delivery, the order goes to disputed and CorpX decides. While the dispute is open, the amount stays held and no deadline runs.
Who opens and when
POST .../p2p/orders/{orderId}/disputes with reason (crypto_not_received, wrong_amount, release_not_done, other) and an optional description (up to 2,000 characters).
Outside these conditions: 409 dispute_not_allowed_yet. Order already in dispute: 409 dispute_already_open. The answer is 201 with the dispute, or 202 with status: opening if it is still being recorded.
Flow
- Messages:
POST .../disputes/messageswithbody(up to 2,000 characters). When CorpX requested information, the reply from the requested party moves the dispute back toopen. - Evidence:
POST .../disputes/evidence/upload-urlreturns an upload URL (PUT) for a PDF, JPEG, PNG or WebP of up to 5 MB. After the upload,POST .../disputes/evidenceregisters the file withkey,evidenceId,filename,contentTypeandsizeBytes. - The order’s price evidence (the Binance query that locked the price, at
GET .../p2p/orders/{orderId}/price-evidence) is already part of the analysis; it does not need to be attached. - Once decided, messages and evidence answer
409 dispute_already_decided.
A message with contact or off-platform payment details is flagged to CorpX.
Decision
The decided dispute carries decision, fault (buyer, seller or none) and the CorpX note. The fault counts toward reputation. On a refund to the buyer, the fee is not charged.
If the decision’s transfer fails, the order stays in disputed with lastError and CorpX retries from the desk, without a new decision.
Webhooks
p2p.dispute.updatedon each change (opened, information requested, reply, decided).p2p.order.updatedwhen the order entersdisputedand when it reachesresolved.