Usage-based pricing (UBP) — billing customers based on what they actually consume rather than a fixed seat or plan — is growing rapidly in Indian SaaS. API platforms, data tools, communication SaaS, AI products, and infrastructure services are increasingly usage-billed. This guide covers how Indian SaaS companies implement usage-based billing for international customers in 2026.
What Usage-Based Billing Is
Instead of "$49/month for the Pro plan," usage-based billing looks like:
- $0.01 per API call
- $5 per GB processed
- $0.005 per SMS sent
- $2 per active user per month (MAU-based)
- $10 per 1,000 AI model calls The customer pays based on actual consumption in a billing period. Bills vary monthly.
The challenge for Indian SaaS: Usage tracking, bill calculation, and payment collection across international customers in multiple currencies — all while maintaining FIRA documentation per charge and settling to INR daily.
Two Usage Billing Models
Model A: Prepaid Credits
Customer buys a block of credits upfront. Credits are consumed over time. When credits run low, customer tops up.
Example:
-
Customer buys $100 credit block
-
Each API call consumes $0.01 in credits
-
After 10,000 API calls, credit is depleted
-
Customer receives low-credit warning at $20 remaining
-
Customer tops up with another $100 block Payment implementation:
-
Fixed top-up amounts ($50, $100, $250, $500)
-
One-time card charge per top-up via Playto Pay (4% flat)
-
FIRA auto per top-up
-
Simpler to implement than metered billing Best for: Most early-to-mid stage Indian SaaS with usage-based pricing. Credit packs are much easier to implement than true metered billing.
Model B: True Metered Billing
At end of billing period, calculate actual usage and charge exactly for what was consumed.
Example:
-
Customer uses 15,342 API calls in March
-
Bill: 15,342 x $0.01 = $153.42
-
Charge $153.42 to card on file on April 1 Payment implementation:
-
Track usage in real-time
-
At billing period end: calculate amount
-
Generate invoice for the calculated amount
-
Charge stored card via payment platform Challenge: Variable amounts per charge require payment infrastructure that can charge arbitrary amounts to a stored card. Playto Pay handles this for moderate complexity.
For complex metered billing at scale: Stripe Billing's metered feature is the most capable tool available, with native usage record API. Requires US LLC for Indian companies.
Implementation on Playto Pay
Credit pack billing (recommended for most):
-
Create fixed-denomination "top-up" products in Playto Pay ($50, $100, $250, $500 credit packs)
-
Customer selects top-up amount and pays via card (4% flat) or UPI (0% for INR credit packs)
-
FIRA auto-generated per purchase
-
Credits added to customer's account balance in your database
-
Consumption tracked in your system; credits deducted per API call/action
-
Low-balance alert triggers top-up notification to customer Variable metered billing:
-
Track usage in your system throughout billing period
-
At period end: calculate customer's bill
-
Generate Playto Pay payment link for the calculated amount
-
Auto-charge via stored card-on-file (requires Playto Pay's subscription/tokenization flow)
-
FIRA auto-generated per charge
FIRA for Usage-Based Billing
Each usage-based charge to an international customer generates a FIRA. For a customer making 3 top-ups per month: 3 FIRAs/month.
At 200 international customers averaging 2 top-ups/month: 400 FIRAs/month.
Playto Pay auto-generates all FIRAs. Manual process would be unworkable at this scale.
Pricing International Usage vs Indian Usage
Same price globally or PPP-adjusted?
For most API/infrastructure pricing: same price globally in USD makes sense. The usage cost (API infrastructure, compute) is your cost in USD terms. Discounting for Indian users means subsidizing each API call, which compounds at volume.
Exception: If you're building for Indian enterprises specifically (and international is secondary), INR pricing with a separate USD tier is workable.
Minimum charges: For usage-based billing, set a minimum monthly charge (e.g., $5 minimum even if usage is $2) to make small accounts economically viable.
Customer Communication for Variable Bills
Variable bills create customer friction. Reduce with:
Real-time usage dashboard: Show customers their current period consumption and estimated bill at any time.
Usage alert notifications: Email when customer reaches 50%, 75%, 90% of their typical monthly usage or credit balance.
Monthly bill preview: 5 days before billing date, send "Your estimated bill for [month] is $[X]."
Detailed invoice: Line items showing usage categories and amounts. Reduces support requests and disputes.
When to Move to Stripe for Usage Billing
Playto Pay handles credit pack billing well. For complex true metered billing at growth stage:
Move to Stripe if:
-
You need Stripe's native metered billing API (usage records per customer per timestamp)
-
Your billing complexity requires Stripe Billing's revenue recognition and invoice automation
-
You're above $10K monthly and have US LLC already incorporated
-
Enterprise US customers expect Stripe-generated invoices with USD billing Playto Pay is sufficient for:
-
Credit pack top-up billing (most common usage-billing model in Indian SaaS)
-
Simple metered billing via payment-link-per-period approach
-
Hybrid models (base subscription + usage overage)
-
Below $10K MRR or without US LLC
FAQ
How do Indian SaaS companies implement usage-based billing without Stripe? Credit pack model: sell fixed credit blocks ($50/$100/$500) via Playto Pay payment links. Track consumption internally. Trigger top-up notifications when credits run low. Simpler than true metered billing and works on Playto Pay.
Can Playto Pay handle variable monthly billing amounts? Yes for credit pack top-ups (customer initiates) and manually triggered payment links. For fully automated metered billing at scale with variable amounts: Stripe's metered billing API is more purpose-built.
Does FIRA apply to each usage top-up from an international customer? Yes. Each payment from an international customer is a foreign inward remittance requiring FIRA. Playto Pay auto-generates per charge.
Should Indian SaaS price usage the same for Indian and international customers? For API/infrastructure usage: same USD price globally is usually simplest and most defensible. INR pricing for Indian customers makes sense if Indian market is primary and you're building specifically for Indian use cases.
At what revenue level should Indian usage-based SaaS move to Stripe? When you've incorporated Delaware C Corp (typically for fundraising) and your metered billing complexity genuinely needs Stripe's metered billing API. Below these conditions, Playto Pay's credit pack approach handles most usage-billing needs.