Stripe vs XPay: When to Use Subscription Billing vs Pay-Per-Call

If you're monetizing an API, you need a billing strategy. The two dominant models are subscription billing (Stripe, Recurly) and pay-per-call (XPay, HTTP 402). Each has its place — here's how to choose.

The Subscription Model (Stripe)

Stripe is excellent for subscription billing. It handles recurring payments, invoices, and customer management.

Best for:

• Consumer SaaS products
• Monthly/annual recurring revenue
• Products with predictable usage patterns

Downsides:

• Requires customer payment info upfront
• Overcharges light users, undercharges heavy users
• Complex metered billing setup
• High fees for microtransactions

The Pay-Per-Call Model (XPay)

XPay implements HTTP 402, charging per API request. No subscriptions, no upfront commitments.

Best for:

• API-first products
• Microtransaction billing ($0.001–$0.10 per call)
• Developer tools and infrastructure
• AI/ML API endpoints

Downsides:

• Requires crypto wallet (USDC on Base)
• Newer ecosystem

When to Use Which

FactorChoose StripeChoose XPay User baseConsumersDevelopers Pricing$10–$100/mo$0.001–$0.10/call Payment methodCredit cardUSDC Billing frequencyMonthlyPer request Setup complexityMediumLow (one line of code)

The Hybrid Approach

Some of the best setups combine both: a subscription for base access plus pay-per-call for premium features. With XPay, you can add pay-per-call billing to any existing Stripe subscription.

Bottom Line

Stripe wins for consumer subscriptions. XPay wins for API monetization. Choose the tool that fits your use case — or use both.