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 in p2p.order.updated
event in p2p.dispute.updated
opened, info_requested, reply and decided.
Example
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:
The counterparty never carries a document or account. Descriptions and p2pKind as in Statement and balance.