← Back

Country payment guide

Accept payments in Nepal

Nepal payment planning should test local customer method fit before assuming one PSP route covers checkout, QR, wallet, bank, refund, and dispute needs. Use the page to ask providers whether the merchant can be boarded, which entity signs, which payout account and currency are available, what KYB and tax documents are required, how failed or pending payments are reconciled, and how public contact routes should be used.

Which PSPs and payment routes can you explore in Nepal?

Start with the payment methods and provider directory below for Nepal. Research does not cover every route; contact us if you cannot find a suitable option.

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.

8Channel recordsPublic directory entries
AsiaRegionNP
Usually requires a local entityOnboardingFrom structured fields
Real-time / T+0SettlementVerify on detail pages

Curated market guide

Nepal PSP routes to verify first

Which PSPs, acquirers, gateways, and local payment routes should a merchant ask first for Nepal?

6
bank_or_financial_institution · curated

bank_or_financial_institution

Prioritize this when you need NEPALPAY QR merchant enrollment, local settlement, or bank-led acquiring.

Official NEPALPAY QR material tells merchants to contact their bank, financial institution, or service provider for enrollment. Treat Nepali business registration, bank-account, tax, and documentation needs as provider-specific checks until the onboarding provider confirms them in writing.

  • Can my merchant entity onboard directly, or do you require a Nepali registered business and local bank account?
  • Can you enroll merchants for static QR, dynamic QR, gateway-based QR, or card acquiring?
  • Which documents are required for merchant code issuance, settlement, refund handling, and reconciliation?
payment_system_operator_or_gateway · curated

payment_system_operator_or_gateway

Prioritize this when you need connectIPS, NEPALPAY QR gateway flows, biller collection, or technical routing through the national payment infrastructure.

Official NEPALPAY QR material tells merchants to contact their bank, financial institution, or service provider for enrollment. Treat Nepali business registration, bank-account, tax, and documentation needs as provider-specific checks until the onboarding provider confirms them in writing.

  • Is my use case supported through a bank, a PSP, a biller gateway, or a direct technical integration?
  • Which onboarding steps are handled by NCHL infrastructure versus the merchant's bank or service provider?
  • Which API, dashboard, or merchant enrollment form applies to online checkout?
local_psp_or_wallet · curated

local_psp_or_wallet

Prioritize this when the customer base pays through wallet apps and you need QR or wallet checkout coverage.

Official NEPALPAY QR material tells merchants to contact their bank, financial institution, or service provider for enrollment. Treat Nepali business registration, bank-account, tax, and documentation needs as provider-specific checks until the onboarding provider confirms them in writing.

  • Are you enabled for NEPALPAY QR issuing, acquiring, or both?
  • Can you onboard my business category and current entity jurisdiction?
  • How do you handle refunds, failed payments, customer references, settlement reporting, and support escalation?
nepalpay_qr_through_an_acquiring_bank_financial_institution_or_psp · curated

NEPALPAY QR through an acquiring bank, financial institution, or PSP

NEPALPAY QR supports merchant-level QR interoperability and includes static QR, dynamic QR, gateway-based QR, merchant acquiring APIs, and acquiring settlement context.

Official NEPALPAY QR material tells merchants to contact their bank, financial institution, or service provider for enrollment. Treat Nepali business registration, bank-account, tax, and documentation needs as provider-specific checks until the onboarding provider confirms them in writing.

  • Start with the merchant's bank or a listed acquiring institution; ask for merchant enrollment rather than a generic support path.
  • Can my merchant entity onboard directly, or do you require a Nepali registered business and local bank account?
  • Can you enroll merchants for static QR, dynamic QR, gateway-based QR, or card acquiring?
connectips_payment_gateway_for_account_based_checkout_and_biller_flows · curated

connectIPS payment gateway for account-based checkout and biller flows

connectIPS is positioned as a bank-account payment platform for fund transfer, service payment, and gateway use cases.

Official NEPALPAY QR material tells merchants to contact their bank, financial institution, or service provider for enrollment. Treat Nepali business registration, bank-account, tax, and documentation needs as provider-specific checks until the onboarding provider confirms them in writing.

  • Ask whether the flow is available for your merchant type through your bank, a biller arrangement, or a gateway integration.
  • Can my merchant entity onboard directly, or do you require a Nepali registered business and local bank account?
  • Can you enroll merchants for static QR, dynamic QR, gateway-based QR, or card acquiring?
KYB prep

Documents to prepare

  • Company registration certificate and operating entity details.
  • Beneficial-owner, director, and signatory identity documents.
  • Business website/app URLs, product description, refund policy, terms of service, and restricted-category explanation where relevant.
  • Bank account, settlement currency, tax/VAT/GST information, and expected processing volume.
Due diligence

Questions to ask

  • Can my current merchant entity onboard, or is a local company or bank account required?
  • Which local payment methods are live for my business category and customer flow?
  • What documents are required for KYB, technical review, and production approval?
  • How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
  • Which public email, form, dashboard, or partner manager should be used for merchant onboarding?
Contact route fallback

If the official contact route is unclear

Use the official merchant enrollment form, bank relationship manager, or provider contact page first. If no merchant owner is visible, use LocalPayMap to route the question to the right bank, PSP, or gateway path.

  • Which local payment methods are live for my business category and customer flow?
  • What documents are required for KYB, technical review, and production approval?
  • How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
  • Which public email, form, dashboard, or partner manager should be used for merchant onboarding?

How local customers usually pay

Nepal is a wallet, QR and bank-transfer market. eSewa, Khalti, Fonepay, connectIPS, NEPALPAY QR and bank gateway routes can be more familiar to local buyers than international card checkout. Cards still matter for travel and higher-value online transactions, but many everyday customers expect mobile wallet or QR payment experiences. A merchant should ask whether the provider supports wallet collection, interoperable QR, bank transfers and automatic reconciliation from one dashboard. Foreign merchants need extra clarity on whether a local entity, tax registration or local settlement account is required. Refund handling is especially important because wallet, QR and bank rails may not behave like card refunds.

  • eSewa, Khalti, IME Pay or similar wallet coverage. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
  • Fonepay, NEPALPAY QR or connectIPS-style bank rails. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
  • Cards for travel, education and international customer segments. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.

Payment methods to check first

For Nepal, begin with the methods that match real customer behavior, then map each one to a provider that can actually onboard your merchant. Current public records point to Digital wallet, General commerce, Payment aggregator, Instant payment and Bank transfer, but availability can vary by PSP, entity type and industry.

  • Start with the payment method customers already recognize, not the provider with the longest logo wall.
  • Check whether the method supports online checkout, payment links, QR, app redirects, refunds and clear transaction references.
  • Keep one fallback method for buyers who cannot or will not use cards.
  • Document which method is mandatory for launch and which can wait for phase two.

What to do if you do not have a local company

Do not assume a foreign company can use the same route as a local merchant in Nepal. Some PSPs can onboard overseas entities, some require a local company and local bank account, and some support only selected industries. The cleanest first email states your incorporation country, product, website, expected volume, average order value, customer location, settlement currency and refund model.

  • Ask whether foreign entities are accepted directly or only through a local subsidiary, distributor or merchant-of-record arrangement.
  • Confirm local company, tax ID, local bank account, local director, licence and proof-of-address requirements.
  • Ask which settlement currencies and payout countries are supported for your entity.
  • Get the onboarding answer in writing before promising a local method to customers.

PSP and four-party provider screening

Use provider discovery to separate customer-facing payment brands from the companies that can legally process and settle funds. Public PSP/contact leads for Nepal currently include CellPay, eSewa, eSewa Merchant Services, Fonepay, Gateway Payment Service and Himalayan Bank E-Commerce Gateway. Compare them by eligibility, method coverage, operational support and documentation quality rather than headline pricing alone.

  • CellPay: Wallet operator. Verify live coverage for Mobile wallet, QR code, Cards, Bank transfer, Bills payment and P2M, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • eSewa: Wallet operator. Verify live coverage for eSewa wallet, merchant payments, online payments, mobile wallet and developer integration, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • eSewa Merchant Services: Wallet operator. Verify live coverage for eSewa wallet, merchant payments, online/offline payments and developer integration, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • Fonepay: Card network / switch. Verify live coverage for Fonepay QR, merchant payments and bank wallet network, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • Gateway Payment Service: Card network / switch. Verify live coverage for PaymentNepal, card e-commerce payment, mobile banking interchange, QR, wallet interchange and remittance, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • Himalayan Bank E-Commerce Gateway: Bank merchant services. Verify live coverage for Cards and Bank transfer, entity eligibility, pricing, settlement and support before treating it as a launch option.
  • IME Pay: Wallet operator. Verify live coverage for Mobile wallet, QR code, Cards, Bank transfer, Remittance and Bills payment, entity eligibility, pricing, settlement and support before treating it as a launch option.

Settlement, currency, refunds and disputes

Treat all pricing and settlement information for Nepal as preliminary until confirmed by the official provider or contract. Fees, payout timing, rolling reserves, FX, chargeback costs and refund rules can change by industry, volume, risk review, settlement currency and integration route.

  • Ask for transaction fee, fixed fee, refund fee, chargeback fee, payout fee, FX spread, reserve policy and minimum monthly or setup charges.
  • Confirm payout timing, settlement currency, settlement account country, failed-payout handling and reconciliation file fields.
  • Check whether refunds must return through the original method and whether partial refunds are supported.
  • For cards, confirm dispute workflow, evidence deadlines, chargeback fees and fraud-monitoring rules.

Compliance and operating checks

Before launch in Nepal, prepare KYB and risk material as if the provider will ask for it. Most delays for new merchants come from unclear ownership, unsupported industries, missing licences, incomplete websites, weak refund policies or settlement accounts that do not match the merchant record.

  • Prepare company registration, ownership, director ID, website/app URL, product description, terms, privacy policy and refund policy.
  • Disclose regulated products, digital content, subscriptions, marketplace activity, high-risk categories and cross-border fulfilment.
  • Ask how the provider screens sanctions, fraud, AML risk, chargebacks and customer complaints.
  • Keep sensitive or restricted markets at compliance-review level; do not use unofficial workarounds.

Questions to ask service providers

Send a concise written checklist to every Nepal PSP or aggregator so responses can be compared side by side. The goal is to expose hidden entity, settlement, support and technical gaps before engineering work begins.

  • Which payment methods are live today for my exact merchant entity, industry and customer geography?
  • Do you support hosted checkout, API, plugin, payment links, webhooks, sandbox, refunds and reconciliation exports?
  • Who is the merchant of record, who handles chargebacks and who owns customer support for failed payments?
  • What documents are requested, how is approval reviewed, and what would cause rejection?
  • Can you provide official links for pricing, settlement terms, developer docs and support escalation?

Common beginner mistakes

The most common mistake in Nepal is treating payment acceptance as a logo checklist. Local conversion depends on customer habit, provider eligibility, settlement flow, refund support and operational reliability. A cheaper-looking route can become expensive if it cannot settle where you need, cannot refund cleanly or cannot support the methods buyers expect.

  • Choosing cards only when wallets, mobile money, bank transfer, QR or cash-style routes are normal for local buyers.
  • Building against an API before KYB, entity and settlement eligibility are confirmed.
  • Ignoring refund and dispute flows until the first customer complaint arrives.
  • Comparing providers without asking the same written questions of each one.

Next actions

Next actions for Nepal

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

Questions merchants ask

Which payment methods should a new merchant check first in Nepal?

Start with Digital wallet, General commerce, Payment aggregator, Instant payment and Bank transfer. Then confirm which provider can support your entity, industry, customer geography, settlement currency and refund model.

Can a foreign merchant accept local payments in Nepal without a local company?

Sometimes, but it must be verified provider by provider. Ask whether a local entity, local bank account, tax ID, licence, local director or merchant-of-record route is required.

Which PSPs or aggregators are worth screening for Nepal?

Public leads include CellPay, eSewa, eSewa Merchant Services, Fonepay, Gateway Payment Service and Himalayan Bank E-Commerce Gateway. Treat them as a shortlist for outreach, not as confirmed eligibility or complete market coverage.

Can I use public fee pages as a final quote?

No. Public fees are screening context only. Final pricing can vary by country, industry, volume, risk review, settlement currency, FX, reserves and contract terms.

What operational questions should I ask before integration?

Ask about onboarding documents, restricted industries, live payment methods, checkout flow, webhooks, sandbox, refunds, disputes, chargebacks, reconciliation files, settlement timing and support escalation.

What should I do if the provider has no public sales email?

Use the official contact form, support page or developer contact route, and send a short brief with your entity country, product, volume, currencies and required payment methods.