> This page is for BaaS.

> 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 — getting started

Before the first order, the account needs a public profile and at least one approved wallet on the pair's network. Every route on this page lives under `/v1/accounts/{accountId}/p2p`.

## 1. Profile

`PUT .../p2p/profile` with `{"username": "..."}`. The `username` is the public name in the market: lowercase, unique across the whole market (every tenant). Already taken: `409 username_taken`. `GET .../p2p/profile` returns the profile with the advertiser status and the reputation.

Any account's public profile is at `GET /v1/p2p/profiles/{username}`: reputation, completion rate and median delivery time. The numbers only show up after a minimum number of orders, set by CorpX.

## 2. Wallets

`POST .../p2p/wallets` with `network` (`tron`, `ethereum` or `polygon`), `address` and an optional `label` (up to 40 characters). The address is validated against the network's format. The same wallet cannot be added twice to the account (`409 wallet_already_registered`).

Every wallet goes through Elliptic risk screening:

```mermaid
flowchart TD
    A["POST .../p2p/wallets"] --> B{"Screening answers<br />within a few seconds?"}
    B -- "yes" --> C["<b>201</b><br />screeningStatus: approved or rejected"]
    B -- "no" --> D["<b>202</b><br />screeningStatus: pending"]
    D --> E["Screening continues"]
    E --> F["Webhook <code>p2p.wallet.screened</code><br />approved or rejected"]
```

```mermaid
stateDiagram-v2
    [*] --> pending: registration
    pending --> approved: screening approved
    pending --> rejected: high risk
    approved --> removed: DELETE (no open order)
    rejected --> removed: DELETE
    removed --> [*]
```

* Only an `approved` wallet trades. A `rejected` wallet never goes back to `approved`: register another one.
* **Default wallet.** `POST .../wallets/{walletId}/default` changes the default (`approved` only). The change takes effect after a grace period set by CorpX; until then, `defaultEffectiveAt` shows when it applies. The grace period protects the buyer against a wallet swap by someone who took over the account.
* **Remove.** `DELETE .../wallets/{walletId}`. Wallet in an ongoing order: `409 wallet_in_open_order`. Any ad that used the wallet is paused.
* When each order opens, CorpX screens both wallets again. A wallet that became risky refuses the order, and `details.walletOf` says whose it is.

## 3. Market

* `GET /v1/p2p/pairs`: the pairs enabled in the market (asset, network, token contract, decimals and required confirmations).
* `GET /v1/p2p/settings`: the market parameters that apply to the tenant: signing, delivery and release deadlines, new-wallet grace, per-order and daily caps, advertiser fee range and the pairs. Handy for a "how it works" screen before the first order.
* `GET /v1/p2p/ads?pair=&side=`: the book of active ads, with price, limits and the advertiser's public profile.

## Ready to trade

* [ ] The `p2p_crypto` feature is enabled in the tenant (otherwise, `403 feature_disabled`).
* [ ] The credential has `p2p.read` and `p2p.trade` (and `p2p.wallets` to register a wallet).
* [ ] The profile has a `username`.
* [ ] There is an `approved` wallet on the pair's network, and it is the default (or the `walletId` goes in the opening request).
* [ ] The account has available balance for the amount (buyer) and is not blocked.
* [ ] The customer has a transaction PIN set up (buying from a sell ad and releasing ask for the PIN; selling does not).
* [ ] The app subscribes to the P2P webhooks, or polls the order (see [Webhooks](/baas/guias/p2p/webhooks)).

Next step: [Ads](/baas/guias/p2p/anuncios) if you are going to advertise, or [Orders](/baas/guias/p2p/ordens) to take an ad.