Pagar.me Brazil Developer Payment API
Pagar.me Brazil developer payment REST API for startups and technology companies to accept PIX, Boleto, credit/debit cards, and digital wallets with developer-first API design, transparent pricing, and Stone fintech group infrastructure for modern Brazil e-commerce and fintech integration. Enables AI agents to manage PIX payment creation for Brazil instant payment automation, handle Boleto Bancário generation for Brazil bank slip automation, access credit card processing with split and installments for Brazil card commerce automation, retrieve payment status and webhook for Brazil order confirmation automation, manage subscription and recurring billing for Brazil subscription automation, handle refund and chargeback for Brazil dispute management automation, access marketplace split payment for Brazil platform automation, retrieve anti-fraud scoring for Brazil payment security automation, manage customer and card vault for Brazil tokenization automation, and integrate Pagar.me with Brazilian startups, SaaS, and marketplace platforms for end-to-end developer Brazil payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Brazil payments. PCI-DSS, BACEN. Secret/Public keys. BR. PIX and payment data.
⚡ Reliability
Best When
A Brazilian startup, SaaS, or marketplace wanting AI agents to automate PIX, Boleto, and card payment acceptance with marketplace split payments through Pagar.me's developer-friendly Brazil payment API backed by Stone fintech group.
Avoid When
BACEN PIX COMPLIANCE: Pagar.me PIX operations comply with Brazilian Central Bank PIX rules; automated PIX must follow BACEN QR code standards and transaction limits; automated non-standard PIX QR code creates payment routing error. INSTALLMENT CONFIGURATION PER CARD BRAND: Pagar.me installments require configuration per card brand (Visa, Mastercard, Elo); automated installment checkout must configure supported installment counts per brand; automated generic installment creates invalid installment option for some card brands. BOLETO BANK SLIP REGISTRATION: Pagar.me Boleto generates registered boleto (boleto registrado) required by FEBRABAN since 2017; automated Boleto must include payer CPF/CNPJ; automated Boleto without payer tax ID creates unregistered boleto rejection. SPLIT PAYMENT RECIPIENT APPROVAL: Pagar.me marketplace split requires recipient (recebedor) registration and approval; automated split payment requires pre-approved recipient account; automated split to unapproved recipient creates recipient not found error.
Use Cases
- • Accepting PIX instant payments from Brazil startup checkout agents
- • Processing Boleto with expiry management from Brazil bank payment agents
- • Managing marketplace split payments from Brazil two-sided platform agents
- • Setting up PIX and card subscriptions from Brazil recurring billing agents
Not For
- • Enterprise Brazil payments at highest volume (use Cielo or Rede for enterprise acquiring)
- • Pan-LatAm payments beyond Brazil (use EBANX or MercadoPago for LatAm)
- • Physical POS (Pagar.me is online-focused; use Stone POS for physical retail)
Interface
Authentication
Pagar.me uses Secret Key (sk_) and Public Key (pk_) for API authentication. REST API with JSON. São Paulo, Brazil HQ. Founded 2013 by Pedro Franceschi and Henrique Dubugras. Acquired by Stone in 2016. Products: PIX, Boleto, card processing, installments, subscriptions, marketplace split, anti-fraud. SDKs: PHP, Python, Node.js, Ruby, Java, .NET, Go. PCI DSS. BACEN regulated. Serves Brazilian startups and SMBs. Competes with PagSeguro and MercadoPago for developer-focused Brazil payments.
Pricing
São Paulo BR. Stone subsidiary. Per-transaction fees in BRL. Transparent pricing. Brazilian CPF/CNPJ required.
Agent Metadata
Known Gotchas
- ⚠ SECRET KEY vs PUBLIC KEY SEPARATION: Pagar.me uses sk_ (server-side) and pk_ (client-side browser) keys; automated server-side API must use sk_ key only; automated pk_ key server-side use creates permission denied for charge operations; automated sk_ key in browser creates credential exposure
- ⚠ IDEMPOTENCY KEY FOR CHARGE RETRY: Pagar.me supports idempotency key header for charge creation; automated payment retry must use same idempotency key; automated retry without idempotency key creates duplicate charge if original request succeeded but response was lost
- ⚠ BOLETO CPF/CNPJ PAYER REQUIREMENT: Pagar.me registered Boleto requires payer CPF or CNPJ; automated Boleto must collect Brazilian tax ID before generation; automated Boleto without payer document creates FEBRABAN registration failure
- ⚠ PIX QR CODE STATIC vs DYNAMIC: Pagar.me supports both static QR (reusable) and dynamic QR (per-transaction, recommended); automated single-use PIX collection must use dynamic QR; automated static QR for individual payment creates QR reuse allowing repeated payment against same QR
- ⚠ WEBHOOK HMAC-SHA256 VERIFICATION: Pagar.me webhooks include X-Hub-Signature header; automated webhook processing must verify HMAC-SHA256 signature; automated unverified webhook processing creates spoofed payment acceptance vulnerability
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Pagar.me Brazil Developer 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.