Why use them
The buyer may close the page before returning. A confirmation can also happen after the initial API response. For this reason, your backend must confirm the result through the signed webhook.Delivery flow
1
Bob creates the event
A relevant change happens, such as the confirmation of a transaction.
2
Your endpoint receives the request
Bob sends the payload to the HTTPS URL configured in the project.
3
Your application validates the signature
Verify the authenticity of the message using the raw request body.
4
Your application processes the event
Update the order idempotently and respond with success.
Bob may retry a delivery. Use the transaction identifier to prevent the same event from releasing an order more than once.
Next steps
Configure webhooks
Events, payload versions, signature, and implementation examples.
Transactions
Understand the states that the events communicate.