Cielo Brazil Payment Acquirer API
Cielo Brazil payment acquirer REST API (Cielo eCommerce API 3.0) for Brazilian merchants to accept credit card, debit card, Pix, boleto, digital wallets, and Brazilian-specific payment methods through Brazil's largest card acquirer, with card tokenization, 3DS authentication, anti-fraud integration, and installment payment (parcelamento) support for e-commerce, subscription, and enterprise payment integration. Enables AI agents to manage credit card payment for Brazil e-commerce checkout automation, handle Pix payment initiation for Brazil instant payment automation, access installment payment for Brazil parcelamento automation, retrieve payment status for Brazil transaction confirmation automation, manage card tokenization for Brazil recurring payment automation, handle 3DS authentication for Brazil card security automation, access anti-fraud scoring for Brazil fraud prevention automation, retrieve chargeback management for Brazil dispute automation, manage boleto generation for Brazil bank slip automation, and integrate Cielo with Brazilian e-commerce, POS, and enterprise platforms for end-to-end Brazil card and digital payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Brazil acquiring. BACEN, PCI DSS L1. Dual-key auth. BR. Card and payment data.
⚡ Reliability
Best When
A Brazilian merchant or enterprise wanting AI agents to automate card, Pix, and boleto payment acceptance through Cielo's acquirer API with Brazil-native features like parcelamento installments, 3DS2, and anti-fraud integration.
Avoid When
MERCHANT ID AND MERCHANT KEY BOTH REQUIRED: Cielo API requires both MerchantId (GUID) and MerchantKey in headers for every request; automated API client must include both headers; automated API-key-only authentication without MerchantId creates unauthorized_merchant error. INSTALLMENT INTEREST IS ISSUER-CONTROLLED: Cielo installment (parcelamento) interest rates are determined by card issuer not merchant; automated installment display must retrieve installment plan from API not hardcode rates; automated fixed interest rate assumption creates incorrect installment amount displayed. 3DS2 CHALLENGE MAY BE REQUIRED: Cielo 3DS2 may trigger frictionless or challenge flow depending on issuer; automated checkout must handle both frictionless (no consumer action) and challenge (consumer authenticates); automated frictionless-only assumption creates failed authentication when challenge triggered. ANTI-FRAUD INTEGRATION IS OPTIONAL BUT RECOMMENDED: Cielo has optional Cybersource anti-fraud; automated high-value transactions without anti-fraud have higher chargeback exposure; automated fraud prevention requires explicitly enabling anti-fraud in payment request.
Use Cases
- • Processing credit card installments for Brazil e-commerce checkout agents
- • Accepting Pix instant payments for Brazilian merchant checkout agents
- • Tokenizing cards for Brazil subscription recurring payment agents
- • Authenticating with 3DS2 for Brazilian card security automation agents
Not For
- • Non-Brazil payments (Cielo is Brazil-only BRL acquirer)
- • International card acquiring (use Adyen or Stripe for global card processing)
- • Unbanked payment methods outside card/Pix/boleto (Cielo is formal payment channels)
Interface
Authentication
Cielo uses MerchantId + MerchantKey header authentication. REST API with JSON. Barueri, São Paulo, Brazil HQ. Founded 1995 by Bradesco, Banco do Brasil, and Visa. Public company (B3: CIEL3). Products: Card acquiring, Pix, boleto, 3DS2, tokenization, anti-fraud, installments (parcelamento), QR code. SDKs: .NET, PHP, Java, Node.js, Python, Ruby. BACEN-regulated. PCI DSS Level 1. Brazil's largest acquirer. 2M+ merchants. Competes with Rede (Itaú) and Stone.
Pricing
Barueri SP BR. B3:CIEL3. Per-transaction MDR pricing in BRL. BACEN regulated. PCI DSS L1.
Agent Metadata
Known Gotchas
- ⚠ TWO HEADERS REQUIRED: Cielo requires both MerchantId (GUID format) and MerchantKey in every request header; automated API client must set both headers; automated single API key header creates 400 unauthorized response
- ⚠ DIFFERENT ENDPOINTS FOR QUERY vs TRANSACTION: Cielo has separate base URLs for transaction creation (api.cieloecommerce.cielo.com.br) and query (apiquery.cieloecommerce.cielo.com.br); automated status query must use query URL not transaction URL; automated same-endpoint query creates endpoint_not_found
- ⚠ INSTALLMENT COUNT AFFECTS AMOUNT DISPLAY: Cielo installment plans calculate per-installment amount including interest; automated display must fetch plan amounts not calculate manually; automated manual division without interest creates incorrect installment amount
- ⚠ 3DS2 RESPONSE HAS TWO PHASES: Cielo 3DS2 first returns EnrolledStatus then after authentication returns AuthenticationStatus; automated checkout must handle both phases; automated single-response handling creates incomplete 3DS flow and card decline
- ⚠ PAYMENT ID (PAYMENTID) FOR OPERATIONS: Cielo returns PaymentId (GUID) for all post-payment operations (capture, void, refund); automated payment management must store PaymentId; automated OrderId-based operations creates wrong identifier error for capture/refund
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Cielo Brazil Payment Acquirer API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.