Create a credit card payment

Create a credit card transaction

EnvironmentMethodEndpoint
Sandboxhttps://apisandbox.braspag.com.br/v2/sales/
Productionhttps://api.braspag.com.br/v2/sales/
⚠️

Warning

  • The Payment.ServiceTaxAmount field is exclusive to airlines and travel agencies, allowing them to charge the boarding fee separately from the airfare;
  • To validate if the authentication was accepted in the authorization response, consider the ECI outside the Payment.ExternalAuthentication node;
  • The JCB and Diners brands are foreign and do not allow credit card installments.
ℹ️

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.


3DS authentication in credit card payments

3DS authentication is optional for credit card transactions.

If your store integrates with the 3DS protocol for cardholder authentication, pay attention to the parameters that must be provided in the request:

  • Send the parameter Payment.Authenticate = "true";
  • Provide the data received from the 3DS script output in the Payment.ExternalAuthentication node;
  • For transactions with 3DS Data Only authentication, provide the parameter ExternalAuthentication.DataOnly as "true".
  • To confirm if authentication was accepted in the authorization, check the ECI value returned in Payment.Eci. The API replicates the ECI informed by the merchant in the Payment.ExternalAuthentication field. However, the value actually used by the brand in the authorization is the one shown in Payment.Eci.
ℹ️

Important

The validation and return of the Payment.Eci field occur only in the production environment at this initial stage.

Visa Intelligent Data Exchange (IDX)

If you use Visa’s IDX authentication service, see Visa Intelligent Data Exchange (IDX).

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

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

See more details in Brand identifiers for Cielo.


Credit card transaction response

Following table presents the main parameters that may be returned by the API when creating a credit card payment.

Property

Description

Type

Syze

AcquirerTransactionId

Transaction ID in the payment provider.

string

40

ProofOfSale

Sales receipt number, identical to the NSU (Unique Sequential Number).

string

20

AuthorizationCode

Authorization code

string

300

SentOrderId

Indicates which order number was sent to the acquirer.

  • If the number provided is in an invalid format, the acquirer will generate a new identifier, returned in the SentOrderId field.
  • If the format is valid and accepted by the acquirer, the SentOrderId field will contain the same value provided in MerchantOrderId.

GUID


PaymentId

Payment identifier field. PaymentId will be used in future operations such as query, capture, and void.

string

36

ReceivedDate

Date the transaction was received by Cielo.

datetime

19

CapturedDate

Date the transaction was captured.

string

19

CapturedAmount

Captured amount, without punctuation.

integer

15

Payment.ECI

Electronic Commerce Indicator. Represents the authentication result.

string

2

ReasonCode

API return code to indicate success or error in the operation.

string

32

ReasonMessage

Message corresponding to the ReasonCode.

string

512

Status

Transaction status. See the complete list of transaction status list.

byte

2

ProviderReturnCode

Code returned by the payment provider (acquirer or issuer).

string

32

ProviderReturnMessage

Message returned by the payment provider (acquirer or issuer).

string

512

Payment.MerchantAdviceCode

Brand return code that defines the retry period. Valid for Mastercard brand. Learn more at Merchant Advice Code (MAC) – Mastercard

string

2

Payment.IssuerTransactionId

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

Payment.TransactionLinkId

TransactionLinkId is a unique identifier generated by Mastercard for each transaction. It must be used to link the initial transaction to subsequent related transactions. 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

BrandTransactionId

Identifier for recurring transactions with card brands at acquirer Rede. Exclusive to Rede.

string

21


Body Params
int32
required

Order ID number.

Customer
object
Payment
object
Headers
string
required
Defaults to e3c24810-18bb-4bd7-88a0-a36d6b4a0731

Merchant identifier at Braspag.

string
required
Defaults to GQUAIWVDKUINZRHDQPLHUVHAIIFEIXFEXWPOYGHY

Public key for dual authentication at Braspag.

string

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

Responses

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json