Create payment with network token via external integration

If the merchant uses a gateway or another partner that already offers the network token solution, it is necessary to send some specific parameters in the request to the Gateway de Pagamento so that the card network receives the token data.

  • Payment.CreditCard.Cryptogram: this is the token cryptogram generated by the card network for each transaction and associates the token with a specific transaction;
  • Payment.IssuerTransactionId: this is the card network's identifier for transactions in a series of recurrences (stored credentials). It is important to send the Payment.IssuerTransactionId with each transaction so that the card brand and issuer can identify that there is a previous transaction with that token (and improve the chances of approval).
ℹ️

Mastercard transactions

For tokenized MIT transactions on the Mastercard card brand, you do not need to send the cryptogram, because the token was previously validated in the original CIT transaction. In other words:

  • in CIT transactions, the cryptogram must be sent in the Payment.CreditCard.Cryptogram field;
  • in MIT transactions, the cryptogram must not be sent.

If the cryptogram is not sent, you must provide the Payment.IssuerTransactionId.

See more about CIT and MIT transactions at Transaction Initiator Indicator.

⚠️

Warning

  • Available only for Cielo, Rede, and Getnet.

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.


Check out the example request for using a card token with external integration:

Request

EnvironmentMethodEndpoint
Sandboxhttps://apisandbox.braspag.com.br/v2/Sales/
Productionhttps://api.braspag.com.br/v2/Sales/

Header parameters

ParameterDescriptionTypeSizeRequired
Content-TypeMedia type accepted by the resource.String40Yes
MerchantIdStore identifier in Cielo.String36Yes
MerchantKeyPublic key for dual authentication in Cielo.String40Yes
RequestIdRequest identifier, used when the store uses different servers for each GET/POST/PUT.String36No

Body Parameters

Check the standard credit card request to verify all mandatory fields. The table below presents the exclusive parameters for tokenization via external integration.

ParameterTypeSizeRequiredDescription
Payment.CreditCard.CardNumberText19YesToken generated by the brand (DPAN). Indication that the CardNumber should be filled with the DPAN in case of brand tokenization
Payment.CreditCard.CardNumberTypeText--ConditionalThis field supports the values PAN and DPAN.
  • Optional: When the customer sends the Cryptogram.
  • Required: When the customer sends a tokenized card (DPAN) without the Cryptogram. In this case, the value of CardNumberType must be DPAN.
Payment.CreditCard.HolderText25YesBuyer's Name printed on the card.
Payment.CreditCard.CryptogramText28ConditionalCryptogram generated by the brand. Must be sent if tokenization is done by the brand (external integration).
Payment.CreditCard.ExpirationDateText7YesExpiration date of the token generated by the brand.
Payment.CreditCard.SecurityCodeText4NoSecurity code printed on the back of the card - See Attachment.
Payment.CreditCard.SaveCardBoolean
No (Default false)Boolean that identifies if the card will be saved to generate the CardToken. Learn more about Tokenization.
Payment.CreditCard.BrandText10YesCard brand (Visa / Master / Amex / Elo / Aura / JCB / Diners / Discover / Hipercard).

Must be sent if tokenization is done by the brand (external integration).

Example of the request

{
  "MerchantOrderId": "Loja123456",
  "Customer": {
    "Name": "Comprador Teste",
    "Email": "[email protected]",
    "Birthdate": "1991-01-02",
    "Address": {
      "Street": "Rua Teste",
      "Number": "123",
      "Complement": "AP 123",
      "ZipCode": "12345987",
      "City": "Rio de Janeiro",
      "State": "RJ",
      "Country": "BRA"
    },
    "DeliveryAddress": {
      "Street": "Rua Teste",
      "Number": "123",
      "Complement": "AP 123",
      "ZipCode": "12345987",
      "City": "Rio de Janeiro",
      "State": "RJ",
      "Country": "BRA"
    }
  },
  "Payment": {
    "Type": "CreditCard",
    "Amount": 15700,
    "Currency": "BRL",
    "Country": "BRA",
    "ServiceTaxAmount": 0,
    "Installments": 1,
    "Interest": "ByMerchant",
    "Capture": true,
    "Authenticate": false,
    "SoftDescriptor": "123456789ABCD",
    "CreditCard": {
      "CardNumber": "1234123412341231",
      "CardNumberType":"DPAN",
      "Holder": "Teste Holder",
      "Cryptogram": "abcdefghijklmnopqrstuvw==",
      "ExpirationDate": "12/2030",
      "SecurityCode": "123",
      "SaveCard": "true",
      "Brand": "Visa"
    }
  }
}

Response

{
    "MerchantOrderId": "Loja123456",
    "Customer": {
        "Name": "Comprador Teste",
        "Identity":"11225468954",
        "IdentityType":"CPF",
        "Email": "[email protected]",
        "Birthdate": "1991-01-02",
        "Address": {
            "Street": "Rua Teste",
            "Number": "123",
            "Complement": "AP 123",
            "ZipCode": "12345987",
            "City": "Rio de Janeiro",
            "State": "RJ",
            "Country": "BRA"
        },
        "DeliveryAddress": {
            "Street": "Rua Teste",
            "Number": "123",
            "Complement": "AP 123",
            "ZipCode": "12345987",
            "City": "Rio de Janeiro",
            "State": "RJ",
            "Country": "BRA"
        }
    },
    "Payment": {
        "ServiceTaxAmount": 0,
        "Installments": 1,
        "Interest": "ByMerchant",
        "Capture": true,
        "Authenticate": false,
        "CreditCard": {
            "CardNumber": "455187******0183",
            "Holder": "Teste Holder",
            "ExpirationDate": "12/2030",
            "SaveCard": true,
            "CardToken": "d37bf475-307d-47be-b50a-8dcc38c5056c",
            "Brand": "Visa"
        },
        "ProofOfSale": "674532",
        "Tid": "0305020554239",
        "AuthorizationCode": "123456",
        "SoftDescriptor":"123456789ABCD",
        "PaymentId": "24bc8366-fc31-4d6c-8555-17049a836a07",
        "Type": "CreditCard",
        "Amount": 15700,
        "CapturedAmount": 15700,
        "Country": "BRA",
        "ExtraDataCollection": [],
        "Status": 2,
        "ReturnCode": "6",
        "ReturnMessage": "Operation Successful",
        "Links": [
            {
                "Method": "GET",
                "Rel": "self",
                "Href": "https://apisandbox.braspag.com.br/v2/sales/{PaymentId}"
            },
            {
                "Method": "PUT",
                "Rel": "void",
                "Href": "https://apisandbox.braspag.com.br/v2/sales/{PaymentId}/void"
            }
        ]
    }
}

Response property

ParâmetroDescriçãoTipoTamanhoFormato
ProofOfSaleAuthorization number, identical to NSU.Text6Alphanumeric text
TidTransaction ID at the acquirer.Text20Alphanumeric text
AuthorizationCodeAuthorization code.Text6Alphanumeric text
SoftDescriptorText to be printed on the cardholder's bank statement - available only for VISA/MASTER - does not allow special charactersText13Alphanumeric text
PaymentIdPayment identification number, required for operations such as Query, Capture, and Cancellation.GUID36xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
ECIElectronic Commerce Indicator. Represents how secure a transaction is.Text2Example: 7
StatusTransaction Status.Byte
2
ReturnCodeAcquirer return code.Text32Alphanumeric text
ReturnMessageAcquirer return message.Text512Alphanumeric text
CardtokenCard identification token.GUID36xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Payment.IssuerTransactionIdTransaction 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 IssuerTransactionId.string30Alphanumeric text
Payment.TransactionLinkIdTransactionLinkId 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 TLID Mastercard
Format: 22 alphanumeric characters (A–Z, a–z), case-sensitive, and may include hyphens (-) and underscores ()._
string22Alphanumeric text