How to Choose and Set Up a Payment Gateway for Your Nepali Online Store

Accepting payments online is one of the first real infrastructure decisions a Nepali e‑commerce business makes. The options have multiplied, but the fundamentals haven't changed: you need a provider that settles reliably in rupees, integrates with your stack, and won't disappear when you need support. This guide covers what to prepare, what to ask, and how to think through the trade‑offs.

Start with the paperwork you can gather now

Every provider will ask for proof that your business exists and that you are who you say you are. The usual suspects are your company registration certificate, PAN or VAT certificate, a bank account in the business name, and KYC documents for the authorised signatories. Some gateways also want a board resolution authorising the account, or a recent utility bill matching the registered address. The exact list varies, so ask for the onboarding checklist before you start collecting — it saves the back‑and‑forth that stalls most applications.

Understand how fees actually work

Headline transaction rates are easy to compare; the total cost of acceptance is not. Look for setup fees, monthly or annual maintenance charges, refund and chargeback fees, and any minimum‑volume commitments. Settlement speed matters too — funds that arrive in one business day keep your cash flow healthier than a three‑day cycle, but faster settlement sometimes carries a premium. Ask whether settlement happens directly in Nepali rupees or if a currency conversion step is involved; conversion spreads can quietly eat margin. Request a full fee schedule in writing and model it against your expected order volume and average ticket size.

Match the gateway to your technical reality

If you have developers, a REST API with SDKs for your stack gives you control over the checkout experience. If you don't, a hosted payment page or a plugin for your platform (WooCommerce, Shopify, custom PHP, etc.) keeps PCI scope off your shoulders. Either way, insist on a sandbox environment. Test success flows, failed payments, timeouts, and webhook delivery before you ever switch to production keys. The time you spend in sandbox is the time you don't spend debugging live orders.

Verify the provider's standing yourself

Don't rely on a sales deck. Check the Nepal Rastra Bank website for the current list of licensed payment system operators — it's updated regularly. Ask the provider for their PCI‑DSS Attestation of Compliance and note the date. If data residency matters for your business (some sectors require transaction data to stay in Nepal), confirm where their primary and backup servers sit. A provider that can't answer these questions clearly is a risk you probably don't need.

Support is part of the product

Open a test ticket during business hours before you sign. Ask a specific question — about webhook retry logic, or settlement cut‑off times, or how they handle a disputed transaction. The speed and clarity of the answer tells you more than any SLA document. When a payout gets stuck at 11 PM on a Friday, you'll want a team that actually responds.

Compliance habits that protect you

Rotate API keys on a schedule. Restrict webhook endpoints to known IPs. Log every transaction response your system receives — not just the successful ones. Keep your integration code under version control so you can roll back if a gateway update breaks something. These aren't gateway features; they're your operational discipline.

A practical shortlist for evaluation

• Current NRB licence status (check the central bank site yourself)
• Full fee breakdown with no hidden line items
• Settlement currency, speed, and cut‑off times
• PCI‑DSS AoC date and data‑hosting locations
• Sandbox access and documentation quality
• Support responsiveness on a real test query
• Plugin or API fit for your current stack

You don't need the cheapest gateway. You need the one that settles on time, answers the phone, and doesn't surprise you with fees six months in. Do the homework once, and you can get back to selling.