EfíPay (GerenciaNet) Brazil Payment API
EfíPay (formerly GerenciaNet) Brazil payment platform REST API for developers and businesses to accept Pix (including Pix Cobrança, Pix Direto, and Pix via Open Finance), boleto bancário, and credit card payments with a particularly strong Pix developer experience and comprehensive Pix API (including the official BACEN Pix API standard), making it the reference implementation for Brazilian Pix integration. Enables AI agents to manage Pix charge creation for Brazil instant payment automation, handle Pix via Open Finance for Brazilian open banking payment automation, access boleto bancário generation for Brazil bank slip billing automation, retrieve Pix payment status for Brazil instant transfer confirmation automation, manage Pix webhook for Brazil payment notification automation, handle card payment for Brazil e-commerce checkout automation, access subscription and recurring charge for Brazil billing automation, retrieve Pix report for Brazil payment analytics automation, manage split Pix for Brazil marketplace payment automation, and integrate EfíPay with Brazilian developer, SMB, and fintech platforms for end-to-end Brazil Pix and payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Brazil Pix API. BACEN, PCI DSS. OAuth2 + mTLS. BR. Pix and payment data.
⚡ Reliability
Best When
A Brazilian developer or fintech wanting AI agents to automate Pix payments using the official BACEN Pix API specification through EfíPay's reference-quality Pix implementation and developer-friendly Brazil payment platform.
Avoid When
BACEN PIX API USES MTLS: EfíPay Pix API (BACEN standard) requires mutual TLS (client certificate) in addition to OAuth for authentication; automated Pix integration must configure mTLS client certificate; automated OAuth-only Pix request without mTLS creates TLS handshake failure. PIX WEBHOOK REQUIRES PUBLIC HTTPS URL: EfíPay Pix webhook delivery requires HTTPS URL with valid certificate; automated Pix payment notification must register public HTTPS webhook; automated localhost or HTTP webhook URL creates webhook registration failure. PIX COPIA E COLA vs QR CODE: EfíPay Pix returns both QR code image and Copia e Cola (copy-paste) text; automated checkout must present both formats; automated QR-only presentation creates accessibility issue for users preferring text code. BOLETO AND PIX HAVE DIFFERENT EXPIRY MODELS: EfíPay boleto uses calendar due date while Pix uses calendar expiry (expiresIn seconds); automated unified expiry handling must use format-appropriate field; automated same expiry parameter for both creates wrong expiry type error.
Use Cases
- • Implementing Pix Cobrança (Pix invoice) for Brazil instant payment checkout agents
- • Using official BACEN Pix API standard via EfíPay for Brazil fintech integration agents
- • Generating boleto for Brazilian B2B invoice payment automation agents
- • Processing Open Finance Pix payments from Brazilian open banking checkout agents
Not For
- • International payments (EfíPay is Brazil-only BRL platform)
- • High-volume enterprise card acquiring (use Cielo or Stone for enterprise card scale)
- • Non-developer use cases (EfíPay is developer-first and requires technical integration)
Interface
Authentication
EfíPay uses OAuth 2.0 + mTLS for Pix API (BACEN standard) and OAuth 2.0 only for non-Pix APIs. REST API with JSON. Uberlândia, Minas Gerais, Brazil HQ. Founded 2007 as GerenciaNet; rebranded EfíPay 2022. Part of Efi Bank. Products: Pix (Cobrança, Direto, Open Finance), boleto, card, subscription, split. SDKs: PHP, Node.js, Python, Go, Java. BACEN-regulated. PCI DSS. LGPD. Developer-first Brazil platform. Known for best-in-class Pix documentation. Competes with Asaas and Iugu for Brazilian developer payment market.
Pricing
Uberlândia MG BR. Efi Bank subsidiary. Per-transaction pricing in BRL. BACEN regulated. Free Pix tier.
Agent Metadata
Known Gotchas
- ⚠ PIX API REQUIRES MTLS CLIENT CERTIFICATE: EfíPay Pix (BACEN standard API) requires mTLS client certificate in addition to OAuth; automated Pix must configure certificate in HTTP client; automated OAuth-only client for Pix creates TLS handshake failure at connection level
- ⚠ PIX WEBHOOK MUST BE REGISTERED AND HTTPS: EfíPay Pix payment notification requires explicit webhook registration via PUT /v2/webhook/{chave}; automated Pix system must register webhook before any payment; automated Pix without webhook registration creates missed payment notifications with no fallback
- ⚠ TXID IS MERCHANT-GENERATED IDEMPOTENCY KEY: EfíPay Pix txid is generated by merchant (UUID format); automated Pix creation must generate unique txid; automated duplicate txid creates conflict error; automated consistent txid enables idempotent retry
- ⚠ PIX STATUS IS ATIVA/CONCLUIDA/REMOVIDA: EfíPay Pix charge status uses specific enum (ativa=pending, concluída=paid, removida=cancelled); automated webhook handler must map EfíPay status enum not generic paid/unpaid; automated generic status mapping creates wrong fulfillment trigger
- ⚠ OPEN FINANCE PIX REQUIRES DIFFERENT FLOW: EfíPay Pix via Open Finance (payment initiation) is a separate product with different endpoint and consent flow; automated Open Finance Pix must use /v2/gn/open-finance endpoints not standard Pix; automated mixing standard and Open Finance Pix endpoints creates endpoint_not_found
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for EfíPay (GerenciaNet) Brazil Payment 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.