Accept Khalti payments from customers in Nepal through A-Pay. Add this supported local payment method to your merchant setup, integrate payment requests with your platform, and handle transaction results in your backend. The available Khalti configuration is confirmed for your project during onboarding.
Nepal payment method
Khalti is a digital payment platform used by customers in Nepal. For merchants, it is a local payment option that can be offered through an approved A-Pay payment setup.
Khalti and IME Pay merged in 2025, and the combined service now operates under the Khalti brand. Khalti is the customer-facing payment method, while A-Pay provides gateway integration and transaction processing for eligible merchant projects in Nepal.
A-Pay documents Khalti deposits in Nepalese rupees (NPR). The specific customer flow and enabled payment configuration are agreed during integration.
Merchant integration choice
Khalti operates its own payment services. A-Pay is a separate payment gateway: it offers merchants a way to add the supported Khalti method to their broader payment setup. The right model depends on your business, technical requirements and onboarding conditions.
Your business works with Khalti's own onboarding process, merchant requirements and developer documentation. The payment method is connected directly through the infrastructure offered by Khalti. This can be an appropriate path when your business wants a direct arrangement with the payment provider.
Your platform integrates with A-Pay to initiate payments using the Khalti configuration enabled for your project. Your backend receives transaction results and updates customer-facing payment states. You can also discuss adding other supported local payment methods within your A-Pay setup, subject to availability for your business.
Already connected to A-Pay? Additional supported payment methods can be enabled for an existing merchant without an extra method-activation fee. The number of enabled methods does not change the connection price. Availability is assessed for your project.
From payment request to merchant result
A Khalti deposit starts in your platform. The payment request is created through the agreed A-Pay integration, the customer follows the enabled payment instructions, and your backend processes the reported transaction outcome. The exact wallet screens depend on the configured method.
Illustrative interface only; not an actual Khalti or A-Pay checkout screenshot.
Your backend creates and tracks the deposit. It must not treat a browser return alone as proof that a payment succeeded.
A customer chooses Khalti in your checkout. Your backend sends the deposit request to A-Pay using an enabled configuration.
The documented API response includes a payment-page URL. The customer completes the available Khalti payment steps.
A-Pay sends a technical deposit callback to your configured application handler when the deposit is confirmed.
Your backend checks the result, updates the relevant order or balance, and displays the outcome to the customer.
For product and engineering teams
A-Pay supports Host-to-Host API integration and a Hosted Payment Page. These are connection approaches, not separate payment gateways. The available interface and payment-system configuration for Khalti must match the setup approved for your merchant project.
Your server initiates deposits with authorized A-Pay credentials. A Hosted Payment Page also requires backend integration; it is not a no-code substitute for handling transactions.
A-Pay's NPR deposit documentation lists
khalti
and
khalti_l
as payment-system identifiers. Your A-Pay integration team will confirm which identifier and customer payment flow are available for your merchant project.
The API response schema for both documented Khalti variants includes
paymentpage_url
. Your frontend can then direct the customer to the payment interaction described by your integration.
Connect your application handler for deposit callbacks. Match the result to your transaction record, validate the reported data and update the customer-facing payment state in your own system.
DOCUMENTED A-PAY DEPOSIT CONTEXT
The available payment-system identifier and checkout flow depend on your configured merchant integration.
Developer resources: Check the Deposit API documentation and the Hosted Payment Page guide before implementing your checkout.
Discuss integrationLocal payment coverage
Khalti can be part of a wider Nepal payment setup. A-Pay also lists eSewa as a local wallet method and Khalti QR as a separately named QR variant. These options are assessed and activated according to the configuration available for your merchant.
The digital wallet option covered here. A-Pay documentation includes Khalti deposit configurations for NPR, with customer payment steps determined by the enabled integration.
Another local payment option in the supported Nepal method list. Ask A-Pay whether it can be added to your current project and which payment flow applies.
Khalti QR is an additional payment variant listed for Nepal. If your business needs a QR-based Khalti payment flow, A-Pay can confirm the available configuration and implementation requirements for your project.
To explore other supported payment methods and merchant payment options in Nepal, see Payment Gateway in Nepal . Ask our team which local methods can be enabled together for your business.
Merchant onboarding
The next steps depend on whether you are connecting to A-Pay for the first time or expanding an existing integration. For both cases, the availability of Khalti and the exact payment configuration are confirmed for your business.
Tell the A-Pay team about your project, customer market and the payment flow you need. Discuss merchant eligibility, the Khalti configuration, integration approach and commercial terms. After onboarding, your developers can implement the agreed requests, configure callback handling and test the supported scenario before launch.
If your business already works with A-Pay, request Khalti as an additional supported method. Adding supported methods is free for existing merchants, and the number of enabled methods does not change the connection price. The product team can resolve an additional-method request within one day, subject to availability for your setup.
Khalti is a digital payment platform used in Nepal. Businesses can accept Khalti payments directly through the provider or use a gateway integration where the method is available. A-Pay offers Khalti as a supported local payment option for merchant projects in Nepal; it does not operate or own the Khalti wallet.
Yes, Khalti is in A-Pay's supported payment-method list for Nepal. Actual availability, customer flow and merchant conditions are reviewed for your project. Contact A-Pay with your business model, the expected payment direction and the integration approach you plan to use.
A-Pay's published deposit API lists Khalti-related payment-system identifiers under NPR, the Nepalese rupee. This is a documented deposit currency; it should not be interpreted as a promise of automatic multicurrency Khalti processing or zero currency-conversion costs.
Your backend creates a deposit request through the authorized A-Pay integration. The documented Khalti configurations include a paymentpage_url in the response, which can direct the customer to the required payment interaction. The customer completes the enabled steps, and your backend handles the transaction result. The precise interface depends on your configured flow.
A-Pay describes a technical deposit callback sent to the merchant application handler when the deposit is confirmed. Your server should match the received information to the relevant transaction record and use its own business rules to update an order, account or balance. A browser return alone should not be treated as proof of successful payment.
No. Khalti and IME Pay merged in 2025, and the combined service now uses the Khalti brand. A-Pay lists Khalti as a supported wallet method for Nepal. If an existing technical integration refers to IME Pay, contact our team to confirm the appropriate configuration.
A-Pay lists eSewa and a Khalti QR variant as supported payment options for Nepal. The methods and payment flows available to your business depend on your merchant configuration. Existing A-Pay merchants can request additional supported methods without an extra activation charge.
Contact your A-Pay account or support team to request Khalti for your existing integration. The team will confirm method availability and the required configuration. Adding supported methods is free for existing merchants, and these requests can be resolved within one day. New merchant onboarding is handled separately.
