> This page is for Internet banking (beta).

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://en.docs.api.corpx.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://en.docs.api.corpx.com/_mcp/server.

# P2P Crypto — FAQ

## Does CorpX keep the crypto?

No. The crypto goes straight from the seller's wallet to the buyer's. CorpX only reads the network to check the transfer. What CorpX keeps is the buyer's BRL, held in their account until release.

## Why did the buyer's balance drop if nothing was paid yet?

Because opening holds the amount (and the fee, when the buyer pays). The money is still in the account, but outside `available`. It shows up in `heldAmount` on the balance and in `GET .../holds?status=held`, with the order in `source`.

## Who pays the fee?

Whoever published the ad. On a sell ad, the seller; on a buy ad, the buyer. The amount is the advertiser's level percentage over the order amount. See [Money and fee](/baas/guias/p2p/dinheiro-e-taxa).

## Can the counterparty be from another tenant?

Yes. There is one book for every tenant with the feature on, so the ad your account takes can belong to an account of another tenant. The rules and the protection are the same: the amount is held in the buyer's account, CorpX checks the network and pays the seller by internal transfer. The counterparty's tenant does not appear in any response.

## Why can't I see the counterparty's name?

Until the trade concludes, each party sees only the other's `username` and reputation. Name and masked document appear on the receipt (`GET .../receipt`), after conclusion. In the statement, the counterparty is always `ORDEM P2P CRIPTO`.

## The receipt answers 409. Why?

`order_not_concluded`: some step is missing. The order concludes when it was released (or the dispute was decided for the seller), both parties signed, the seller was paid and the fee was charged. A cancelled order, or one refunded to the buyer, never concludes.

## The seller sent the wrong amount. What now?

If crypto is missing, the txid stays `partial` and the seller can complete it with a second txid. If the destination or the token is wrong, the txid becomes `invalid`; within the deadline, the seller can report another one. Otherwise, the buyer opens a dispute with `wrong_amount` or `crypto_not_received`.

## The buyer disappeared after receiving the crypto.

If they do not release by `releaseDeadlineAt` (24 h after confirmation, by default), CorpX opens the dispute on its own (`release_overdue`). The seller can also open a dispute 24 h after confirmation.

## Release answered `release_failed`.

The transfer to the seller was refused at the banking provider and the amount stays held. CorpX follows these orders and retries the release; do not ask the buyer for a new one. When it succeeds, `p2p.order.updated` arrives with `released`.

## Can I cancel after signing?

No. After both signatures, the path is a dispute. Before signing their own copy, either party can cancel, and the fault is on whoever cancelled.

## My ad was paused on its own.

Check `pausedReason`: pair disabled, advertiser suspended, wallet removed, lack of balance (buy ad) or suspension by CorpX (`staff_suspended`). When CorpX suspended it, turning it back on answers `ad_suspended`; contact support.

## Can I use `p2p-` or `fee-` in my transfers' identifier?

No. These prefixes are reserved for P2P orders and fees, and the API refuses the identifier. That is how the statement and webhooks recognize an order leg without looking anything up.

## How long does an order take?

With active parties, a few minutes plus the network confirmation time: buyer signature (up to 15 min), seller signature and transfer (up to 15 min), confirmations (minutes, up to 60 min) and the release.

## Where does the price come from?

From the Binance spot price for the `{ASSET}BRL` pair, read live, with 4 decimal places. There is no other source, average or stored quote. The pair list and the ads show the spot of that request (cached up to 2 s); the order locks the spot captured at opening, with the same 4 decimal places, and the whole query is stored at `GET .../p2p/orders/{orderId}/price-evidence`. The order's BRL amount rounds to cents only at opening (truncated), and the fee rounds up. If Binance does not answer, opening refuses with `409 price_unavailable` and nothing is created.