Getnet Brazil Payment Acquirer API
Getnet Brazil payment acquirer REST API (Santander subsidiary) for Brazilian merchants to accept credit card, debit card, Pix, and voucher payments with card tokenization, installment payment (parcelamento), 3DS authentication, and anti-fraud integration through Santander's Brazilian acquiring platform serving large and mid-size merchants. Enables AI agents to manage credit and debit card authorization for Brazil e-commerce 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 3DS2 authentication for Brazil card security automation, access anti-fraud scoring for Brazil fraud prevention automation, retrieve chargeback management for Brazil dispute automation, manage payment capture and cancellation for Brazil transaction control automation, and integrate Getnet with Brazilian retail, e-commerce, and enterprise platforms for end-to-end Brazil card payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Brazil acquiring. Santander, BACEN, PCI DSS L1. OAuth2. BR. Card and payment data.
⚡ Reliability
Best When
A mid-to-large Brazilian merchant wanting AI agents to automate card and Pix payment acceptance through Getnet's Santander-backed Brazilian acquirer API with enterprise-grade features including tokenization and anti-fraud.
Avoid When
OAUTH TOKEN ROTATION REQUIRED: Getnet OAuth token expires and must be refreshed; automated long-running integration must handle token refresh; automated static token without refresh creates expired_token after TTL. SELLER ID REQUIRED FOR ALL REQUESTS: Getnet requires seller_id (merchant identifier) in all API requests; automated client must include seller_id in every call; automated requests without seller_id creates unauthorized_seller error. CAPTURE IS EXPLICIT FOR PRE-AUTH: Getnet pre-authorization requires explicit capture call; automated checkout with pre-auth must call capture separately; automated no-capture workflow creates authorized funds that automatically reverse. PIX REQUIRES REGISTERED PIXKEY: Getnet Pix payment requires merchant's registered Pix key (CNPJ key or random key); automated Pix setup must register merchant Pix key first; automated Pix without registered key creates pix_key_not_found error.
Use Cases
- • Processing card payments for Brazilian enterprise e-commerce checkout agents
- • Accepting Pix instant payments for Santander merchant checkout agents
- • Tokenizing cards for Brazil subscription recurring billing agents
- • Handling installment payments for Brazil parcelamento retail checkout agents
Not For
- • Non-Brazil payments (Getnet is Brazil-only BRL acquirer)
- • Small merchant acquiring (Getnet focuses on mid-to-large merchants; use Stone or Asaas for SMB)
- • International acquiring beyond Brazil (Getnet is Brazilian market only)
Interface
Authentication
Getnet uses OAuth 2.0 for API authentication. REST API with JSON. São Paulo, Brazil HQ. Santander Brasil subsidiary (acquired 2014). Products: Card acquiring (credit/debit), Pix, voucher (VR/Ticket), tokenization, 3DS2, anti-fraud, installments, POS terminals. SDKs: PHP, Java, .NET, Node.js. BACEN-regulated. PCI DSS Level 1. LGPD. Serves mid-to-large Brazilian merchants. Competes with Cielo and Rede for enterprise Brazilian acquiring.
Pricing
São Paulo BR. Santander Brasil subsidiary. Negotiated MDR in BRL. BACEN regulated. PCI DSS L1.
Agent Metadata
Known Gotchas
- ⚠ SELLER_ID IN EVERY REQUEST HEADER: Getnet requires seller_id in Authorization header or request body for all calls; automated client must include seller_id; automated requests without seller_id creates 401 unauthorized response
- ⚠ TOKEN EXPIRY REQUIRES PROACTIVE REFRESH: Getnet OAuth access_token expires (typically 1 hour); automated integration must refresh before expiry; automated token-on-demand without expiry tracking creates mid-workflow expired_token and transaction failure
- ⚠ TWO-PHASE CAPTURE DEFAULT: Getnet card authorization captures funds but requires explicit /capture call for settlement; automated payment must explicitly capture; automated assume-and-forget creates authorized uncaptured transaction that auto-reverses
- ⚠ VOUCHER (VALE-REFEIÇÃO) REQUIRES SEPARATE FLOW: Getnet voucher (VR Refeição, Ticket) has different authorization flow from standard card; automated multi-payment-method checkout must handle voucher-specific endpoints; automated standard card flow for voucher creates wrong tender type error
- ⚠ PIX KEY REGISTRATION PRECEDES PIX API USE: Getnet Pix requires merchant to register at least one Pix key via dashboard before API Pix calls work; automated Pix integration must verify key registration; automated Pix API calls without registered key creates merchant_pix_key_not_configured
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Getnet 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.