Skip to navigation

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.

ErrorWhen
403 order_role_not_allowedThe caller is the buyer.
422 txid_invalid_formatThe format does not match the pair’s network.
409 order_step_out_of_orderThe order is not waiting for a txid.
422 txid_limit_reachedThe order already has two txids.
409 txid_already_usedThe txid was already used in another order.

Up to two txids per order: a partial transfer can be completed by a second one.

What CorpX checks

no yes not yet yes no yes yes rejected under review Reported txid Transaction risk screening Network read Destination = destinationAddress?Right token and network? invalid Amount ≥ cryptoAmount(adding up the txids)? partial Confirmations ≥ pair minimum? pending (waiting) Screening approved? confirmed

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

ResultWhat happens
Amount confirmedOrder crypto_confirmed; the release deadline starts (releaseDeadlineAt, 24 h by default).
All txids invalid, seller deadline still openOrder goes back to signed; the seller can report another txid.
All txids invalid, seller deadline expiredAutomatic dispute (crypto_not_received).
Network does not confirm in 60 minAutomatic dispute (onchain_unconfirmed).

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_failed and the amount stays held. CorpX follows up and retries from the desk.
  • Without a release by releaseDeadlineAt, the order goes to dispute (release_overdue).