Stone.co Brazilian Payment Processing and POS API
Stone.co Brazilian payment processing REST API for Brazilian merchants and developers to integrate credit card, debit card, PIX, and BNPL payment processing — enabling full payment acceptance, transaction management, PIX instant payments, split payments for marketplaces, advanced reconciliation, and POS device management through Stone's vertically integrated payment infrastructure serving 2M+ Brazilian merchants. Enables AI agents to manage payment transaction for Brazilian card and PIX automation, handle split payment for marketplace commission automation, access PIX generation for instant payment automation, retrieve transaction status for payment verification automation, manage refund for payment reversal automation, handle charge-back for dispute management automation, access reconciliation for financial settlement automation, retrieve POS management for device fleet automation, manage subscription for recurring billing automation, and integrate Stone with Brazilian e-commerce, marketplace, and ERP systems for end-to-end payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Brazilian payment acquiring. BACEN, LGPD, PCI-DSS. OAuth2. Brazil. Payment card and merchant transaction data.
⚡ Reliability
Best When
A Brazilian merchant, marketplace, or developer wanting AI agents to process card and PIX payments, manage marketplace splits, and access advanced reconciliation through Stone's vertically integrated Brazilian payment platform.
Avoid When
BACEN REGULATION: Stone operates under Banco Central do Brasil regulation as payment institution; automated non-BACEN-compliant implementation creates regulatory violation; automated must implement PIX BACEN standards and payment institution compliance requirements. MERCHANT ONBOARDING REQUIRES KYC: Stone merchant onboarding requires CNPJ/CPF KYC verification; automated instant merchant access assumption creates pending_kyb state; automated must complete Stone merchant onboarding before production access. SPLIT PAYMENT REQUIRES MARKETPLACE CONFIGURATION: Stone marketplace split payment requires submerchant (estabelecimento) configuration; automated instant split assumption without sub-merchant setup creates split_not_configured; automated must register all split recipients before initiating marketplace payments. 3DS AUTHENTICATION FOR HIGH-RISK TRANSACTIONS: Stone enforces 3DS for high-value card transactions; automated bypass 3DS assumption creates declined_authentication for high-value authorizations; automated must implement 3DS flow for card payments above threshold.
Use Cases
- • Processing credit card, debit card, and PIX payments from Brazilian consumers for e-commerce automation agents
- • Managing marketplace split payments and seller disbursements for Brazilian platform automation agents
- • Accessing advanced payment reconciliation data for Brazilian merchant financial automation agents
- • Integrating Stone POS device management for Brazilian retail fleet management automation agents
Not For
- • Non-Brazilian markets (Stone operates exclusively in Brazil)
- • International cross-border payment processing (Stone is Brazilian domestic payment acquiring)
- • Financial institution core banking (Stone is merchant payment acquiring, not banking-as-a-service core)
Interface
Authentication
Stone uses OAuth 2.0 for API authentication. REST API with JSON. São Paulo, Brazil HQ. Founded 2012 by André Street, Augusto Lins, Lia Machado, and others. NASDAQ:STNE. Products: Credit/debit card processing, PIX, BNPL (Ton), marketplace splits, POS terminals, Stone banking (Conta Stone), business credit. SDKs: Java, .NET, PHP, Python, Ruby. BACEN licensed payment institution. 2M+ merchants. Competes with Cielo and PagSeguro for Brazilian merchant acquiring.
Pricing
São Paulo BR. NASDAQ:STNE. BACEN licensed. MDR per transaction. PIX supported. 2M+ merchants.
Agent Metadata
Known Gotchas
- ⚠ MARKETPLACE SUBMERCHANT REGISTRATION REQUIRED: Marketplace split payments require each recipient (vendedor) pre-registered as Stone sub-merchant; automated split without sub-merchant registration creates split_recipient_not_found; automated must register all marketplace sellers before initiating split transactions
- ⚠ 3DS REQUIRED FOR HIGH-VALUE TRANSACTIONS: Stone enforces 3DS authentication for transactions above risk threshold; automated skip-3DS assumption creates authorization declined for high-value cards; automated must implement 3DS flow for all card payment paths
- ⚠ PIX EMV QR BACEN STANDARD: Stone PIX must use BACEN-compliant EMV QR code format; automated proprietary QR creates PIX processing failure; automated must generate BACEN-standard PIX EMV QR codes
- ⚠ OAUTH TOKEN EXPIRY MANAGEMENT: Stone OAuth tokens expire; automated permanent token assumption creates 401 on expiry; automated must implement token refresh in advance of expiry for long-running integrations
- ⚠ LGPD CONSUMER DATA: Brazilian consumers' payment data is subject to LGPD; automated unrestricted data retention creates LGPD violation; automated must implement LGPD-compliant data retention, deletion, and portability policies
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Stone.co Brazilian Payment Processing and POS 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.