Subscription Recurring Billing
Check our Reference Materials for more details about a payment connector.
Overview
First, let's get to know what a recurring billing process means.
Recurring billing is when a merchant automatically charges a subscriber for specified goods or services on a prearranged schedule. Recurring billing requires the merchant to get the subscriber's payment details permission one time upfront for recurring charges, then continues with scheduled charges until the subscriber withdraws permission.
Now let’s talk about the two steps in recurring billing:
- Payment authorisation
- Payment capture
There are some exceptions where payment capture is the only step. However, in most common payment gateways it is recommended to take both steps to increase recurring billing success percentage.
Authorisation is the first step of a recurring billing process. This is a chain of commands to be followed in order to successfully launch the first step:
- The merchant sends a request to their acquirer (payment gateway) — PayPal for example.
- The payment gateway then submits a request to the payment details issuer.
- The issuer reviews the subscriber's account and decides if enough funds exist to cover the cost of the sale.
- If they do, an authorization hold is made which reduces the customer's credit for the amount of the sale.
- Then an authorization code is sent back to the payment gateway which instantly responds to the merchant with a code for approval or error.
- If an error code is issued, the transaction is still incomplete.
Capture, on the other hand, refers to the process by which a transaction moves out of the pending state and the merchant gets their money.
Note
The merchant must send a request to capture the transaction amount within a certain number of days, to verify that they really want to process it before the funds are released.
Cleeng-Managed vs. Externally-Managed Recurring Billing
There are two approaches in creating a connector:
Recurring Billing in Cleeng-Managed Purchases - It's a recurring billing flow where Cleeng manages when an authorisation/ capture/ termination is made.
Recurring Billing in Externally-Managed Purchases - If the recurring billing flow is managed outside of Cleeng, it is gateway-specific on how to notify about successful/failed payment attempts or subscription status changes.
For your understanding, we have prescribed a step-by-step guide on both approaches. Choose your preferred one and continue with the setup.
| Approach 1: Connector based on Cleeng recurring | Approach 2: Connector based on external recurring |
|---|---|
| 1. Prerequisites :- Implement your front-end part - Meet your payment gateway’s requirements - Make sure you are ready to integrate with Cleeng | 1. Prerequisites :- Implement your front-end part - Meet your payment gateway’s requirements - Make sure you are ready to integrate with Cleeng |
| 2. Build a connector | 2. Build a connector |
| 3. Subscribe to Cleeng Webhooks | 3. Set up gateway event notifications |
| 4. Set up Dunning actions | 4. Make Subscription Initial Purchase |
| 5. Make Subscription Initial Purchase | 5. Make sure the connector is ready to handle:- Managing the Recurring Billing with external module- Termination |
| 6. Make sure the connector is ready to handle:- Managing the Recurring Billing with Cleeng- Termination |
Up Next
If you want to continue with Recurring Billing in Cleeng-Managed Purchases, go straight to the next step.
If you want to find out about the other option - go to Externally Managed Recurring Billing.
Updated 3 months ago