Create a credit transaction without the split node

⚠️
To submit a Gateway de Pagamento transaction to Split de Pagamento, simply send the Payment.DoSplit parameter as true and add the Payment.SplitPayments node.

ℹ️
The characteristics of a credit transaction are:

Send Payment.Type as "CreditCard";

Send the Payment.CreditCard node;

If the transaction goes through fraud analysis, send the Payment.FraudAnalysis node. Check an example of a credit transaction with fraud analysis in the Gateway manual.

In this case, the master receives the transaction amount minus the MDR agreed with the Split de Pagamento. The Fixed Fee agreed between the master and the Split de Pagamento is applied directly to both parties' schedules.

Split de Pagamento Fee: 2% MDR + R$0.10 Fixed Fee.

Master:

Credit of R$98.00 (R$100.00 transaction amount minus R$2.00 MDR from Split de Pagamento);
Debit of R$0.10 (Fixed Fee agreed with Split de Pagamento).

The total amount to be received by the master will be R$97.90.

Split de Pagamento:

Credit: R$2.10 (MDR applied on the total transaction amount plus R$0.10 Fixed Fee agreed with the Master).

The total amount to be received by Split de Pagamento will be R$2.10.

See the request for this transaction of R$100.00, with automatic capture, without the node containing the split rules.

ℹ️
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.

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

Request

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

{
    "merchantorderid": "30082019",
    "customer": {
        "Name": "Comprador Accept",
        "email": "[email protected]",
        "Identity": "18160361106",
        "identitytype": "CPF",
        "Mobile": "5521995760078"
    },
    "payment": {
        "Provider": "Simulado",
        "type": "Creditcard",
        "DoSplit": true,
        "amount": 10000,
        "capture": true,
        "installments": 1,
        "softdescriptor": "teste",
        "CreditCard": {
            "cardNumber": "4481530710186111",
            "holder": "Yamilet Taylor",
            "ExpirationDate": "12/2030",
            "SecurityCode": "693",
            "Brand": "Visa",
            "SaveCard": false
        }
    }
}

Below are the field properties in this request:

Property (Header)	Type	Size	Required	Description
`MerchantId`	Guid	36	Yes	Merchant identifier in Split de Pagamento
`MerchantKey`	Text	40	Yes	Public key for Dual Authentication in Split de Pagamento
`Content-Type`	Header	40	Yes	Application/json

Property	Type	Size	Required	Description
`MerchantOrderId`	Text	50	Yes	Order identification number
`Customer.Email`	Text	255	No	Shopper's email
`Customer.Name`	Text	255	Yes	Shopper's name
`Customer.Identity`	Text	14	No	Shopper's CPF, or CNPJ number Allows submission of alphanumeric CNPJs.
`Customer.IdentityType`	Text	255	No	Shopper identification document type (CPF or CNPJ)
`Customer.Mobile`	Text	14	No	Shopper's mobile phone
`Customer.Phone`	Text	14	No	Shopper's phone
`Customer.DeliveryAddress.Street`	Text	255	No	Shopper's address
`Customer.DeliveryAddress.Number`	Text	15	No	Order delivery address number
`Customer.DeliveryAddress.Complement`	Text	50	No	Order delivery address complement
`Customer.DeliveryAddress.ZipCode`	Text	9	No	Order delivery address ZIP code
`Customer.DeliveryAddress.City`	Text	50	No	Order address city
`Customer.DeliveryAddress.State`	Text	2	No	Order address state
`Customer.DeliveryAddress.Country`	Text	35	No	Order delivery address country
`Customer.DeliveryAddress.District`	Text	50	No	Delivery address neighborhood
`Payment.Provider`	Text	15	Yes	Name of the payment provider. Possible values: Sandbox: Simulado Production: Cielo30
`Payment.Type`	Text	100	Yes	Payment method type. For credit card transactions, use CreditCard.
`Payment.Amount`	Number	15	Yes	Order amount (to be sent in cents)
`Payment.Installments`	Number	2	Yes	Number of installments
`Payment.Capture`	Boolean		No (Default false)	Boolean indicating whether the authorization should include automatic capture (true) or not (false).
`Payment.SoftDescriptor`	Text	13	No	Text to be printed on the cardholder's statement. On the statement, the `SoftDescriptor` may be shortened according to the acquirer and card brand rules.
`Payment.IssuerTransactionId`	Text	30	No	Transaction identifier generated by the card brand, returned in the CIT or in VerifyCard. Send in recurring, incremental, and re-authorized MITs. Mandatory for the Visa, Mastercard, Elo, and Amex card brands.
`Payment.TransactionLinkId`	Text	22	No	Unique identifier generated by the Mastercard card brand (TLID), used to link the CIT to related subsequent MITs, such as recurring payments, future installments, post-authorization charges, and card-on-file payments. Send the original value together with `IssuerTransactionId`: both are mandatory for Mastercard, and sending the `TransactionLinkId` is mandatory starting Oct 23, 2026. Format: 22 alphanumeric characters (A-Z, a-z, case-sensitive), and may include hyphen (-) and underscore (_). If the value is null, empty, or outside this format, Cielo ignores it without returning an error.
`Payment.OriginalRecurrentAmount`	Number	15	No	Amount of the original transaction (the first in the cycle), in cents. Mandatory in own recurrence (`Payment.Recurrent` = true), together with `IssuerTransactionId` and, for Mastercard, `TransactionLinkId`.
`CreditCard.CardNumber`	Text	19	Yes	Shopper's card number
`CreditCard.Holder`	Text	25	Yes	Cardholder name printed on the card
`CreditCard.ExpirationDate`	Text	7	Yes	Expiration date printed on the card
`CreditCard.SecurityCode`	Text	4	Yes	Security code printed on the back of the card
`CreditCard.Brand`	Text	10	Yes	Card brand
`CreditCard.SaveCard`	Boolean		No (Default false)	Boolean indicating whether the card will be saved to generate the token (CardToken)
`Payment.ExternalAuthentication.Cavv`	Text	--	No	Signature returned in successful authentication scenarios. ⚠️This field is mandatory for transactions authenticated by the issuer or the card brand, and for authorization requests with Data Only.
`Payment.ExternalAuthentication.Xid`	Text	28	No	Mandatory only when the 3DS version is "2" or higher. XID returned during the authentication process.
`Payment.ExternalAuthentication.Eci`	Number	1	No	Electronic Commerce Indicator returned during the authentication process.
`Payment.ExternalAuthentication.Version`	Text	5	No	Mandatory for transactions with 3DS authentication. 3DS version applied during the authentication process. Possible values: - Visa and Mastercard: "2.2.0" - Elo and Amex: "2.1.0"
`Payment.ExternalAuthentication.ReferenceId`	Text	36	No	Mandatory only when the 3DS version is "2" or higher. RequestID returned during the authentication process.
`Payment.ExternalAuthentication.DataOnly`	Boolean	--	No	Defines whether it is a 3DS authentication transaction of type Data Only. Sending this field is mandatory for Data Only transactions.

Response

{
    "MerchantOrderId": "30082019",
    "Customer": {
        "Name": "Comprador Accept",
        "Identity": "18160361106",
        "IdentityType": "CPF",
        "Email": "[email protected]",
        "Mobile": "5521995760078"
    },
    "Payment": {
        "ServiceTaxAmount": 0,
        "Installments": 1,
        "Interest": "ByMerchant",
        "Capture": true,
        "Authenticate": false,
        "Recurrent": false,
        "IssuerTransactionId": "580027442382078",
        "CreditCard": {
            "CardNumber": "448153******6111",
            "Holder": "Yamilet Taylor",
            "ExpirationDate": "12/2030",
            "SaveCard": false,
            "Brand": "Visa"
        },
        "ProofOfSale": "20190830104433081",
        "AcquirerTransactionId": "0830104433081",
        "AuthorizationCode": "042693",
        "SoftDescriptor": "teste",
        "DoSplit": true,
        "SplitPayments": [
            {
                "SubordinateMerchantId": "f43fca07-48ec-46b5-8b93-ce79b75a8f63",
                "Amount": 10000,
                "Fares": {
                    "Mdr": 2.0,
                    "Fee": 10
                },
                "Splits": [
                    {
                        "MerchantId": "f43fca07-48ec-46b5-8b93-ce79b75a8f63",
                        "Amount": 10000
                    }
                ]
            }
        ],
        "PaymentId": "5b01552e-bf38-430e-bd38-8517c36a1ca2",
        "Type": "CreditCard",
        "Amount": 10000,
        "ReceivedDate": "2019-08-30 10:44:13",
        "CapturedAmount": 10000,
        "CapturedDate": "2019-08-30 10:44:33",
        "Currency": "BRL",
        "Country": "BRA",
        "Provider": "Simulado",
        "ReasonCode": 0,
        "ReasonMessage": "Successful",
        "Status": 2,
        "ProviderReturnCode": "6",
        "ProviderReturnMessage": "Operation Successful",
        "Links": [
            {
                "Method": "GET",
                "Rel": "self",
                "Href": "https://apiquerysandbox.braspag.com.br/v2/sales/5b01552e-bf38-430e-bd38-8517c36a1ca2"
            },
            {
                "Method": "PUT",
                "Rel": "void",
                "Href": "https://apisandbox.braspag.com.br/v2/sales/5b01552e-bf38-430e-bd38-8517c36a1ca2/void"
            }
        ]
    }
}

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

Property	Description	Type	Size
`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.	Text	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 ().	Text	22
`Payment.SentTransactionLinkId`	TLID that the merchant sent in the request and that Cielo forwarded to the card brand. The field only appears when Cielo sent the TLID. See more details in Brand identifiers for Cielo acquirer.	Text	22

To submit a Gateway de Pagamento transaction to Split de Pagamento, simply send the Payment.DoSplit parameter as true and add the Payment.SplitPayments node.

Alphanumeric CNPJs will be implemented by the Brazilian Federal Revenue Service in July 2026

TLID Mastercard

Request

Response

To submit a Gateway de Pagamento transaction to Split de Pagamento, simply send the `Payment.DoSplit` parameter as true and add the `Payment.SplitPayments` node.