P2P Crypto — crypto transfer and verification
The seller sends the crypto from their wallet to destinationAddress (the buyer’s wallet chosen on opening) and reports the transaction hash. CorpX checks it on the network and unlocks the next step.
Report the txid
POST .../p2p/orders/{orderId}/txids with { "txid": "..." }. Seller only, and only in signed or crypto_sent.
Up to two txids per order: a partial transfer can be completed by a second one.
What CorpX checks
A txid only becomes confirmed with the network confirmed and the screening approved; a rejected screening makes the txid invalid.
Each txid shows checkStatus (pending, partial, confirmed, invalid), onchainStatus, screeningStatus, confirmations and amount (the amount seen on the network). Each change triggers p2p.order.txid.checked.
Results
Release
POST .../p2p/orders/{orderId}/release with the transaction PIN. Buyer only, and only after the txid is reported (409 order_step_out_of_order before that).
- In
crypto_confirmed, release is the normal path. - In
crypto_sent, the buyer can release before the confirmations if they already checked the wallet themselves. Releasing is final. - On release, CorpX transfers the held amount to the seller (
p2p-{orderId}) and charges the fee to whoever pays it (fee-p2p-{orderId}). - If the transfer fails, the answer is
422 release_failedand the amount stays held. CorpX follows up and retries from the desk. - Without a release by
releaseDeadlineAt, the order goes to dispute (release_overdue).