Subscription Infrastructure

Nepal's Subscription Infrastructure Layer

Nepal has payment infrastructure. eSewa, Khalti, and ConnectIPS handle transactions reliably. What Nepal has been missing is the layer above them — the system that manages renewal cycles, tracks subscriber status, sends reminders automatically, and makes recurring payment collection run without manual effort. That's what SUQO is.

The gap

Nepal's payment stack has a missing layer.

Infrastructure is the unsexy part of any technology ecosystem. It's not the application people use; it's the layer underneath that makes the application possible. Nepal's payment infrastructure — eSewa, Khalti, ConnectIPS, bank rails — has developed substantially over the past decade. Tens of millions of users. Billions in transaction volume. The payment layer works.

The subscription layer above it has been missing. Every business in Nepal that collects recurring fees — gyms, ISPs, coaching centers, insurance agents, SaaS companies — has been filling the gap manually. Personal calls before due dates. Spreadsheets to track who paid. Cash at the counter with notes somewhere. WhatsApp reminders copied one by one.

This isn't a technology problem — it's an infrastructure gap. The payment pipe exists. The system that schedules, monitors, and automates what flows through it on a recurring basis has not existed at scale in Nepal. Until now.

The stack

The payment layer vs the subscription layer.

It's worth being precise about what each layer does, because the confusion between them is exactly where recurring revenue leaks.

The payment layer (eSewa, Khalti, ConnectIPS)

Payment processors handle individual transactions. When a customer initiates a payment — scanning a QR code, clicking a payment link, entering credentials — the processor moves money from their wallet to the merchant account, confirms the transaction, and stops. That's it. The processor has no concept of "this customer is due again in 30 days." It doesn't track renewal cycles, send reminders, or maintain a subscriber record. It handled one transaction. The next transaction is a completely separate event.

The subscription layer (SUQO)

Subscription infrastructure sits above the payment processors and manages everything around the transaction. It knows that a subscriber's renewal is in 5 days. It sends the reminder. It includes the payment link. When the customer pays, it confirms the renewal and sets the next due date. When they don't pay, it sends a follow-up and marks the account overdue. It maintains the subscriber record — active, due, overdue, lapsed — and makes that state available to the business or to any application that integrates via API.

One layer moves money. The other layer manages the system that ensures money moves on schedule — and knows what to do when it doesn't.

SUQO in the stack

What subscription infrastructure provides.

The recurring payment cycle has more moving parts than a single transaction. SUQO manages all of them.

Renewal cycle management

Every subscriber's renewal date is tracked from their first payment. The billing cycle advances automatically — no manual input required. The system always knows who renews when.

Automated SMS reminders

Reminders go out before and after renewal dates over SMS — the channel Nepal subscribers actually respond to. Each reminder includes a payment link. No manual sends, no copy-paste.

Payment collection via eSewa & Khalti

Subscribers pay through their existing eSewa or Khalti account via a payment link. No new app, no new account. Payment is confirmed automatically and the subscriber record updates.

Subscriber state management

Active, due, overdue, paused, cancelled — every subscriber's status is maintained in real time. Queryable by the dashboard or by any application via the REST API.

Revenue and collection reporting

Active subscribers, upcoming renewals, overdue amounts, collection history — all in real time. Recurring revenue is visible and accurate without manual tallying.

REST API for integration

The full subscription lifecycle is available programmatically. Build subscription billing into any Nepal product via API — SaaS, ISP portals, CRM, ERP — without building the billing infrastructure from scratch.

A question you're probably thinking about

You want auto-debit. So do we.

Let's be honest about where Nepal's payment infrastructure is — and where it's going.

Right now

Reminder-driven collection. Fully structured.

Auto-debit isn't available in Nepal yet. Banking infrastructure hasn't opened that up. But subscription management is far more than one feature. SUQO handles everything that can be structured right now:

  • Automated SMS reminders before and after renewal dates
  • Payment links sent directly to subscribers
  • Full visibility on who's paid, who's due, who's overdue
  • Collection via eSewa, Khalti, and ConnectIPS
  • Manual recording for cash and bank transfers
Coming

When auto-debit arrives in Nepal, SUQO will have it first.

Nepal's payment infrastructure is evolving. When auto-debit becomes available, SUQO is positioned to integrate it immediately — and you'll already be on the platform.

  • First-mover advantage for businesses already on SUQO
  • No migration — same subscribers, same plans, upgraded flow
  • The subscription infrastructure is already built and running
Two entry points

One infrastructure layer. Two ways in.

Subscription infrastructure looks different depending on whether you're a business owner managing recurring customers or a developer building a product that needs recurring billing. SUQO is the same platform for both — one truth, two entry points.

For businesses: software

Business owners — gym operators, ISPs, coaching centers, insurance agents — use SUQO as subscription management software. The dashboard gives a complete view of every customer, their renewal status, payment history, and outstanding balance. Plans, reminders, and payment collection are managed through the UI. No technical knowledge required. The infrastructure runs invisibly underneath.

For developers and vendors: API

Developers and software vendors use SUQO as billing infrastructure. The REST API exposes the full subscription lifecycle programmatically — create subscribers, manage plans, query billing state, trigger renewals. The dashboard doesn't need to be touched. Your product is the interface; SUQO is the billing layer underneath it. CRM and ERP vendors integrate SUQO once and offer recurring payment collection as a native feature to all their clients.

By industry

Subscription infrastructure across Nepal's recurring-fee economy.

The infrastructure layer is the same across industries. The context — billing cycle, customer relationship, stakes of a missed renewal — varies. Here's how subscription infrastructure fits the highest-priority segments of Nepal's recurring-fee economy.

Frequently asked questions

eSewa and Khalti are payment processors — they handle individual transactions when a customer initiates a payment. SUQO is subscription infrastructure — it manages the recurring cycle above the payment layer: tracking renewal dates, sending automated SMS reminders, collecting via eSewa/Khalti payment links, and maintaining subscriber status. You need both layers for a complete recurring payment system in Nepal.

Functionally, yes — SUQO is Nepal's equivalent of the recurring billing infrastructure that Stripe Billing or Chargebee provides in Western markets. The core distinction is that Stripe and Chargebee are built for card-based payment infrastructure and don't support eSewa or Khalti. SUQO is built specifically for Nepal's payment stack, with eSewa, Khalti, and ConnectIPS as first-class payment methods.

No. eSewa and Khalti process the actual transactions — SUQO sits above them and manages the subscription cycle. When a subscriber pays via a SUQO payment link, the transaction runs through eSewa or Khalti. SUQO handles everything around the transaction: the reminder, the link, the status update after payment. The two layers work together.

Yes. This is one of SUQO's primary use cases. The REST API allows any Nepal software product — CRM, ERP, SaaS, ISP portal — to integrate SUQO as the billing layer underneath. Your product handles the user experience; SUQO handles the recurring billing infrastructure. One integration, deployed across every product that needs it. See the subscription billing API page →

Auto-debit will allow payments to be pulled from a subscriber's digital wallet automatically at renewal — no link click required. When Nepal's payment rails support this, SUQO will expose it through the same API endpoints and dashboard controls. Businesses and products already on SUQO will have auto-debit from day one. The subscription infrastructure layer doesn't change — it gains a new payment collection method.

Build on Nepal's subscription infrastructure. One integration. Every product.

Free to start. Dashboard for business owners. API for developers. KYC required to collect payments.

Free to start  ·  100 SMS credits included  ·  Set up in minutes