# Recurring payments

> 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:

<table>
<thead>
  <tr>
    <th>
      Dimension
    </th>
    
    <th>
      <a href="/payments/recurring/charge-authorization">
        Charge authorization
      </a>
    </th>
    
    <th>
      <a href="/payments/recurring/subscriptions">
        Subscriptions
      </a>
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Control
    </td>
    
    <td>
      Your application decides exactly when to charge
    </td>
    
    <td>
      Paystack manages the billing schedule and lifecycle
    </td>
  </tr>
  
  <tr>
    <td>
      Retry logic
    </td>
    
    <td>
      You design and run your own retry rules
    </td>
    
    <td>
      Paystack manages the billing lifecycle and invoice events for you
    </td>
  </tr>
  
  <tr>
    <td>
      Customer portal
    </td>
    
    <td>
      You build your own customer management flow
    </td>
    
    <td>
      Includes a hosted management link for updating payment details or cancelling
    </td>
  </tr>
  
  <tr>
    <td>
      Supported channels
    </td>
    
    <td>
      Card across Paystack markets
    </td>
    
    <td>
      Card, plus Direct Debit in Nigeria
    </td>
  </tr>
  
  <tr>
    <td>
      Implementation effort
    </td>
    
    <td>
      Higher, because you own scheduling and recovery logic
    </td>
    
    <td>
      Lower, because the billing engine is built in
    </td>
  </tr>
  
  <tr>
    <td>
      Best for
    </td>
    
    <td>
      Custom billing dates, usage-based collections, or billing tied to your own workflow
    </td>
    
    <td>
      Standard memberships, plans, and software subscriptions
    </td>
  </tr>
</tbody>
</table>

With charge authorization, use [partial debits](/payments/recurring/charge-authorization/partial-debits) to recover part of the amount when the full amount can't be charged, or a [bulk charge](/payments/recurring/bulk-charge) to queue many authorization charges in one batch.

<overview-card-grid>
<overview-card description="Store the authorization from a first payment and charge it again when your schedule says to." path="/payments/recurring/charge-authorization" title="Charge authorization">



</overview-card>

<overview-card description="Queue and monitor many authorization charges in a single batch." path="/payments/recurring/bulk-charge" title="Bulk charge">



</overview-card>

<overview-card description="Create a plan, subscribe customers and let Paystack run the billing cycle." path="/payments/recurring/subscriptions" title="Subscriptions">



</overview-card>
</overview-card-grid>

<localized-block regions="ng">

To debit a customer's bank account on a recurring basis, set up a [Direct Debit](/payments/recurring/charge-authorization/direct-debit) mandate.

</localized-block>
