How does a Yape payment work?
Yape accounts are identified by the user’s Peruvian mobile number. In a shop, the customer scans a QR code or sends money to the merchant’s number. Online, the flow is different and needs no QR code. At checkout the shopper chooses Yape and enters the phone number linked to their account. They then open the Yape app, select the approval code option in the menu, copy the six-digit code and paste it into the checkout. The provider sends the number, code and amount to Yape, Yape debits the balance and the provider reports an approved or declined result to the merchant within seconds. One major Peruvian gateway gives the code a two-minute expiry and applies a daily limit to Yape e-commerce purchases, so the shopper should generate the code only when they are ready to pay. The shopper never shares a card number or bank login with the merchant, only the phone number and a single-use code.
Why does Yape matter for merchants?
Yape is part of daily life in Peru. Credicorp reported 16.4 million monthly active users at the end of the first quarter of 2026, with an average of 67 transactions a month per active user, and 16.7 million in the second quarter, when Yape’s fee income grew 62.5%, according to La República. Since 2023 Yape has been interoperable with Plin, the wallet service of several other banks, and BBVA Peru counts about 28 million active accounts across the two. For an online merchant that means a large share of shoppers already have the app on their phone and are used to approving payments in it. Yape added its online payment button in 2022 through Peruvian payment gateways, starting with more than 100 e-commerce sites in sectors such as entertainment, insurance, transport and education. For merchants, Yape reaches customers who have no credit card or prefer not to use it online, at a lower risk of card-style disputes.
Yape also runs in Bolivia. Infobae reported in January 2026 that Yape entered Bolivia in 2023 through BCP’s Bolivian bank and had about four million users there, and that a merchant product, Yape Comercios, was being prepared. The Bolivian app is separate from the Peruvian one and works in BOB, so a merchant selling in Bolivia needs a provider with a Bolivian Yape or QR connection.
What can go wrong?
Most failed Yape payments are expired or mistyped codes. Shoppers generate the approval code, switch apps, and return after it has expired, or enter a phone number that is not the one linked to their Yape account. Daily limits on e-commerce payments produce declines for larger baskets, so merchants with high average order values need a second method, such as cards or a payment code, ready in the same checkout. Yape transfers between people cannot be cancelled or reversed in the app once sent, and the app’s help channel for mistaken payments depends on the recipient agreeing to return the money, so refunds for online orders have to be handled by the merchant and the provider. Timeouts between the provider and the merchant can also leave a payment approved on one side and pending on the other, which is why the final status should come from the provider, not from the browser redirect.
How would Omno handle Yape?
A merchant would show Yape in the hosted checkout with the phone number and approval code fields in one step, or offer it through Direct Links on its own checkout. Routing rules set by the merchant would choose the provider. In the hosted checkout, if a provider is unavailable or rejects the request, the payment moves to the next provider in the rule until one accepts. The final status would reach the merchant by webhook, which is the source of truth for confirming the order. Rules could show Yape only for PEN payments within the amount range the provider supports, and offer cards or PagoEfectivo for larger amounts. The routing-decision log would record which provider handled each payment.