Triage failed payments
Paystack Subscription Recovery focuses on Paystack subscription recovery, billing failed payment webhooks, retry schedules, and dunning notifications. In AWRA, plans configuration and subscription billing controls regulate tenant feature access levels, billing cadences, and payment compliance.
The primary objective is transactional stability and feature lock enforcement. Admins must verify plans properties and limits rules before saving configurations.
In practice, an admin configures a Paystack retry queue, triggers failed billing notices, and audits recovery logs.
Recovery dunning path
Webhook
Receive failed charge event callback from Paystack gateway.
Alert
Send initial payment failure notice to billing contact.
Retry
Schedule automated card charge retry (e.g. after 3 days).
Suspend
Deactivate plan features if recovery fails after final retry.
Billing model
- Tenant plans define strict feature groups and limits.
- Subscription conversions require clear upgrade paths.
- Failed invoice collections trigger automatic dunning cycles.
- Always audit overrides permissions to prevent revenue leakage.