> 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 — webhooks

P2P events go to the account involved, with the same envelope as the other webhooks (`id`, `type`, `occurredAt`, `tenantId`, `accountId`, `data`). Order and dispute events go out **one per party**, each with that party's view in `data` and in that party's tenant (`tenantId`): in an order between tenants, each tenant only gets the event for its own account. Subscribe to the types below with `POST /v1/webhooks/subscriptions`.

## Events

| Event                                              | When                                                                               | `data`                                                               |
| -------------------------------------------------- | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| `p2p.order.updated`                                | The order changed status or step.                                                  | The order as in `GET .../orders/{orderId}`, plus `event`.            |
| `p2p.order.signature.requested`                    | The party's copy was sent for signature.                                           | `orderId`, `role`, `status`, `signatureUrl`, `deadlineAt`.           |
| `p2p.order.txid.checked`                           | A txid changed state during verification.                                          | The order, plus `event: txid_checked`, `txid` and `checkStatus`.     |
| `p2p.dispute.updated`                              | The dispute opened, had information requested, got a reply or was decided.         | The dispute, plus `event` and `role`.                                |
| `p2p.wallet.screened`                              | The wallet finished screening.                                                     | The wallet (`walletId`, `network`, `address`, `screeningStatus`, …). |
| `p2p.advertiser.updated`                           | The advertiser request was decided, or the advertiser was suspended or reinstated. | `accountId`, `advertiserStatus`, `level`, `occurredAt`.              |
| `account.hold.created`                             | The buyer's amount was held on opening.                                            | The hold, with `reason: p2p_order`.                                  |
| `account.hold.released` / `account.hold.cancelled` | The order's hold was released or undone.                                           | The hold.                                                            |

## `event` in `p2p.order.updated`

| `event`                           | Meaning                                                                         |
| --------------------------------- | ------------------------------------------------------------------------------- |
| `funded`                          | Order opened, amount held.                                                      |
| `signing_started`                 | Contract generated; the buyer's signature starts.                               |
| `buyer_signed`, `seller_signed`   | One copy was signed.                                                            |
| `signed`                          | Both copies signed (or signing disabled). The seller's deadline starts.         |
| `crypto_sent`                     | The seller reported the txid.                                                   |
| `txid_invalid`                    | The txids do not match; the order went back to `signed`.                        |
| `crypto_confirmed`                | Amount confirmed on the network. The release deadline starts.                   |
| `dispute_opened`                  | The order went into dispute.                                                    |
| `released`                        | The buyer released; seller paid.                                                |
| `resolved`                        | The dispute was decided and executed.                                           |
| `cancelled`                       | The order was cancelled.                                                        |
| `release_failed`, `cancel_failed` | The transfer or the refund failed; CorpX retries. `lastError` carries the code. |

## `event` in `p2p.dispute.updated`

`opened`, `info_requested`, `reply` and `decided`.

## Example

```json
{
  "id": "p2p-order-evt-1842-buyer",
  "type": "p2p.order.updated",
  "occurredAt": "2026-11-01T14:03:12Z",
  "tenantId": "tenant-acme",
  "accountId": "acc_comprador",
  "data": {
    "event": "crypto_confirmed",
    "orderId": "ord_4235120236fa625f2a539d0c",
    "role": "buyer",
    "side": "buy",
    "status": "crypto_confirmed",
    "pair": "USDT_TRON",
    "amount": "1000.00",
    "cryptoAmount": "196.29",
    "fee": "5.00",
    "feePayer": "seller",
    "heldAmount": "1000.00",
    "counterparty": { "username": "ciclano", "reputation": { "tradesTotal": 42, "completionPercent": "97.62", "deliveryMedianSeconds": 540, "deliveryPercentile": 80 } },
    "deadlineAt": "2026-11-02T14:03:12Z",
    "releaseDeadlineAt": "2026-11-02T14:03:12Z"
  }
}
```

The `id` is stable per event and party: use it to discard repeats.

## Order transfers

Release generates internal transfers with a reserved identifier. The `transfer.internal.in`, `transfer.internal.out`, `fee.charged` and `fee.refunded` webhooks for these transfers arrive with the P2P presentation:

```json
{
  "type": "transfer.internal.in",
  "data": {
    "transactionId": "internal-…",
    "amount": 1000.00,
    "identifier": "p2p-ord_4235120236fa625f2a539d0c",
    "description": "VENDA P2P CRIPTO",
    "p2pOrderId": "ord_4235120236fa625f2a539d0c",
    "p2pKind": "payment",
    "source": { "name": "ORDEM P2P CRIPTO" },
    "destination": { "name": "…", "accountId": "acc_vendedor" }
  }
}
```

The counterparty never carries a document or account. Descriptions and `p2pKind` as in [Statement and balance](/baas/guias/p2p/extrato-e-saldo).