Transbank Chile Payment API (Webpay)
Transbank Chile Webpay REST API for Chilean merchants to accept credit cards, debit cards, and prepaid cards through Chile's dominant card payment network covering Visa, Mastercard, CMR, and RedCompra for online e-commerce, subscription billing, and in-store payment integration. Enables AI agents to manage Webpay Plus transaction initiation for Chile card payment automation, handle Webpay redirect flow for card checkout automation, access transaction status confirmation for Chile payment verification automation, retrieve refund and annulment for Chile order management automation, manage Oneclick Mall subscription for Chile recurring card billing automation, handle deferred capture transactions for Chile authorization management automation, access transaction reporting for Chile payment analytics automation, retrieve multi-commerce (mall) payment orchestration for Chile platform automation, manage installment plan for Chile cuotas payment automation, and integrate Transbank with Chilean e-commerce, government, and enterprise platforms for end-to-end Chile card payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Chile card payments. PCI-DSS. Commerce Code + API Key. CL. Card payment data.
⚡ Reliability
Best When
A Chilean merchant or platform wanting AI agents to automate credit and debit card payment acceptance, subscription billing, and multi-commerce payment orchestration through Transbank's Webpay — Chile's dominant card payment network.
Avoid When
WEBPAY REDIRECT FLOW REQUIRES USER BROWSER: Webpay Plus uses redirect flow (merchant → Transbank hosted page → merchant); automated payment requires redirecting user browser to Transbank; automated server-side payment without browser redirect creates no payment interface for cardholder. TRANSACTION MUST BE CONFIRMED WITHIN TIME LIMIT: Webpay transactions must be confirmed (commitTransaction) within 30 seconds of customer completing form; automated confirmation must poll status and commit quickly; automated delayed commit creates transaction timeout and payment voided. COMMERCE CODE IS ENVIRONMENT-SPECIFIC: Transbank uses different Commerce Codes for integration (testing) vs production environments; automated configuration must use correct commerce code per environment; automated production commerce code in integration environment creates invalid commerce error. ANNULMENT vs REFUND DISTINCTION: Transbank has annulment (same-day void) vs refund (post-settlement reversal) with different API calls; automated reversal must choose correct operation based on settlement status; automated annulment after settlement creates operation not permitted error.
Use Cases
- • Processing Chilean card payments via Webpay from Chile e-commerce checkout agents
- • Managing Webpay Oneclick subscriptions from Chile recurring billing agents
- • Confirming card authorization from Chile payment verification agents
- • Processing refunds and annulments from Chile order management agents
Not For
- • Non-Chile card payments (Transbank is Chile-only acquirer)
- • Mobile wallet payments in Chile (Transbank is card-focused; use Mercado Pago for wallet)
- • Cross-border Latin America payments (use EBANX or MercadoPago for multi-country LatAm)
Interface
Authentication
Transbank uses Commerce Code + API Key for authentication. REST API with JSON. Santiago, Chile HQ. Founded 1989 by Chilean banks (Santander, BCI, Banco de Chile, BancoEstado). Products: Webpay Plus, Webpay Oneclick Mall, deferred capture, POS, installments. SDKs: PHP, Node.js, Python, Java, .NET, Ruby, Go. PCI DSS. SBIF regulated. Chile's dominant payment network. No webhooks — polling-based confirmation.
Pricing
Santiago CL. Bank consortium owned. Per-transaction merchant discount rate. Integration sandbox free. Production via bank agreement.
Agent Metadata
Known Gotchas
- ⚠ NO WEBHOOKS — POLLING REQUIRED: Transbank Webpay does not use webhooks; automated payment confirmation requires polling getTransactionStatus or the transaction is confirmed via return URL redirect; automated webhook-based confirmation creates no confirmation receipt
- ⚠ COMMIT WITHIN 30 SECONDS: Webpay transaction commit (confirmTransaction) must occur within 30 seconds of customer completing payment form; automated confirmation workflow must commit immediately upon return redirect; automated delayed commit creates transaction voided
- ⚠ SEPARATE ANNULMENT AND REFUND ENDPOINTS: Transbank uses createRefund for same-day annulments and post-settlement refunds with different behavior; automated reversal must check settlement status before choosing operation; automated annulment after nightly settlement creates 'transaction already settled' error
- ⚠ INTEGRATION COMMERCE CODES ARE FIXED TEST VALUES: Transbank integration environment uses hardcoded test commerce codes (597055555532 etc.); automated testing must use Transbank's published integration commerce codes; automated random commerce code in integration creates unauthorized merchant error
- ⚠ CUOTAS (INSTALLMENTS) REQUIRE EXPLICIT ZERO FOR NO INSTALLMENTS: Transbank cuotas (installment) parameter requires explicit '0' for no installments; automated single-payment transaction must pass cuotas=0; automated omitted cuotas parameter creates default installment applied
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Transbank Chile Payment API (Webpay).
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.