Supported Events
Subscribe only to the events your application needs. Each event includes structured data in the webhook payload.Payment Events
| Event name | When it fires | Typical uses |
|---|---|---|
payment.created | A new payment was created | Update order state, start fulfillment |
payment.updated | A payment’s status changed (pending, failed, authorized, settling, settled, declined, cancelled, refunded) | Sync status, notify customers, adjust inventory |
refund.created | A refund process started | Trigger return workflows, update AR |
refund.updated | A refund’s status changed (processor-specific statuses) | Close tickets, update financial records |
Payment events fire immediately when the status changes. Use them to keep PayNext and your order management system synchronized in real time.
Subscription Events
| Event name | When it fires | Typical uses |
|---|---|---|
subscription.created | A subscription was started | Provision access, begin billing |
subscription.updated | A subscription was modified (plan, billing cycle) | Adjust access, prorated billing |
subscription.cancelled | A subscription ended or was cancelled | Revoke access, close billing cycle |
Saved payment flows trigger
subscription.updated events when plans change with immediate payment or when a past_due subscription recovers.