connectIPS and Bank-Transfer Payments in Nepal

What this page covers

Bank-transfer style payments - where the customer moves money from their own bank rather than typing card details at checkout - are one of the families Nepali merchants ask about. This page sets out what our directory has recorded about the connectIPS profile, what to ask before you build on a transfer flow, and how to confirm a claim rather than take it.

What our directory has recorded

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

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 product, that a transfer flow is enabled for your business category, or that it is live for new merchants 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".

What a transfer flow asks of you

1. **Is the flow live for new merchants in my category today**, rather than planned? 2. **What does the customer see** - a list of banks to choose from, a reference code, or a redirect to their own bank's interface? 3. **How is a completed transfer confirmed to your system**, and how quickly? A payment that has left the customer's account but not yet been confirmed to you is the gap where support tickets are born. 4. **What happens when a customer starts a transfer and does not finish it** - is the order held, released, or left in limbo? 5. **Refunds** - who initiates them, how long they take, and what the customer is told. 6. **Settlement** - when funds arrive, into which account, and in which currency. 7. **Cost** - what you pay per transaction and per failed attempt, in writing. 8. **Support** - the escalation route when a transfer is stuck, and the hours it operates.

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 flow list in writing. Test the full flow in a sandbox, including a transfer that is started and abandoned. 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.

Why the abandoned transfer matters

An unfinished transfer is the most common failure in this family of payments. Ask explicitly whether the order is held, released, or left open, and whether your system is told which of those happened. The answer decides what your support team says to a customer who insists they have already paid.