Recurring Module

The Recurring Module is a low-code alternative to managing Credential on File and building your own subscription billing logic.

Instead of designing and maintaining CIT/MIT workflows, retry handling, and billing schedulers, you can use the Recurring Module to configure automated, repeat charges.

Every recurring billing configuration consists of two core objects that allow you to define billing rules once and apply them to multiple customers.

A Plan

A plan defines the billing terms. It controls:

Charge amount
Billing frequency
Billing interval
The billing start date

You create a plan once and assign multiple customers to it.

A Subscription

A subscription connects a customer's payment method to a plan. It defines:

The customer being billed
The payment details
The associated plan

Once a subscription is active, the gateway automatically processes transactions according to the plan schedule.

Use the Recurring Module when:

You need predictable, scheduled billing such as memberships or subscriptions
You want to avoid building custom recurring billing infrastructure
You prefer a gateway-managed solution rather than maintaining your own Credential on File logic

The Recurring Module provides a streamlined path to launch with minimal development overhead.

If you require full control over billing orchestration within your platform, you can store payment credentials and trigger transactions directly via the API. For greater flexibility, refer to the Credential on File guide.

⚠️
The Recurring Module is available only in regions that are not subject to PSD2 regulations. For customers in the EU and other PSD2-mandated regions, please refer to the Credential on File guide.

Setup Flow

To create a recurring billing relationship:

Create a plan with the desired billing configuration.
Create a subscription for the customer and associate it with the plan.

After setup, the Recurring Module handles the ongoing transaction scheduling and processing.

You can create Plans and Subscriptions within the Partner Portal or via API. For API details, see the Plans and Subscriptions sections in the API Reference.

Webhooks

Recurring billing events can trigger webhook notifications so your platform stays in sync.

Common use cases include:

Updating subscription status in your system
Notifying customers of billing changes
Syncing billing data with reporting tools

See the Recurring Events guide for full webhook details and event payloads.