Yape Peruvian Digital Wallet and QR Payments API
Yape Peruvian digital wallet and QR payment REST API for Peruvian merchants, e-commerce platforms, and fintech developers to accept Yape wallet payments via QR code from Peru's most popular digital payment app — serving 14M+ Peruvian users through Banco de Crédito del Perú (BCP)'s consumer wallet platform with QR-based payment acceptance, payment link generation, and merchant settlement for Peruvian consumer payment automation. Enables AI agents to manage QR payment for Peruvian consumer checkout automation, handle payment link for remote payment collection automation, access payment status for transaction verification automation, retrieve settlement for merchant disbursement automation, manage refund for payment reversal automation, handle webhook for payment event notification automation, access merchant analytics for Peruvian transaction reporting automation, retrieve yape code for consumer payment generation automation, manage mass payment for Peruvian disbursement automation, and integrate Yape with Peruvian e-commerce, delivery, and SME platforms for mobile wallet payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Peruvian bank-backed wallet. SBS. API key + OAuth2. Peru. Consumer payment and mobile data.
⚡ Reliability
Best When
A Peruvian merchant, e-commerce platform, or delivery service wanting AI agents to accept Yape QR payments from Peru's 14M+ Yape users through BCP's consumer wallet platform.
Avoid When
SBS AND BCP REGULATIONS: Yape operates under Peru's Superintendencia de Banca, Seguros y AFP (SBS) and BCP bank regulations; automated non-regulated payment implementation creates compliance risk; automated must comply with SBS electronic payment regulations. MERCHANT PARTNER REQUIRED: Yape merchant API access requires partnership agreement with BCP/Yape; automated public API access assumption creates no merchant endpoint; automated must complete Yape merchant onboarding. PERUVIAN SOL ONLY: Yape processes PEN (Peruvian Sol); automated USD payment assumption creates currency_not_supported; automated must handle PEN amounts. YAPE CODE IS CONSUMER-GENERATED: The 'Yape code' (6-digit code) is generated by the consumer in their Yape app for in-person transactions; automated merchant-generated Yape code assumption misses correct flow; automated must support both QR display and consumer-generated code entry.
Use Cases
- • Accepting Yape QR payments from Peruvian consumers for e-commerce and in-person merchant checkout automation agents
- • Generating Yape payment links for remote payment collection from Peruvian consumers for SME automation agents
- • Processing Yape mass payouts to Peruvian freelancers and delivery drivers for gig economy disbursement automation agents
- • Integrating Yape with Peruvian marketplace platforms for consumer wallet payment and merchant settlement automation agents
Not For
- • Non-Peruvian markets (Yape is Peru-specific digital wallet backed by BCP)
- • International cross-border payments (Yape is domestic Peruvian payment platform)
- • Large enterprise B2B procurement (Yape is consumer and SME payment app)
Interface
Authentication
Yape uses API key + OAuth2 for merchant authentication. REST API with JSON. Lima, Peru HQ. Launched 2016 by BCP (Banco de Crédito del Perú, Peru's largest bank). Products: QR payment, Yape code, payment link, merchant payment, mass payout, merchant analytics. SDKs: None public. SBS regulated. Backed by BCP (Credicorp group). 14M+ users. Peru's #1 digital wallet. Competes with Plin (BBVA/Scotiabank/Interbank) for Peruvian digital wallet.
Pricing
Lima PE. SBS regulated. BCP subsidiary. Per-transaction. 14M+ users. Peru's leading digital wallet.
Agent Metadata
Known Gotchas
- ⚠ TWO PAYMENT FLOWS: Yape supports (1) merchant QR display that consumer scans and (2) consumer-generated 6-digit Yape code that merchant enters; automated single-flow assumption misses half of Yape payment scenarios; automated must support both scan-to-pay and code-entry flows
- ⚠ CONSUMER MUST HAVE YAPE APP: Yape payments require consumer to have active Yape account with Peruvian phone number; automated universal Peruvian coverage assumption misses non-Yape users; automated should offer Plin or card payment fallback
- ⚠ PERUVIAN SOL WITHOUT CENTS: Yape processes PEN amounts typically as integers; automated decimal-cent assumption creates validation error; automated must handle PEN amounts correctly (Yape tends to use whole soles)
- ⚠ PHONE NUMBER IS YAPE IDENTIFIER: Yape accounts linked to Peruvian mobile phone numbers; automated email-based consumer identification assumption creates consumer_not_found; automated must collect Peruvian phone number for payment link and mass payout flows
- ⚠ MERCHANT ONBOARDING IS BCP-CONTROLLED: Yape merchant API access is controlled by BCP; automated independent Yape access assumption creates gated production; automated must work through BCP commercial relationship for merchant API access
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Yape Peruvian Digital Wallet and QR 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.