Culqi Peru Payment Gateway API
Culqi Peru payment gateway REST API for Peruvian businesses and developers to accept Visa, Mastercard, American Express, Diners Club, and digital wallets in Peruvian Sol (PEN) with developer-friendly API design and SBS-regulated compliance for modern Peru e-commerce. Enables AI agents to manage card payment charging for Peru e-commerce automation, handle card tokenization for PCI-compliant Peru checkout automation, access subscription and recurring payment for Peru subscription automation, retrieve payment status for Peru order confirmation automation, manage refund processing for Peru order management automation, handle webhook events for Peru payment lifecycle automation, access customer and card vault management for Peru recurring automation, retrieve transaction reporting for Peru financial reconciliation automation, manage anti-fraud protection for Peru payment security automation, and integrate Culqi with Peruvian e-commerce, fintech, and SaaS platforms for end-to-end Peru developer payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Peru payments. PCI-DSS. Public/Secret key. PE. Card data.
⚡ Reliability
Best When
A Peruvian startup or developer wanting AI agents to automate card payment acceptance, tokenization, and subscription billing through Culqi's developer-friendly Peru-native payment gateway.
Avoid When
SBS REGULATORY COMPLIANCE: Culqi operates under Superintendencia de Banca, Seguros y AFP (SBS) of Peru; automated payment operations must comply with SBS fintech regulations; automated payment without merchant SBS compliance creates regulatory risk. CHECKOUT TOKENIZATION BEFORE CHARGE: Culqi requires card tokenization via Culqi.js or hosted checkout before server-side charge; automated charge must use Culqi-generated token; automated direct card number charge without tokenization creates PCI scope expansion. PEN CURRENCY PRIMARILY: Culqi transactions are primarily in Peruvian Sol (PEN); automated pricing in foreign currency requires explicit currency parameter; automated USD amount without PEN conversion creates currency mismatch. API KEY SCOPING TEST vs LIVE: Culqi sandbox uses different API keys from live environment; automated environment management must maintain separate key sets; automated live key use in testing creates real charges from test scenarios.
Use Cases
- • Accepting Visa/Mastercard payments from Peru developer e-commerce agents
- • Creating card subscriptions from Peru SaaS recurring billing agents
- • Tokenizing cards for PCI-compliant from Peru recurring payment agents
- • Processing refunds from Peru order management automation agents
Not For
- • Pan-LatAm payments beyond Peru (use Kushki or EBANX for multi-country LatAm)
- • Enterprise Peru payments at scale (use Niubiz/VisaNet for enterprise acquiring)
- • Cash payments in Peru (Culqi is card-focused; use PagoEfectivo for cash)
Interface
Authentication
Culqi uses public key (for tokenization) and secret key (for API) authentication. REST API with JSON. Lima, Peru HQ. Founded 2013 by Amparo Nalvarte and Danilo Cieza. Backed by Y Combinator, Credicorp, IFC. Products: Card processing, tokenization, subscriptions, refunds, anti-fraud. SDKs: PHP, Python, Node.js, Ruby, Java, .NET. PCI DSS. SBS regulated. Serves 5,000+ Peruvian merchants. Competes with Niubiz and MercadoPago for Peru payments.
Pricing
Lima PE. YC/Credicorp backed. Per-transaction fees in PEN. Peruvian RUC (tax ID) required.
Agent Metadata
Known Gotchas
- ⚠ TOKEN-THEN-CHARGE FLOW MANDATORY: Culqi requires Culqi.js tokenization before server-side charge; automated checkout must first obtain token via browser, then charge via server; automated server-side direct card charge without prior tokenization creates unsupported payment method error
- ⚠ CHARGE AMOUNT IN CENTAVOS: Culqi amounts are in centavos (smallest PEN unit, 1 PEN = 100 centavos); automated charge must multiply PEN amount by 100; automated decimal PEN amount creates amount mismatch (100x smaller than intended)
- ⚠ SUBSCRIPTION PLAN CREATION BEFORE SUBSCRIPTION: Culqi subscription requires existing Plan object; automated recurring billing must create Plan first, then Subscription; automated direct subscription creation without Plan creates plan not found error
- ⚠ EMAIL REQUIRED FOR CUSTOMER: Culqi Customer and Charge require valid email address; automated payment must collect customer email; automated payment without email creates validation error for required field
- ⚠ WEBHOOK SECRET FOR PAYLOAD VERIFICATION: Culqi webhooks include HMAC signature for authenticity; automated webhook endpoint must verify signature; automated unverified webhook creates spoofed charge event vulnerability
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Culqi Peru 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.