Developer guide
Follow the event. Reconcile the outcome.
Use financial events to keep your own system informed. Plan for verification, repeat delivery and reconciliation against the underlying operation.
Keep events tied to their source.
- Identify the operation
Associate each event with the stable object identifier in the API contract.
- Verify the delivery
Implement the authentication or signature-verification method specified for webhook delivery. No header names or signing algorithm are defined on this page.
- Handle repeated events
Use the documented event identifiers and replay semantics to prevent duplicate effects in your system.
Design for delayed or repeated delivery.
The production specification must define event types, ordering, acknowledgements, retries and replay. Do not assume delivery order or an exactly-once guarantee from this overview.
- Process the state
- Track instruction approval, transfer confirmation and payment reconciliation separately. Confirmation on a network does not establish receipt in a bank account.
- Recover deliberately
- Follow the documented retry and replay behavior after an interruption.
- Reconcile
- Check your records against the source operation when an event is missing, delayed or unexpected.