Direction matters
| Flow | Current use | External availability |
|---|---|---|
| Paystack → BookedNG | Payment and refund status callbacks validated with Paystack signatures | Payment-provider infrastructure only |
| Resend → BookedNG | Inbound email events validated with provider signatures | Email-provider infrastructure only |
| Approved form automation → BookedNG | A campaign-specific signed complimentary-ticket submission | Restricted bespoke integration, not a general partner endpoint |
| BookedNG → partner website | Generic booking/order/ticket webhooks | Unavailable |
Do not configure a website’s callback URL as a BookedNG webhook destination. BookedNG does not currently send general outbound partner webhooks.
Payment ownership and retries
BookedNG payment callbacks are routed to the relevant booking or subscription handler. Positively identified external merchant Payment Page transactions are retained for audit but do not create BookedNG orders, tickets, refunds or payouts. A transaction reference alone is not proof that a payment is external. Unexplained BookedNG payment references remain available for investigation.
Supported synchronisation
- Appointment providers can connect Google Calendar from their protected dashboard. This synchronises eligible confirmed bookings to the connected provider calendar.
- Organisers and providers can download protected CSV reports where the dashboard offers an export.
- External marketing sites should link to BookedNG and treat the listing page as the live source for availability and checkout.
What to use instead
For a WordPress or custom event site, publish editorial details and a normal BookedNG button. For operational reconciliation, use the BookedNG dashboard and authorised CSV exports. If a workflow genuinely requires near-real-time notifications, submit a reviewed integration request through support; do not poll undocumented routes.
Future outbound webhook requirements
Before BookedNG can offer partner webhooks, the product needs subscription management, tenant-scoped events, signed deliveries, secret rotation, replay protection, retry and dead-letter handling, delivery logs, personal-data minimisation, test events, versioned schemas and operational support. See the implementation proposal referenced in the release audit.