Trile Documentation

Recurring payments for Nepal. Nepali banks don't support auto-billing — Trile does, through a customer wallet that deducts on every cycle.

Quickstart API Reference

What is Trile?

Trile is subscription billing infrastructure for Nepal — a Stripe-analog for a market where no payment provider supports recurring charges and banks don’t offer Variable Recurring Payments. SaaS businesses integrate the Trile API to accept auto-renewing subscriptions; their customers fund a Trile wallet (via eSewa, Khalti, bank transfer, or IME Pay) that auto-deducts on every billing cycle.

Wallet-funded billing

Customers top up a wallet; subscriptions deduct from it each cycle. No card-on-file, because Nepal has no card rails for recurring charges.

One API, three auth modes

API keys for your server, phone+OTP for end users, email+TOTP for the merchant dashboard.

Money done right

Every amount is integer paisa (NPR × 100), serialized as a string. No floats, ever.

Built for correctness

Mandatory idempotency keys, signed webhooks, an append-only event log, and daily balance reconciliation.

Start here

How Trile works The wallet → subscription → invoice flow, end to end.

Quickstart From API key to your first live subscription in ~10 minutes.

Authentication API keys, sessions, and test vs. live mode.

API Reference Every endpoint, generated from the live OpenAPI spec.