Recurrent Payments
Accepted payment method: credit card.
What is recurrence?
Recurrence is a periodic billing service for businesses that need to charge regularly for their products and/or services. It is commonly used for magazine subscriptions, tuition fees, and software licenses, among others.
Each merchant can configure recurrence parameters such as frequency, start and end dates, number of attempts, interval between attempts, and more.
You can set up to four retry attempts for a transaction that is not approved initially.
Benefits of recurrent payments
- Gateway de Pagamento manages the scheduled payments;
- It does not affect the shopper's credit limit;
- Parameters can be adjusted whenever necessary.
How does recurrence work?
There are two ways to create recurring payments:
- Authorize a transaction and schedule future recurrences;
- Schedule a recurrence.
Characteristics
- The accepted payment method is credit card;
- A recurring transaction cannot be split into installments;
- There is a cost for the service and for each transaction analyzed by the anti-fraud system.
Recurring sales with credit cards do not require CVV.
Warning
- Recurrence is not available for e-wallet transactions due to the need for temporary keys to perform credit operations;
- For security reasons, recurrence is only possible for cards that pass the Luhn Algorithm check, also known as "mod10."
The following operations related to recurring transactions are possible:
- Authorize recurrence with a credit card;
- Schedule future authorizations;
- Update shopper information;
- Change the end date of the recurrence;
- Change the recurrence interval;
- Change the recurrence day;
- Update the transaction amount for the recurrence;
- Change the next payment date;
- Update the payment details of the recurrence;
- Deactivate a recurring order;
- Reactivate a recurring order.
How do I enable recurrence?
- Contact the acquirer to configure the recurrence option;
- Refer to the Gateway de Pagamento API Reference to learn about the details of recurrence integration and the possible operations.
Stored credential transaction identifiers
According to card brand rules, recurring transactions require identification fields that link each charge to the original CIT: IssuerTransactionId (all card brands) and TransactionLinkId (Mastercard). In own recurrence, also send Payment.OriginalRecurrentAmount. In scheduled recurrence, the IssuerTransactionId and TransactionLinkId fields are sent automatically in subsequent transactions.
Card brand identifier: IssuerTransactionId
IssuerTransactionIdThe card brand identifier (IssuerTransactionId) is a code returned in the CIT response or in the card verification response (VerifyCard), and it must be sent in the subsequent recurring transactions of all card brands. See more details in Brand identifiers for Cielo acquirer.
TLID Mastercard
The Transaction Link Identifier (TLID), sent and returned in the TransactionLinkId field, is a unique identifier generated by the Mastercard card brand during a CIT, used to link related MITs. The TLID applies to the VerifyCard response (response only) and to credit, debit, and recurring transactions.
For Mastercard, send IssuerTransactionId and TransactionLinkId together in MITs: both parameters are mandatory.
| Phase | Description |
|---|---|
| Phase 1 | Current. The TransactionLinkId field is available in the responses of VerifyCard by card number, credit card payment creation, debit card payment creation, and in the query by PaymentId. |
| Phase 2 | Required inclusion of the TransactionLinkId in the request (MIT) starting Oct 23, 2026. |
Scheduled recurrence: in subsequent transactions, the
IssuerTransactionIdandTransactionLinkIdfields are sent automatically.
The TransactionLinkId sent in the request must have exactly 22 characters (A-Z, a-z, 0-9, hyphen, and underscore). If the value is outside this format, Cielo ignores it without returning an error. When Cielo sends the TLID to the card brand, the response also includes SentTransactionLinkId, with the value that was sent. The VerifyCard request does not accept the field.
See more details in Brand identifiers for Cielo acquirer.
Updated 16 days ago