Izipay Peru Payment Gateway API
Izipay Peru payment gateway REST API (Banco de Crédito del Perú subsidiary) for Peruvian merchants to accept credit card, debit card, Yape, Plin, cash (PagoEfectivo), and digital wallet payments through Peru's bank-backed payment gateway, with tokenization, installment payment (cuotas), 3DS2 authentication, and payment link generation for e-commerce and in-person payment integration. Enables AI agents to manage credit card payment for Peru e-commerce checkout automation, handle Yape and Plin digital wallet payment for Peru mobile checkout automation, access cash payment (PagoEfectivo) for Peru offline payment automation, retrieve payment status for Peru transaction confirmation automation, manage installment payment for Peru cuotas automation, handle 3DS2 authentication for Peru card security automation, access card tokenization for Peru recurring payment automation, retrieve settlement reporting for Peru reconciliation automation, manage refund processing for Peru order management automation, and integrate Izipay with Peruvian e-commerce, retail, and enterprise platforms for end-to-end Peru multi-method payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Peru gateway. SBS, PCI DSS. HMAC. PE. Card and payment data.
⚡ Reliability
Best When
A Peruvian merchant wanting AI agents to automate card, Yape, Plin, and cash payment acceptance through Izipay's BCP-backed Peru gateway with comprehensive local payment method coverage including PagoEfectivo.
Avoid When
HOSTED FORM vs DIRECT API — DIFFERENT PCI SCOPE: Izipay offers hosted payment form (lower PCI scope) and direct API (full PCI scope); automated card integration via direct API requires PCI DSS compliance; automated direct card API without PCI certification creates compliance violation. YAPE/PLIN REQUIRE QR OR DEEP LINK: Izipay Yape/Plin payments use QR code or deep link that consumer opens in their app; automated checkout must present QR/deep link; automated server-side wallet charge without consumer interaction creates no payment. CUOTAS PLAN DEPENDS ON CARD ISSUER: Izipay installment plans depend on card BIN and issuer participation; automated installment must query available plans for card; automated universal cuotas assumption creates cuotas_not_available for non-participating cards. PAGOFECTIVO IS ASYNC: Izipay PagoEfectivo cash payments are paid at agents; automated fulfillment must await cash payment confirmation; automated immediate fulfillment on voucher creation creates unfulfillable premature orders.
Use Cases
- • Accepting card and Yape payments for Peru e-commerce checkout agents
- • Generating PagoEfectivo cash vouchers for Peruvian unbanked payment agents
- • Processing Plin wallet payments from Peru mobile checkout agents
- • Managing installment payments for Peru cuotas retail checkout agents
Not For
- • Non-Peru payments (Izipay is Peru-only gateway)
- • International acquiring beyond Peru (Izipay is Peruvian domestic market)
- • Global enterprise acquiring (use Adyen or Stripe for global operations)
Interface
Authentication
Izipay uses shop username + password (HMAC signed) authentication. REST API with JSON. Lima, Peru HQ. BCP (Banco de Crédito del Perú) subsidiary. Products: Card, Yape, Plin, PagoEfectivo cash, tokenization, installments, 3DS2, payment links, POS. SDKs: JavaScript, PHP, Java. SBS-regulated. PCI DSS. Competes with Niubiz (VisaNet) for Peruvian payment acquiring.
Pricing
Lima PE. BCP subsidiary. Negotiated MDR in PEN. SBS regulated. PCI DSS.
Agent Metadata
Known Gotchas
- ⚠ HMAC SIGNATURE AUTHENTICATION: Izipay uses SHA-256 HMAC signature (not plain API key) combining shop login, password, and request params; automated request must generate HMAC signature; automated plain credentials without HMAC creates invalid_signature error
- ⚠ YAPE PAYMENT IS QR-SCAN FLOW: Izipay Yape payment returns QR code image and deepLink; automated checkout must display QR for consumer to scan in Yape app; automated server-side Yape charge without consumer QR interaction creates no payment
- ⚠ PAGOFECTIVO CASH PAYMENT IS MULTI-DAY: Izipay PagoEfectivo generates voucher for offline cash payment at agent network; automated fulfillment must await cash_confirmed event which comes 1-3 days after voucher generation; automated immediate fulfillment on voucher creation creates unconfirmed order fulfillment
- ⚠ ORDER NUMBER IS MERCHANT-GENERATED UNIQUE ID: Izipay orderNumber is merchant-generated unique transaction identifier; automated payment must generate unique orderNumber; automated duplicate orderNumber creates duplicate_transaction error
- ⚠ CUOTAS WITHOUT INTEREST VS WITH INTEREST: Izipay installments come in con interés (with interest, issuer charges consumer) and sin interés (no interest, merchant absorbs); automated cuotas offer must configure correct type; automated wrong cuotas type creates unexpected consumer charge or merchant fee
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Izipay 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.