Kushki Latin America Payments API
Kushki Latin America payment gateway REST API for businesses to accept cards, bank transfers, cash, and digital wallets across Colombia, Mexico, Ecuador, Peru, Chile, and Guatemala with unified LatAm payment infrastructure designed for developers and enterprise merchants. Enables AI agents to manage card payment processing for LatAm e-commerce automation, handle bank transfer and ACH for LatAm bank payment automation, access cash payment via OXXO and convenience stores for LatAm offline payment automation, retrieve payment token creation for PCI-compliant card automation, manage subscription and recurring payment for LatAm subscription automation, handle refund processing for LatAm order management automation, access split payment for LatAm marketplace automation, retrieve fraud detection and score for LatAm payment security automation, manage multi-currency payment for LatAm cross-border automation, and integrate Kushki with LatAm e-commerce, fintech, and enterprise platforms for end-to-end LatAm payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
LatAm payments. PCI-DSS. Public/Private keys. EC. Card payment data.
⚡ Reliability
Best When
A merchant wanting to expand across Colombia, Mexico, Ecuador, and Peru wanting AI agents to automate local card, bank transfer, and cash payment acceptance through Kushki's developer-friendly pan-LatAm payment gateway.
Avoid When
COUNTRY-SPECIFIC MERCHANT REGISTRATION: Kushki requires merchant registration and legal entity per operating country; automated multi-country expansion must complete per-country onboarding; automated single-registration assumption for all LatAm countries creates unauthorized payment in unregistered countries. TOKENIZATION REQUIRED FOR PCI COMPLIANCE: Kushki requires card tokenization via hosted fields or JavaScript library; automated server-side card charge without tokenization creates PCI DSS full scope; automated direct card API use without token creates non-compliant payment processing. CASH PAYMENT ASYNC CONFIRMATION: Cash payments (OXXO, Efecty) are paid offline; automated order fulfillment must wait for offline payment confirmation (typically hours to days); automated immediate fulfillment after cash order creation creates orders with unconfirmed payment. COUNTRY-SPECIFIC FRAUD RULES: Kushki fraud detection rules vary by country; automated payment with international card for local product may trigger country-specific fraud flag; automated fraud override without country context creates compliance risk.
Use Cases
- • Accepting multi-country LatAm card payments from regional commerce agents
- • Processing Colombia PSE bank transfers from Colombian payment agents
- • Handling Mexico OXXO cash from offline LatAm payment agents
- • Managing Ecuador and Peru local payments from pan-LatAm merchant agents
Not For
- • Brazil payments (Kushki has limited Brazil coverage; use MercadoPago or EBANX for Brazil)
- • Global payment outside LatAm (use Stripe or Adyen for international)
- • Consumer P2P transfers (Kushki is merchant-focused)
Interface
Authentication
Kushki uses Public Key (for tokenization) and Private Key (for API) authentication. REST API with JSON. Quito, Ecuador HQ. Founded 2017 by Aron Schwarzkopf. Backed by SoftBank Latin America Fund, Tiger Global, Kaszek ($86M raised). Products: Card processing, tokenization, bank transfers, cash (OXXO, Efecty), subscriptions, split payments. SDKs: PHP, Java, Python, Node.js, .NET. PCI DSS. Operations: Colombia, Mexico, Ecuador, Peru, Chile, Guatemala. Competes with EBANX and PayU for LatAm payments.
Pricing
Quito EC. SoftBank/Tiger backed. Per-transaction fees in local currency. Per-country merchant agreements.
Agent Metadata
Known Gotchas
- ⚠ PUBLIC KEY vs PRIVATE KEY USAGE: Kushki uses public key for client-side tokenization and private key for server-side API; automated integration must use correct key per context; automated server-side private key exposure to browser creates credential security vulnerability
- ⚠ TOKEN SINGLE-USE AFTER CARD TOKENIZATION: Kushki payment tokens are single-use; automated retry after failed payment must re-tokenize card; automated same token reuse for retry creates token already used error
- ⚠ COUNTRY CODE REQUIRED FOR MULTI-COUNTRY: Kushki API routes payment based on country code; automated multi-country checkout must include customer country; automated missing country code creates incorrect payment routing to default country configuration
- ⚠ 3DS REQUIREMENT FOR SOME COUNTRIES: Colombia and Mexico require 3DS for e-commerce card payments; automated checkout must implement 3DS redirect for required countries; automated server-side card charge without 3DS creates declined transaction for 3DS-required markets
- ⚠ CURRENCY MAPPING TO COUNTRY: Kushki transactions must use correct currency per country (COP for Colombia, MXN for Mexico, USD for Ecuador); automated payment must map country to correct currency; automated wrong currency for country creates invalid currency error
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Kushki Latin America Payments 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.