Khalti Payment Gateway and API: An Overview

What this page covers

If you are a developer wiring a checkout for customers in Nepal, Khalti is one of the names you will meet. This page sets out what our directory has recorded about that profile, the developer questions that decide whether an integration is workable, and how to confirm an answer before you commit to it.

What our directory has recorded

Our directory holds a Nepal market coverage record for Khalti, created from the provider's own website on 11 August 2026, with the official website recorded as khalti.com. The same record set covers four other Nepal-linked names: connectIPS, eSewa, Fonepay and IME Pay.

A coverage record says one thing: our research team linked the provider to the Nepal market using an official source. It does not say the provider offers a merchant API, that the API is open to new businesses in your category, or that it is live today. Each profile shows the verification state and source date of every field, and where our records hold nothing the profile says "Not publicly disclosed".

The developer questions that matter

1. **Is there a test environment**, and does it behave like production - including declined, abandoned and duplicate payments, not only successful ones? 2. **How does your system learn that a payment finished?** Look for a callback or webhook, and ask how retries work when your endpoint is briefly unreachable. 3. **What is the idempotency story?** If your server processes the same notification twice, does the customer get charged or credited twice? 4. **How are refunds initiated** and what states can a refund pass through? 5. **Which currencies and methods does the API expose**, and which are enabled for your account rather than the platform in general? 6. **What does the rate limit look like** at the volume you expect, and what happens when you hit it? 7. **How long do keys and credentials last**, and what is the rotation process? 8. **Who do you call** when a payment is stuck at 2am, and what is the expected response time?

Where the official material sits

Nepal Rastra Bank publishes material on payment systems at https://www.nrb.org.np. Read it for yourself rather than relying on a reseller's summary. Our directory does not interpret those rules for your business, and it does not state that any listed provider holds a licence.

What our records do not cover

For this provider the directory does not hold verified data on pricing, onboarding time, acceptance rules, settlement timing, or authorisation status. Those answers must come from the provider, in writing, so you can compare two or three of them on the same basis.

A short verification routine

Open the profile and read the method rows with their verification state. Ask for the live API capability list in writing. Build against the sandbox and run the full flow, including a declined payment, an abandoned payment and a refund. Check the regulator's published material at https://www.nrb.org.np for what applies to you. Keep every answer with its date.

Where to look next

The Nepal country page lists the providers our directory has recorded for that market. Place two or three profiles in the comparison tool to see which fields are verified and which are still missing. If you hold an official document that adds or corrects a record, submit it through the correction form on the profile and we will check it against the source before the record changes.

A note on documentation you cannot run

Reading an API reference is not the same as calling it. Ask for a test account before you agree to anything, and spend an hour in the sandbox. The gaps that matter - a missing callback, unclear payment states, no refund path - show up in the first hour, not in the first week.