Verified BursaPay gateway workflow: Explains the subscription API and its relationship to repeat charges and webhooks.
1. Overview & Purpose
The gateway provides subscription resources and uses recurring charge authorization under the hood.
2. Requirements & Setup
A customer authorization suitable for recurring charges and the required API permissions are needed.
3. Step-by-Step Workflow
- Create the subscription plan/configuration.
- Associate the customer authorization where required.
- Monitor subscription.created and subscription.charged events.
- Handle charge failures and cancellation states.
4. Rules & Troubleshooting
The webhook catalog includes subscription.created, subscription.charged, subscription.charge_failed and subscription.cancelled.
5. Verification & Next Steps
Treat failed recurring charges as application events that need customer-facing handling.