Receive event notifications from Better Sales Pro and payment providers.
// Example receiver (your server) // 1) Read raw body // 2) Verify source / signature if provided by the producer // 3) Return HTTP 200 quickly // 4) Process asynchronously
Overview
Webhooks let external systems react when something changes. Better Sales Pro currently uses webhook-style receivers primarily for payment gateways and mail providers, and the product surface advertises automation / e-sign completion events.
What exists today
- Stripe / Mollie / 2Checkout style payment webhooks
- Mail provider status webhooks (for example Lob handlers)
- In-product automation hooks that can notify external systems
Gateway webhooks
Payment gateways post to dedicated controllers (for example Stripe webhook endpoints). Configure the gateway dashboard with your Better Sales Pro webhook URL and secret.
E-Sign events
E-Sign product flows support completion notifications and automations. When designing integrations, treat event names as product events (for example completion / sent / viewed) and map them in your receiver—do not assume a universal public event catalog until published in the changelog.
Security
- Validate webhook secrets / signatures when the provider supplies them
- Reject unexpected sources
- Never log full payment credentials
Retries
Retry behavior depends on the producing system (Stripe, Mollie, etc.). Return 2xx quickly and process asynchronously.
Event explorer UI is architected for future catalog growth. Until a first-party webhook event registry is published, use provider docs + the Better Sales Pro changelog.
Was this page helpful?