Rede Brazil Payment Acquirer API
Rede Brazil payment acquirer REST API (Itaú Unibanco subsidiary) for Brazilian merchants to accept credit card, debit card, Pix, and digital payments with card tokenization, installment payment (parcelamento), anti-fraud, and real-time settlement through Itaú's Brazilian acquiring platform serving large enterprises and mid-market merchants. Enables AI agents to manage credit and debit card authorization for Brazil enterprise checkout automation, handle Pix payment initiation for Brazil instant payment automation, access card tokenization for Brazil recurring payment automation, retrieve payment status for Brazil transaction confirmation automation, manage installment payment for Brazil parcelamento automation, handle anti-fraud scoring for Brazil fraud prevention automation, access chargeback management for Brazil dispute automation, retrieve settlement reporting for Brazil reconciliation automation, manage payment cancellation for Brazil void automation, and integrate Rede with Brazilian enterprise, retail, and e-commerce platforms for end-to-end Brazil card and digital payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Brazil acquiring. Itaú, BACEN, PCI DSS L1. OAuth2. BR. Card and payment data.
⚡ Reliability
Best When
A large Brazilian enterprise or mid-market merchant wanting AI agents to automate card and Pix payment acceptance through Rede's Itaú-backed Brazilian acquirer API with enterprise-grade stability and bank-grade infrastructure.
Avoid When
ITAU MERCHANT ACCOUNT REQUIRED: Rede acquiring requires Itaú bank merchant account relationship; automated access without Itaú banking relationship creates no acquiring agreement path; automated merchant without Itaú account must establish banking relationship first. TWO-PHASE CAPTURE FOR PRE-AUTHORIZATION: Rede pre-authorization requires explicit capture; automated pre-auth checkout must explicitly capture; automated no-capture assumption creates auto-reversing authorization. TOKEN EXPIRY IN OAUTH: Rede OAuth token has time-limited validity; automated long-running processes must refresh before expiry; automated static token use creates mid-workflow authentication failure. INSTALLMENT RULES VARY BY CARD BIN: Rede installment availability and interest rates depend on card BIN/issuer; automated installment plans must query available plans per card BIN; automated universal installment plan creates invalid plan for some card types.
Use Cases
- • Processing enterprise card payments for Brazilian large merchant checkout agents
- • Accepting Pix instant payments for Itaú merchant checkout agents
- • Tokenizing cards for Brazil subscription billing agents
- • Reconciling settlements from Brazil enterprise payment analytics agents
Not For
- • Non-Brazil payments (Rede is Brazil-only BRL acquirer)
- • Small merchant acquiring (Rede targets mid-to-large merchants; use Stone for SMB)
- • International card acquiring beyond Brazil (Rede is Brazilian market only)
Interface
Authentication
Rede uses OAuth 2.0 for API authentication. REST API with JSON. São Paulo, Brazil HQ. Itaú Unibanco subsidiary (100% owned). Products: Card acquiring (credit/debit), Pix, boleto, tokenization, anti-fraud, installments, POS terminals, e-commerce. SDKs: PHP, Java, .NET, Node.js, Python. BACEN-regulated. PCI DSS Level 1. LGPD. Serves large and mid-market Brazilian merchants. Brazil's second-largest acquirer. Competes with Cielo and Stone for Brazilian card acquiring.
Pricing
São Paulo BR. Itaú Unibanco subsidiary. Negotiated MDR in BRL. BACEN regulated. PCI DSS L1.
Agent Metadata
Known Gotchas
- ⚠ AFFILIATION (MERCHANT AFFILIATION CODE) IS REQUIRED: Rede API requires affiliation number (filiação) in every payment request; automated client must include Rede-assigned affiliation number; automated request without affiliation creates missing_affiliation error
- ⚠ TOKEN EXPIRY REQUIRES REFRESH LOGIC: Rede OAuth token expires; automated integration must implement token refresh (using refresh_token grant); automated access_token-only caching without refresh creates expired_access_token mid-payment workflow
- ⚠ CAPTURE IS SEPARATE FROM AUTHORIZATION: Rede two-phase flow: authorize → capture; automated e-commerce checkout must call capture after authorization; automated authorize-only creates captured authorization that auto-reverses after 5-7 days without explicit capture
- ⚠ PIX QR HAS EXPIRATION TIME: Rede Pix QR code has expiration (configurable, default 30 minutes); automated Pix checkout must track QR expiry; automated expired QR presentation to consumer creates expired_pix_qr error at payment time
- ⚠ REFUND IS TIME-LIMITED: Rede refund (cancelamento) must be within 90 days of original transaction; automated refund must validate transaction age; automated old transaction refund creates outside_refund_window error
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Rede 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.