← Back

Country payment guide

How customers pay in Peru

Peru adopted bank-built P2P wallets faster than almost anywhere in the region, and Yape and Plin are now everyday payment tools rather than novelties. Cards still carry online value, and cash collection fills the gap. This guide covers the mix, the providers, and the questions to settle before signing.

Which PSPs and payment routes can you explore in Peru?

Existing research for Peru includes Culqi, PagoEfectivo, Izipay, izipay Online, Yape, Plin. Explore their products and local payment methods, then use your business and company location to narrow the enquiries.

No local company, or no clear contact route?

These are research leads, not approval or industry-support guarantees. Tell us the market and your company location so we can help you explore further.

6Channel recordsPublic directory entries
Latin AmericaRegionPE
Medium, verify entity and documentsOnboardingFrom structured fields
Real-time / T+0, T+1SettlementVerify on detail pages

Curated market guide

Peru PSP routes to verify first

Which PSPs or acquiring routes should a merchant ask first for Yape, Plin, PagoEfectivo, wallets, and cards in Peru?

4
local_psp_or_aggregator · curated

Peruvian PSP / aggregator shortlist

CulqiPagoEfectivoMercado Pago Peru for BusinessKushki Peru

Use when you need local wallet, cash, and card options without building each method one by one.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
acquirer_or_bank · curated

Acquirer merchant-services route

Izipayizipay OnlineNiubizVendeMas by Niubiz

Use when direct local acquiring, POS/online acquiring alignment, or bank-linked merchant services are important.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
direct_scheme_or_wallet · curated

Wallet and cash-payment route

YapePlinPagoEfectivo

Use when checkout adoption depends on local wallet or cash-payment familiarity and you can verify merchant access.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
international_psp · curated

Regional PSP route

PayU PeruAlignetRebill Peru

Use when the merchant wants one regional conversation and will verify Peru-specific entity, method, and settlement requirements.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
KYB prep

Documents to prepare

  • Company registration and RUC or foreign-entity onboarding question
  • Beneficial-owner and signatory ID
  • Website/app URL and terms/refund policy
  • Product category and risk explanation
  • Bank account and payout-currency requirements to verify
Due diligence

Questions to ask

  • Can my current merchant entity onboard for this market, or is a local company required?
  • Which local payment methods are actually enabled for my merchant category and transaction model?
  • Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
  • Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
  • Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?
Contact route fallback

If the official contact route is unclear

If public contact details are not specific enough, ask LocalPayMap to identify the right official form, PSP sales route, or local acquiring partner before committing engineering work.

  • Which local payment methods are actually enabled for my merchant category and transaction model?
  • Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
  • Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
  • Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?

How customers actually pay here

Peru's payment story is unusual because the two dominant wallets were built by banks. Yape, from BCP, and Plin, from Interbank, started as person-to-person transfer apps and spread into merchant payments almost by accident, helped by how simple they are: pay a phone number or scan a QR code. Younger buyers in particular reach for a wallet before a card. Cards remain the main online method for higher-value orders, including the local Globo debit network alongside Visa and Mastercard. PagoEfectivo bridges cash and bank transfer for buyers with no card. Cash-on-delivery still holds a modest share of ecommerce, especially outside Lima.

  • Yape and Plin grew out of bank-built P2P transfer apps and are now everyday payment tools.
  • Paying by phone number or QR code is the default mental model for many buyers.
  • Cards still carry higher-value online orders, including the local Globo debit network.
  • PagoEfectivo covers cash and bank transfer for buyers without cards.
  • Cash-on-delivery remains a modest but real share of Peruvian ecommerce.

Payment methods to prioritise first

Shortlist Yape early when selling to Peruvian consumers, because it is one of the most visible local payment apps. Add cards to the shortlist for recurring and higher-ticket orders, then compare Plin, PagoEfectivo and bank transfer based on audience, provider availability and operational fit. Do not lead with international cards only without testing local methods, because conversion can suffer when buyers do not see familiar options. The final checkout order should come from provider availability, conversion data, refund handling, settlement, and written pricing rather than a universal ranking.

  • Shortlist Yape early where your audience expects wallet-style local payment.
  • Keep cards in scope for recurring, higher-ticket and international buyers.
  • Evaluate Plin through aggregators only after confirming live merchant availability.
  • Use PagoEfectivo where cardless or cash-preferring buyers matter.
  • Add bank transfer for invoice or larger-order flows when reconciliation is clear.

How merchants usually connect

Peru is an aggregator market. Few merchants contract directly with a bank or scheme when Culqi, Izipay or Niubiz will hand them wallets, cards and cash collection in one integration. Culqi is the most common starting point for online businesses and small merchants. Izipay, tied to the Interbank group, is strong in both online and physical acceptance. Niubiz is the card acquiring and processing name behind a lot of domestic card volume. Mercado Pago spans wallet and acquiring. PagoEfectivo can be contracted for cash and transfer collection. Kushki, dLocal and PagSeguro are the regional names when Peru is one market inside a wider Latin American expansion.

  • Culqi is the most common starting point for online businesses and small merchants.
  • Izipay, tied to Interbank, is strong across both online and physical acceptance.
  • Niubiz is the domestic acquiring and processing name behind much card volume.
  • Kushki, dLocal and PagSeguro suit merchants expanding across several Latin American markets.

Operating without a local company

Do not assume a foreign entity can use the same Peru payment route as a local merchant. Some regional PSP routes may support cross-border contracting, while Yape, Plin, local acquiring, cash, transfer, or domestic settlement routes may require provider-specific eligibility, local connections, documents, tax data, banking, or a local partner. Confirm method scope, entity eligibility, pricing, payout currency, refunds, disputes, reconciliation, and support ownership in writing before integration.

  • A regional PSP contracts offshore and collects in soles, so a local entity is not mandatory.
  • Yape and Plin access depends on the provider's own local connections and risk appetite.
  • Expect detailed KYC on ownership, industry and volume, and allow extra time for it.

What to ask a provider before you sign

Ask whether Yape and Plin are live in production for merchants, not just listed as supported. Ask how wallet payments are confirmed back to your system and how quickly status updates arrive. Ask for the per-method price list rather than a blended rate. Ask about cards: which acquirers sit behind the integration, whether 3D Secure is supported, and who absorbs chargebacks. Ask for settlement currency options, the payout schedule and the FX spread over interbank. Ask how refunds work on wallet payments, since they are not as standardised as card refunds. Finally, ask whether they can contract a non-Peruvian entity.

  • Confirm Yape and Plin are live for merchants, not only listed as supported.
  • Ask how wallet payments are confirmed back to your system and how fast.
  • Get a written per-method price list and the settlement currency options.
  • Ask specifically how wallet refunds work, since they are less standardised than cards.

Fees, settlement and FX

Public pricing is only a first filter. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms. Confirm against the provider's official pricing page or a written quote before you go live. In Peru, wallet payments usually price below cards and settle faster, which is why they are worth prioritising despite the extra integration work. Cards cost more and carry dispute exposure. Cash and transfer collection through PagoEfectivo is cheap to issue but slow to convert. Add the FX spread on soles conversion, payout fees and any dispute handling charge, then model the blend across your real mix.

  • Public pricing is only a first filter, so confirm real numbers in a written quote.
  • Wallets usually price below cards and settle faster, which justifies integrating them first.
  • Cash and transfer references are cheap to issue but slow to convert into revenue.
  • Include FX spread, payout fees and dispute handling in your blended cost model.

Industry notes

Ecommerce: lead with Yape, add Plin, keep cards for higher tickets, and keep PagoEfectivo for cardless buyers. Digital goods, games and short drama: Yape and Plin are the core methods, because they suit frequent small top-ups and confirm instantly. SaaS and subscriptions: cards remain the realistic recurring option, since wallets here are built around one-off transfers rather than mandates. B2B and services: bank transfer and PagoEfectivo work for larger invoices, and corporate buyers will expect a proper invoice with a tax ID. Keep cash-on-delivery in the mix only if your logistics partner can reconcile it.

  • Ecommerce leads with Yape and Plin, with cards reserved for higher tickets.
  • Digital goods and short drama run on Yape and Plin for frequent small top-ups.
  • SaaS still needs cards for recurring billing, because wallets are one-off transfer tools.
  • B2B invoices use bank transfer or PagoEfectivo with proper tax documentation.

Risks, compliance and common mistakes

The most common mistake is launching with cards alone and assuming wallets are a nice-to-have; in Peru they are close to essential. The second is assuming wallet payments behave like cards: refunds are less standardised and recurring charging is generally not available. Fraud screening still matters, and 3D Secure should be on for cards. Payments sit under the SBS supervisor and data protection follows local privacy rules. Cash and transfer references need disciplined reconciliation, because buyers often pay late or not at all. Finally, treat FX as a real cost line, not an afterthought.

  • Treating wallets as optional is the fastest way to underperform in Peru.
  • Wallet refunds are less standardised than card refunds, so test them before launch.
  • Cash and transfer references need disciplined reconciliation, since buyers pay late or not at all.
  • Turn on 3D Secure for cards and budget FX as a real cost line.

Next actions

Next actions for Peru

Use these internal paths to move from market research to provider outreach without assuming eligibility, pricing, settlement, or local-entity access.

Questions merchants ask

Do I need a Peruvian company to accept payments in Peru?

Not necessarily, but it helps. Regional providers will often contract with a foreign entity and provide cards plus wallet access. Local acquirers and some wallet connections are easier and cheaper with a Peruvian entity. If you expect serious volume, ask your provider to price both routes before you decide.

Which payment method should I add first in Peru?

Add Yape first. It is the most widely used payment app in the country and many buyers will not complete a purchase without it. Add cards second for higher-ticket and recurring orders, then Plin, then PagoEfectivo for cardless buyers. Bank transfer suits B2B rather than consumer checkout.

How long does settlement take for Yape and card payments in Peru?

Wallet payments usually confirm quickly, but your provider still applies its own payout cycle before funds reach your bank. Cards typically settle on a longer cycle and can be slower again with a cross-border acquirer. Cash and transfer references wait on the buyer. Get the exact calendar in writing.

What does it cost to accept payments in Peru?

Public pricing is only a first filter. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms. Confirm against the provider's official pricing page or a written quote before you go live, and include FX spread, payout fees and dispute charges.

Can I get paid in USD or EUR instead of Peruvian soles?

Cross-border providers frequently collect in soles and settle in dollars or euros. Local acquirers more often settle in soles, which means arranging your own conversion. In both cases the spread over interbank and the timing of the conversion are the terms that actually determine what you receive.

What chargeback and refund risks should I plan for in Peru?

Cards carry standard dispute exposure, so use 3D Secure and keep clear delivery evidence. Yape and Plin have no card chargeback process, but refunds are less standardised and need to be tested before launch. Cash and transfer references carry no dispute risk but do carry non-payment.

Can I run subscriptions through Yape or Plin?

Generally not in the way cards allow. These wallets grew out of person-to-person transfers, so they suit one-off payments rather than stored mandates. For recurring revenue, keep cards as the billing method and use wallets for top-ups, one-time purchases and manual renewal.

Public sources