Payments
Recurring payments
In a nutshell
Charge customers again after their first payment, either on your own schedule or through Paystack-managed subscriptions.
Recurring payments let you charge a customer again without asking them to pay from scratch. When a customer pays with a reusable channel such as a card, the successful transaction returns an authorization with reusable: true. You can charge it again later, or Paystack can charge it for you on a subscription plan. Mobile money authorizations aren't reusable.
Choose the approach that matches how much billing logic you want to own:
| Dimension | Charge authorization | Subscriptions |
|---|---|---|
| Control | Your application decides exactly when to charge | Paystack manages the billing schedule and lifecycle |
| Retry logic | You design and run your own retry rules | Paystack manages the billing lifecycle and invoice events for you |
| Customer portal | You build your own customer management flow | Includes a hosted management link for updating payment details or cancelling |
| Supported channels | Card across Paystack markets | Card, plus Direct Debit in Nigeria |
| Implementation effort | Higher, because you own scheduling and recovery logic | Lower, because the billing engine is built in |
| Best for | Custom billing dates, usage-based collections, or billing tied to your own workflow | Standard memberships, plans, and software subscriptions |
With charge authorization, use partial debits to recover part of the amount when the full amount can't be charged, or a bulk charge to queue many authorization charges in one batch.
To debit a customer's bank account on a recurring basis, set up a Direct Debit mandate.