⚠️

To submit a transaction from the API E-commerce Cielo to the Split, simply send the parameter Payment.DoSplit as true and add the node Payment.SplitPayments.

Sending fees in the request: If the request includes fees, they will take precedence over the fees registered in the portal e-commerce. Portal e-commerce fees will only apply when no fees are sent or in cases of redistribution.

Split payment example

The transaction amount is BRL 100.00. In this example, following fees were assumed:

Split Fee: 2% MDR + BRL 0.10 Fixed Fee.
Master fee with seller A: 5% MDR (including the 2% Split MDR) + 0.30 Fixed Fee.
Master fee with seller B: 4% MDR (including the 2% Split MDR) + 0.15 Fixed Fee.

Seller A:

• Credit of BRL 57.00 (BRL 60.00 from the transaction minus 3.00 MDR);
• Debit of BRL 0.30 Fixed Fee.

The amount receivable by seller A will be BRL 56.70.

Seller B:

• Credit of R$38.40 (R$40.00 from the transaction minus BRL 1.60 MDR);
• Debit of R$0.15 Fixed Fee.

The amount receivable by seller B will be BRL 38.25.

Master:

• Credit of BRL 3.05 (BRL 3.00 MDR + 0.30 Fixed Fee from seller A, combined with BRL 1.60 MDR + 0.15 Fixed Fee from seller B, minus BRL 2.00 Split MDR);
• Debit of BRL 0.10 (Fixed Fee agreed with the Split).

The amount receivable by the master will be BRL 2.95.

Split:

• Credit of BRL 2.10 (BRL 2.00 MDR applied on the total transaction amount plus 0.10 Fixed Fee agreed with the Master)

The amount receivable by Split will be BRL 2.10.

See the example request for this scenario in the Example button in the request block.

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 transaction, used to link the related MIT transactions. The TLID applies to the Zero Auth response (response only) and to credit card, debit card, and merchant recurrence transactions.

For Mastercard, send IssuerTransactionId and TransactionLinkId together in MIT transactions: both parameters are mandatory.

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, hyphens, and underscores). If the value doesn't match this format, Cielo ignores it and returns no error. When Cielo sends the TLID to the card brand, the response also includes the SentTransactionLinkId with the value sent. The Zero Auth request doesn't accept this field.

See more details in Card Brand Identifiers.

Credit card transaction response

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