Help with Events and webhooks
This page focuses on the guide you were reading. Work through the relevant checks below, then send us a question if the issue is still unresolved.
Missing access may be expected. Check its rollout status before treating the absence of a control as a technical fault.
Start with your events and webhooks setup
These are checks drawn from this feature's own instructions.
- Use test accounts and fictional client records.
- Keep sandbox and production credentials separated.
- Do not assume event order without a documented contract.
- Handle duplicates and retries safely.
- Verify final payment state with the processor when needed.
Common problems in Developer resources
Choose the problem closest to what you are seeing. Each one includes practical checks and a safe next step.
An expected endpoint or webhook is not available
- Check whether the document describes a conceptual API rather than a published contract.
- Verify the exact supported integration and test environment.
- Do not use internal or undocumented endpoints in a production dependency.
An integration behaves differently on retry
- Check request authentication and signature verification.
- Handle repeated and out-of-order events idempotently.
- Compare a sandbox event with the processor's authoritative state.
Still not resolved?
When you contact support, tell us what you expected, what happened instead, the non-sensitive error text (if any), and roughly when it occurred. The form will automatically include Events and webhooks as the topic.
Please do not include passwords, security codes, payment card details, client health records, or any other sensitive information.