| Environment | Method | Endpoint |
|---|---|---|
| Sandbox | post | https://apisandbox.braspag.com.br/v2/sales |
| Production | post | https://api.braspag.com.br/v2/sales |
To submit a Gateway de Pagamentos transaction to Split de Pagamento, simply set thePayment.DoSplitparameter to true and add thePayment.SplitPaymentsnode.
The characteristics of a credit transaction are:
- Send
Payment.Typeas "CreditCard";- Send the
Payment.CreditCardnode;- If the transaction goes through fraud analysis, send the
Payment.FraudAnalysisnode. See an example of a credit transaction with fraud analysis in the Gateway manual;- Sending fees in the request: If the request includes fees, they will take precedence over the fees registered in the portal. Portal fees will only apply when no fees are sent or in cases of redistribution.
The following example corresponds to a transaction of R$100.00 with the node containing the split rules. In this example, the following fees were assumed:
Split de Pagamento Fee: 2% MDR + R$0.10 Fixed Fee
Master fee with seller A: 5% MDR (including the 2% MDR from Split de Pagamento) + R$0.30 Fixed Fee
Master fee with seller B: 4% MDR (including the 2% MDR from Split de Pagamento) + R$0.15 Fixed Fee
Seller A:
- Credit of R$57.00 (R$60.00 from the transaction minus R$3.00 MDR);
- Debit of R$0.30 Fixed Fee.
The total amount to be received by seller A will be R$56.70.
Seller B:
- Credit of R$38.40 (R$40.00 from the transaction minus R$1.60 MDR);
- Debit of R$0.15 Fixed Fee.
The total amount to be received by seller B will be R$38.25.
Master:
Credit of R$3.05 (R$3.00 MDR + R$0.30 Fixed Fee from seller A, plus R$1.60 MDR + R$0.15 Fixed Fee from seller B, minus R$2.00 MDR Split);
Debit of R$0.10 (Fixed Fee agreed with the Split).
The total amount to be received by the Master will be R$2.95.
Split de Pagamento:
- Credit of R$2.10 (R$2.00 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 will be R$2.10.
See the request for this transaction of R$100.00 with the node containing the split rules.
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.
Visa Intelligent Data Exchange (IDX)
If you use Visa’s IDX authentication service, see Visa Intelligent Data Exchange (IDX).
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
IssuerTransactionIdandTransactionLinkIdfields 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.
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 | 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 |