Plan, test, and monitor webhooks
Webhooks notify an external system when important AtomicPay events happen. Use them for automations, CRM updates, access provisioning, support workflows, or internal reporting.
Webhook workflow areas
| Area | Purpose |
|---|---|
| Events | Defines which AtomicPay actions should trigger a webhook. |
| Endpoint URL | The external URL that receives webhook requests. |
| Simulator | Sends test events before production traffic. |
| Logs | Shows delivery attempts and failures. |
| Security | Protects your endpoint from unwanted or untrusted requests. |
Common events
| Event type | Use it for |
|---|---|
| Purchase approved or completed | Create access, update CRM, or notify fulfillment. |
| Purchase declined | Trigger recovery or support follow-up. |
| PIX generated | Track pending PIX payment flows. |
| Cart abandoned | Trigger reminder automation when supported. |
| Trial started | Start onboarding for trial users. |
| Subscription canceled or renewed | Update access and lifecycle systems. |
| Refund or chargeback | Update finance, access, or risk workflows. |
Create and test a webhook
- Decide what external system should receive events.
[Screenshot: Workflow diagram — CRM, access, or notification target identified.]
- Choose the events needed for the workflow.
[Screenshot: Event checklist — purchase approved, subscription, refund, etc. selected.]
- Create the endpoint in your external system.
[Screenshot: External endpoint URL — server route or catch URL ready.]
- Add the webhook URL in AtomicPay.
[Screenshot: Webhooks page — create webhook with endpoint URL.]
- Save the webhook.
[Screenshot: Webhook saved — status active with selected events.]
- Use the simulator to send test events.
[Screenshot: Webhook simulator — test event sent successfully.]
- Review logs for status, attempts, and response behavior.
[Screenshot: Webhook logs — delivery status and response codes visible.]
- Fix failed deliveries before relying on the automation.
[Screenshot: Failed delivery fixed — retry succeeds in logs.]
Best practices
- Start with only the events your system needs.
- Make your endpoint idempotent so repeated events do not duplicate work.
- Log received events on your side.
- Design retry and failure handling before launch.
- Keep payload and authentication details in the API documentation workflow.
FAQ
Where are webhook payload details documented?
Use AtomicPay API Docs for endpoint, authentication, and payload reference. This help center focuses on seller workflow.
What should I do if a webhook is not firing?
Check the selected events, product or business context, endpoint URL, webhook status, simulator result, logs, and whether the triggering sale or subscription event actually happened.
Can I connect webhooks to Zapier or Make?
Yes, when those tools provide a webhook URL. Test the event and confirm the automation handles retries or failures safely.