Iugu Brazil Payment Platform API
Iugu Brazil payment platform REST API for businesses and developers to accept Pix, boleto bancário, credit/debit card, and manage subscription billing with split payment (sub-accounts) and marketplace payment capabilities for Brazilian e-commerce, SaaS, and marketplace platforms, with emphasis on subscription management and marketplace payment splitting. Enables AI agents to manage Pix payment initiation for Brazil instant payment automation, handle boleto bancário generation for Brazil bank slip payment automation, access credit card tokenization for Brazil card payment automation, retrieve payment status for Brazil transaction confirmation automation, manage subscription creation and billing for Brazil recurring payment automation, handle split payment for Brazil marketplace disbursement automation, access sub-account management for Brazil platform payment automation, retrieve invoice management for Brazil billing automation, manage refund processing for Brazil payment reversal automation, and integrate Iugu with Brazilian e-commerce, SaaS, and marketplace platforms for end-to-end Brazil payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Brazil payments. BACEN, PCI DSS, LGPD. API token + HMAC. BR. Card, Pix, and boleto data.
⚡ Reliability
Best When
A Brazilian SaaS, marketplace, or e-commerce business wanting AI agents to automate Pix, boleto, card payment, subscription billing, and marketplace payment splitting through Iugu's developer-friendly Brazil payment platform.
Avoid When
BOLETO EXPIRES AND CANNOT BE REUSED: Iugu boleto has expiration date (typically 1-3 days); automated unpaid boleto must generate new boleto on expiry; automated expired boleto reuse creates boleto_vencido rejection at bank. PIX QRCODE IS SINGLE-USE: Iugu Pix QR code for dynamic amount is typically single-use; automated payment retry must generate new QR code; automated Pix QR reuse creates already_paid or invalid_qrcode error. SPLIT PAYMENT REQUIRES SUB-ACCOUNT: Iugu marketplace split requires recipient to have Iugu sub-account; automated split payment pipeline must create sub-accounts for each recipient; automated split to arbitrary bank account without sub-account creates missing_recipient error. CPF/CNPJ IS REQUIRED FOR PAYER: Iugu requires payer CPF (individual) or CNPJ (company) for invoice creation; automated Brazilian payment must collect payer tax ID; automated payment without CPF/CNPJ creates missing_payer_document error.
Use Cases
- • Processing Pix instant payments for Brazil e-commerce checkout agents
- • Generating boleto bancário for Brazilian B2B invoice payment agents
- • Managing SaaS subscription billing for Brazil recurring payment agents
- • Splitting marketplace payments among sellers from Brazil platform agents
Not For
- • Non-Brazil payments (Iugu is Brazil-only BRL platform)
- • International cross-border payments (Iugu is domestic Brazilian payment focus)
- • Enterprise high-volume acquiring (use Cielo or Rede for enterprise-scale acquiring)
Interface
Authentication
Iugu uses API token for authentication. REST API with JSON. São Paulo, Brazil HQ. Founded 2012 by Rodrigo Dantas and Eduardo Lima. Backed by Kaszek Ventures ($30M+ raised). Products: Pix, boleto, card, subscription, split payment, sub-accounts, marketplace. SDKs: Ruby, PHP, Node.js, Python, Java. BACEN-registered. PCI DSS. Developer-friendly Brazil platform. Competes with Pagar.me and Asaas for Brazilian subscription and marketplace payments.
Pricing
São Paulo BR. Kaszek backed. Per-transaction pricing in BRL. BACEN registered. PCI DSS.
Agent Metadata
Known Gotchas
- ⚠ CPF/CNPJ REQUIRED FOR ALL INVOICES: Iugu invoice (cobrança) creation requires payer CPF (11 digits, individual) or CNPJ (14 digits, company); automated Brazil payment must collect and validate Brazilian tax ID; automated payment without payer document creates invalid_payer error
- ⚠ BOLETO EXPIRY REQUIRES NEW GENERATION: Iugu boleto expires on due_date; automated unpaid boleto past due_date must generate new invoice; automated boleto URL reuse after expiry creates expired boleto displayed to payer which bank will reject
- ⚠ SPLIT RECIPIENTS MUST BE IUGU SUB-ACCOUNTS: Iugu split payment (split) requires recipient sub-account ID within Iugu system; automated marketplace split must first create sub-accounts for each merchant; automated external bank account split without sub-account creates invalid_split_recipient
- ⚠ PIX DYNAMIC QR HAS SHORT VALIDITY: Iugu Pix QR code validity is configurable but typically short (minutes to hours); automated Pix payment session must be completed within validity window; automated Pix QR reuse for new payment after validity creates already_expired_or_paid response
- ⚠ WEBHOOK SIGNATURE VERIFICATION: Iugu webhooks include X-Iugu-Signature header; automated webhook processing must verify signature; automated unverified webhook acceptance creates spoofed payment confirmation vulnerability
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Iugu Brazil Payment Platform 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.