Authorize a recurring payment with a credit card
Environment | Method | Endpoint |
|---|---|---|
Sandbox | post |
|
Production | post |
|
Add the RecurrentPayment node to the Payment node to configure a recurrence when authorizing a transaction for the first time in the series of recurrences.
Alphanumeric CNPJs will be implemented by the Brazilian Federal Revenue Service in July 2026This change applies only to new registrations. There will be no changes to existing CNPJs.
The alphanumeric CNPJ is already supported by Cielo, with no changes required to your integration.
We recommend checking whether adjustments are needed in your merchant’s own checkout systems.
Stored credential transaction identifiers
According to card brand rules, recurring transactions and those with stored credentials may require additional identification fields, such as IssuerTransactionId and TransactionLinkId. See more details below.
Card brand identifier: IssuerTransactionId
IssuerTransactionIdThe card brand identifier is an identification code for recurring or stored credential transactions, returned in the authorization response or in the card verification response (VerifyCard). See more details in IssuerTransactionId.
TLID Mastercard
The Transaction Link Identifier (TLID) is a unique identifier generated by the Mastercard card brand during a transaction. It is created in the initial transaction (CIT) and must be used to associate all subsequent transactions (MIT) within the same cycle.
| Phase | Description |
|---|---|
| Phase 1 | Availability of the TransactionLinkId 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 |
See more details in Brand identifiers for Cielo.
Recurring payment transaction response
The following table presents the main parameters that can be returned by the API when creating a recurring payment.
Property | Description | Type | Size |
|---|---|---|---|
| ID that represents the recurrence, used for future queries and changes. | string | 36 |
| Date when the next recurrence will occur. | string | 10 |
| Date when the recurrence ends. | string | 10 |
| Interval between recurrences. | string | 10 |
| Defines whether the first recurrence will be authorized immediately or not. | boolean | |
| Mastercard account status feedback
| string | |
| Transaction identifier generated by the card brand; it must be sent to reference the original/previous transaction in related operations, such as recurring payments. See more details in Brand identifiers for Cielo acquirer. | string | 30 |
|
| string | 22 |
Fields returned by Renova Fácil
| Propriedade | Descrição | Tipo | Tamanho |
|---|---|---|---|
NewCard.CardNumber | Shopper's new card number. | string | 16 |
NewCard.ExpirationDate | New expiry date of the card. | string | 7 |
NewCard.Brand | Card brand. | string | 10 |
NewCard.SaveCard | Identifies whether the card generated Cardtoken during the transaction. Find out more about Tokenization of Cards | booleano | *** |
Acquirer Rede
- For the Rede2 provider, the response will return the
BrandTransactionId, which is the identifier of recurring transactions with the flags at the Rede acquirer.- For each new transaction in the sequence of recurrences, the
BrandTransactionIdmust be entered.- For Visa or Elo brands, enter the
BrandTransactionIdreceived in the first transaction.- For Mastercard, enter the
BrandTransactionIdreceived on the first or previous transaction.- The value of the
BrandTransactionIdwill be new with each recurring transaction response.