Yape and Plin for Merchants: QR Collection Versus Online Checkout
Compare Peru's Plin QR, Yape Empresa and gateway-based Yape online checkout, and ask the right questions about proof of payment, fees and reconciliation.
A Plin QR, Yape Empresa's managed QR and Yape online checkout are different merchant workflows. Their public pages describe collection and visibility features, but not one universal fee, refund or payout model.
For a Peru merchant, start with the point of sale: Plin publishes a QR collection route, Yape Empresa offers managed QR codes by location or till with staff visibility, and Yape directs online merchants to gateways such as Culqi, Niubiz and Izipay. These are distinct products. Confirm eligibility, pricing, settlement destination, refund handling and transaction-level reconciliation with the specific provider before launch. Wallet interoperability by itself does not establish that a given checkout or merchant account accepts both brands.
A QR at a counter and a Yape button on a website can look like the same payment choice to a customer. They are different operating choices for the merchant. The question is not simply whether people in Peru can move money between Yape and Plin; it is who receives the payment, what confirms it, and what report ties it to the order.
The Peru market overview explains the wider payment landscape. This guide concentrates on three collection routes documented by their operators. None of the sources below supplies a universal merchant fee, settlement timetable or refund flow across all three.
Three routes, three records to check
| Merchant route | What the public product page establishes | What the merchant still needs to confirm |
|---|---|---|
| Plin QR | Plin describes showing or sharing a QR to collect a payment. Its examples sit inside participating institutions' apps. | Which account receives it, applicable merchant limits or fees, how staff verify it and how the receipt joins the order record. |
| Yape Empresa | The merchant portal describes distinct QR codes by location, till or collaborator, staff payment notifications and sales reports. | Eligibility, account structure, pricing, bank transfer or withdrawal path, report fields and refund process. |
| Yape online through a gateway | Yape tells a business that wants Yape on its website to contact Culqi, Niubiz or Izipay. | The contracted gateway's API or plugin, payment states, confirmation method, fees, refunds and settlement file. |
This is a workflow comparison, not a ranking of providers. A merchant with one physical till may need a simple QR and a way to verify a receipt. A business with several branches may need QR attribution by location and employee. An online seller needs an order-linked checkout confirmation from its actual gateway. One operation can use more than one route; the public pages do not say that a single contract combines them.
A successful customer screen is not the whole ledger
For Plin QR or a Yape Empresa QR, establish which staff member can see a completed collection in the official app or portal and what identifying detail the report retains. Yape Empresa says collaborators can receive payment notifications and that its portal shows sales in real time. That is useful for a busy counter, but a notification should still be matched to the amount and internal sale reference before an order is marked paid. Ask for a sample report and test duplicate amounts, delayed notifications and a customer showing the wrong receipt.
For online Yape, treat the gateway's server-side payment record as the operational source, rather than the shopper's browser return alone. Yape's own merchant help page names three gateways to contact. It does not specify one common status schema, payout timing or refund API. Ask the selected gateway for those details and for the fields that join a payment, refund and settlement line to your order ID.
Interoperability is a consumer reach question, not a merchant contract
The BCRP's interoperability report describes phased connections among wallets, bank apps and QR payments. That describes network reach. It does not establish that every QR, gateway or merchant account accepts every wallet under the same terms. Nor does the report establish a live Phase 4 payment-initiation route: its 2025 description says the model was being designed.
Before signing, ask the provider to demonstrate a real test transaction from each customer app you need to serve. Record which payer app works, who appears as the payee, how a mistaken payment is returned, how funds reach the merchant's bank, and where transaction-level exports are obtained. Keep product fees and limits dated to the actual offer you receive; consumer transfer limits should not be presented as the limits for a business collection product.
The decision is therefore concrete: choose the collection route that fits the sale, then verify payment proof, settlement destination, pricing and reconciliation in the provider's current contract and reports. Do not infer those from a national interoperability headline.
Sources & methodology (4)
Yape Empresa describes multiple QR codes by location, till or collaborator, staff verification, live sales reporting and up to three months of report history.
Checked:
Yape directs merchants seeking Yape online payments on their websites to contact Culqi, Niubiz or Izipay.
Checked:
Plin presents QR collection as a way for a business to receive payments, with immediate receipt messaging and participating-bank app examples.
Checked:
BCRP says its interoperability programme connected wallets, bank apps and QR acceptance in phases, while its Phase 4 payment-initiation model was still being designed in the 2025 report.
Checked:
Source types explained in our Methodology.
By Shaun Toh · Director, Digital Payments · Razer