Subscription

Tokenization

For any subscription model, it is necessary to store the end user's payment data. This process, known as tokenization, can be done via both our in-person payment solution and our online solution.

Therefore, this will be the first step before managing any subscription.

The Scheduler

The first question we should ask ourselves when implementing a subscription system is: what is our scheduler model? In other words, which system will handle the charging processes, determine if special calendar rules are needed, and ultimately calculate the volume of charges we want to process.

A scheduler is a system responsible for triggering processes based on a configured frequency, governed by a calendar-based logic or initiated by chained external business processes.

If, as a Merchant, you already have a scheduler and only need to send multiple charges, you can use our batch call to send multiple charges in a single API call.

If you need a simple scheduler to automatically trigger charges with a card already tokenized in our system according to a calendarized configuration (number of installments and frequency of charge), the API you need is Recurring Payments.

In this integration, the retries system should be set up on your end by launching individual transactions with tokenized cards.