PagSeguro Brazil Payment Gateway API
PagSeguro Brazil payment gateway REST API for Brazilian merchants to accept PIX, Boleto, credit/debit cards, and digital wallets through Brazil's largest independent payment processor with 7M+ active sellers and full Brazilian payment ecosystem integration. 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 and debit card processing for Brazil card payment automation, retrieve payment status and notification for Brazil order confirmation automation, manage subscription and recurring payment for Brazil subscription automation, handle refund and dispute processing for Brazil order management automation, access split payment for Brazil marketplace automation, retrieve transaction reporting for Brazil financial reconciliation automation, manage fraud protection and score for Brazil payment security automation, and integrate PagSeguro with Brazilian e-commerce, marketplace, and fintech platforms for end-to-end Brazil payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Brazil payments. PCI-DSS, BACEN. Token auth. BR. PIX and payment data.
⚡ Reliability
Best When
A Brazilian merchant or marketplace wanting AI agents to automate PIX, Boleto, and card payment acceptance through PagSeguro's comprehensive Brazilian payment ecosystem covering 7M+ sellers.
Avoid When
BACEN PIX REGULATORY COMPLIANCE: PIX instant payments are regulated by Brazilian Central Bank (BACEN); automated PIX operations must comply with BACEN PIX rules (transaction limits, QR code standards); automated PIX without BACEN compliance creates instant payment rejection. BOLETO EXPIRY DATE MANAGEMENT: Boleto Bancário has configurable expiry dates; automated checkout must set appropriate expiry; automated long-expiry boleto for high-inventory-risk products creates fulfillment commitment before payment; automated short-expiry boleto creates customer payment difficulty on slow payment. PAYMENT NOTIFICATION vs STATUS POLLING: PagSeguro uses notification (IPN) and status polling for payment confirmation; automated order fulfillment must validate notification via PagSeguro status API; automated fulfillment on notification without validation creates spoofed payment acceptance. PIX KEY REGISTRATION: PIX payments to PagSeguro merchant require registered PIX key (CPF, CNPJ, email, phone, or random key); automated PIX receipt requires pre-configured PIX key in PagSeguro account; automated PIX without configured key creates PIX routing failure.
Use Cases
- • Accepting PIX instant payments from Brazil e-commerce checkout agents
- • Generating Boleto Bancário from Brazil bank slip payment agents
- • Processing card payments from Brazil merchant payment agents
- • Managing marketplace split payments from Brazil platform agents
Not For
- • International payments outside Brazil (use Ebanx or MercadoPago for broader LatAm)
- • Enterprise-scale Brazil payments (use Cielo or Rede for enterprise acquiring)
- • Global payment processing (use Stripe or Adyen for international markets)
Interface
Authentication
PagSeguro uses email, token, and OAuth for API authentication. REST API with XML/JSON. São Paulo, Brazil HQ. Founded 2006 as UOL subsidiary. Publicly traded (PAGS) on NYSE since 2018. Products: PIX, Boleto, card processing, PagBank digital account, POS (Moderninha), split payments. SDKs: PHP, Java, Python, .NET, Node.js, Ruby. PCI DSS. BACEN regulated. 7M+ active sellers. Competes with MercadoPago and Cielo for Brazil payments.
Pricing
São Paulo BR. NYSE-listed (PAGS). Per-transaction fees in BRL. BACEN regulated.
Agent Metadata
Known Gotchas
- ⚠ XML AND JSON DUAL API VERSIONS: PagSeguro has older XML-based API and newer JSON REST API; automated integration should use newer JSON API (Connect); automated legacy XML API use creates deprecated format warnings and reduced feature support
- ⚠ NOTIFICATION TOKEN vs PAYMENT STATUS POLLING: PagSeguro IPN notification requires polling status API for confirmation; automated fulfillment must call transaction status API using notification code; automated fulfillment on raw IPN without status validation creates spoofed payment vulnerability
- ⚠ BOLETO BARCODE vs QR CODE FORMAT: PagSeguro generates both barcode and QR code for Boleto; automated Boleto display must present both barcode number and QR code; automated barcode-only display creates UX friction for mobile payers who use QR code scanning
- ⚠ PIX EXPIRY WINDOW CONFIGURATION: PagSeguro PIX payment requests have configurable expiry; automated PIX checkout must set expiry appropriate for payment context; automated long-expiry PIX QR code creates payment attribution complexity if customer pays after order timeout
- ⚠ SPLIT PAYMENT PERCENTAGES vs FIXED AMOUNTS: PagSeguro split supports both percentage and fixed amount splits; automated marketplace must choose split type based on business logic; automated incorrect split type creates wrong amount distribution for fixed-price marketplace scenarios
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for PagSeguro Brazil Payment Gateway 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.