Create recurring payment

Authorize a recurring payment with a credit card

Environment

Method

Endpoint

Sandbox

https://apisandbox.braspag.com.br/v2/sales/

Production

https://api.braspag.com.br/v2/sales/

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 2026

This 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.


Card brand identifiers: in scheduled recurrence, the IssuerTransactionId and TransactionLinkId fields are sent automatically in subsequent transactions. In sandbox, these fields are only returned with the Simulado provider and an authorized transaction scenario. See more details in Brand identifiers for Cielo acquirer.

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

The 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), 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.

PhaseDescription
Phase 1Current. 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 2Required inclusion of the TransactionLinkId in the request (MIT) starting Oct 23, 2026.

Scheduled recurrence: in subsequent transactions, the IssuerTransactionId and TransactionLinkId fields 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.

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

RecurrentPaymentId

ID that represents the recurrence, used for future queries and changes.

string

36

NextRecurrency

Date when the next recurrence will occur.

string

10

EndDate

Date when the recurrence ends.

string

10

Interval

Interval between recurrences.

string

10

AuthorizeNow

Defines whether the first recurrence will be authorized immediately or not.
If you want to authorize a recurrence later, see Schedule a recurrence.

boolean


CardBrandStatus

Mastercard account status feedback

  • VALID: Valid card or no updates on base
  • UNKNOWN: Card not available at ABU
  • NON_PARTICIPATING: Card not available at ABU
  • ACCOUNT_CLOSED: Card is closed
  • UPDATE: vUpdate plastic or expiration
  • EXPIRY: Validity update
  • ERROR: There was an error in the update (Timeout for example)

string

Payment.IssuerTransactionId

Transaction identifier generated by the card brand and returned in the CIT response. Store the value to send it in subsequent MITs: sending is mandatory, for all card brands, in recurring, incremental, and re-authorized transactions. See more details in Brand identifiers for Cielo acquirer.

string

30

Payment.TransactionLinkId

Unique identifier (TLID) generated by Mastercard and returned in the response, used to link the CIT to subsequent MITs. For Mastercard, send the original TransactionLinkId together with IssuerTransactionId: both are mandatory, and sending the TransactionLinkId is mandatory starting Oct 23, 2026. See more details in Brand identifiers for Cielo acquirer.
Format: 22 alphanumeric characters (A–Z, a–z), case-sensitive, and may include hyphens (-) and underscores ()._

string

22

Fields returned by Renova Fácil

PropriedadeDescriçãoTipoTamanho
NewCard.CardNumberShopper's new card number.string16
NewCard.ExpirationDateNew expiry date of the card.string7
NewCard.BrandCard brand.string10
NewCard.SaveCardIdentifies whether the card generated Cardtoken during the transaction. Find out more about Tokenization of Cardsbooleano***
⚠️

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 BrandTransactionId must be entered.
  • For Visa or Elo brands, enter the BrandTransactionId received in the first transaction.
  • For Mastercard, enter the BrandTransactionId received on the first or previous transaction.
  • The value of the BrandTransactionId will be new with each recurring transaction response.

Body Params
string
required

Order ID number.

Customer
object
Payment
object
Headers
string
required

Store identifier at Gateway de Pagamento. Size: 36.

string
required

Public key for dual authentication at Gateway de Pagamento. Size: 40.

string

Store-defined request identifier used when the merchant uses different servers for each GET/POST/PUT. Size: 36.

Response

Language
LoadingLoading…
Response
Choose an example:
application/json