Notification Options
Anton Payments keeps you informed about important events on your account through two channels: email notifications and webhooks. This article explains how to configure your notification preferences so you receive the alerts that matter to you.
Email Notifications
Email notifications are sent to your registered email address when key events occur on your account. These are designed for human awareness and do not require any technical setup beyond choosing which events you want to be notified about.
Events You Can Subscribe To
The following event types are available for email notifications:
Payout Completed — Sent when a payout has been successfully delivered to the payee.
Payout Failed — Sent when a payout fails during processing. The email includes the reason for the failure so you can take corrective action.
Low Balance — Sent when your balance in any currency drops below a threshold you define. This helps you avoid payout failures due to insufficient funds.
RFI Received — Sent when a Request for Information (RFI) is issued on your account, typically related to compliance or onboarding. RFIs require your attention and response.
Configuring Email Notifications
To set up or change your email notification preferences:
Log in to the merchant portal at app.antonpayments.com.
Navigate to Settings > Notifications.
Toggle each event type on or off based on your preferences.
Save your changes.
Each team member can configure their own notification preferences independently. This means your finance team can subscribe to low balance alerts while your operations team subscribes to payout status updates.
Webhooks
Webhooks are HTTP callbacks that deliver event data to your server in real time. Unlike email notifications, webhooks are designed for automation: your system receives the event payload and can act on it programmatically.
Webhooks are configured separately under Settings > Webhooks in the merchant portal. You provide an endpoint URL, and Anton sends a POST request to that URL whenever a subscribed event occurs. The request body contains structured event data including the event type, timestamp, and the relevant resource (such as the payout object).
Webhooks vs. Email: When to Use Each
Both notification channels serve different purposes, and many merchants use both:
Use Case | Recommended Channel |
Keeping your team informed about payout status | |
Triggering automated workflows when a payout completes | Webhook |
Alerting finance when balances are low | |
Updating your internal database with payout status changes | Webhook |
Responding to compliance RFIs promptly | |
Reconciling payouts in your accounting system | Webhook |
Email notifications are best for awareness and manual follow-up. Webhooks are best for system-to-system integration where you want to automate a response to an event.
Reliability and Retries
Webhook deliveries include automatic retries if your endpoint returns an error or is temporarily unavailable. You can monitor webhook delivery status in the merchant portal under Settings > Webhooks to ensure your endpoint is receiving events successfully.
For more details on webhook payload formats and verification, see the API documentation at docs.antonpayments.com.