trade.message.created
Before you receive events
- Register an endpoint, store its signing secret, and verify the receiver.
- Subscribe the endpoint to this event type.
- Verify the timestamp and signature against the raw request body before you parse or acknowledge it. See Webhooks.
Payload examples
Customer text
Customer image
Customer file
Merchant text
Merchant image
Merchant file
Your response
Return a 2xx response once you have durably stored the event. Deduplicate on the signed event ID: retries and manual replays keep the same ID.
Trade and message events share one sequence counter, so gaps are normal if you subscribe to only some event types. A message can arrive after a newer trade update, so do not treat arrival order as the complete history of a trade. List the trades to reconcile.
If an attachment is unavailable, the payload says so explicitly. Read the original attachment through the authenticated API.
These payloads are synthetic examples.