Getnet DocsGetnet Docs

Recurring Payments

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page
Connect to CursorUse these docs in CursorConnect to VS CodeUse these docs in VS Code

This feature allows managing transactions that repeat multiple times on a specific date range and charge on a periodic basis, easily and quickly. With this solution, you can issue recurring charges without consuming the customer’s card limit with each new charge. It is possible to define the billing frequency according to your model, annualy, monthly, or bimonthly, according to your needs.

Getnet stores card data in the secure vault (tokenization) so that the customer does not need to enter the data with each payment. The initial setup requires integration via API + vault enablement + recurrence module activation. After this, charges are made automatically using the stored card.

You can implement any of the following functionalities according to your requirements, depending on the country to consider:

  • Subscriptions Engine
  • One Click transactions - Cardholder initiated
  • Tokenizations transactions - Merchant initiated

Below are the available card brands that support recurring payments in each country

FunctionalityArgentinaBrazilChileMexicoUruguaySpainColombiaPortugal
Subscriptions Engine✅✅✅✅----
One Click Payments-✅--✅✅✅✅
Merchant Intiated transactions (MIT)-✅--✅✅✅✅

Subscriptions Engine

This functionalities is implemented by following these steps.

1. Client registration

The client or consumer of the product/service must be registered.

2. Periodicity plan:

The information on the value and number of the instalments and periodicity that should match with one of the following options:

  • Annual: Charges once a year,
  • Monthly: Charges one a month,
  • Bimonthly: Charges once every 2 months,
  • Quarterly: Charges once every 3 months,
  • Half-yearly: Charges once every 6 months,
  • Specific: Specific billing cycle in days.

3. Subscription

For recurrence to work, the client and the plan must be linked through the creation of a subscription, and the signature conditions will be respected in all recurring charges. If the change request date is within the period, the change will be counted from the request date + 1 day.

For example: If the billing schedule date to be changed is 01/20/2025 and the request date is 01/10/2025, the valid period for the change will be from 01/11/2025 to 01/31/2025.

Charges with scheduling that are in the retry process and had the payment denied will be disregarded in the validation of the period.

Purchase of the Recurrence Package or Modular Package with Recurrence and Vault.

For more details, see the API reference

One Click Payments and Merchant Intiated transactions

Card on File (CoF) is used to securely store card details in order to enable future payments without requiring the customer to re-enter their information for each transaction. In the case of recurring payments, this functionality allows for automated periodic charges (e.g., subscriptions, memberships, or subscription-based services), ensuring a seamless experience and reducing friction at checkout.

In order to use it as a Recurring Payment feature, we have the following options for credentials_on_file_type

ValuesDescription
ONE_CLICKUsed when the first transaction (installment) of a normal payment is made.
ONE_CLICK_PAYMENTUsed when making transactions for the remaining installments of a normal payment. Note: It is necessary to inform the transaction_id of the first transaction carried out.
RECURRINGUsed when the first transaction (installment) of a recurring payment is made.
RECURRING_PAYMENTUsed when making transactions for the remaining installments of a recurring payment. Note: It is necessary to inform the transaction_id of the first transaction carried out.

Next Step

You can explore more features of the Getnet Global API:

  • Read more about Create a Tokenized Payment