What is it?

Recurring payments are transactions that happen on a regular schedule — such as monthly subscriptions, annual memberships, or automated billing for usage-based services. Instead of asking customers to re-enter their payment details each time, these payments are processed automatically after an initial consent is provided.

How it works?

There are certain events that need to take place in a correct order to make recurring payments work properly.

There are two main types of recurring payment events:

• Customer Initiated Transactions (CIT): This is the first payment in a recurring setup. It’s triggered directly by the customer, who enters their card details and provides consent for future billing. This transaction establishes the foundation for storing the card and linking future charges to the original authorization.
• Merchant Initiated Transactions (MIT): These are the follow-up payments that occur without direct involvement from the customer. Using the stored card information and referencing the original CIT, the merchant can charge the card at scheduled intervals or based on usage. MITs must comply with payment network rules, including attaching proper metadata that ties them back to the initial transaction.

Swap Token feature

To support flexibility, we also offer a Swap Token feature. This allows you to reuse the token already provided by your partner without a need PCI process of token migration. It’s a key tool when switching processors, helping ensure recurring payments continue seamlessly.

Recurring API collection

Please refer to our Recurring API collection for all needed details to process recurring payments successfully.