# Subscription Payment Gateway: How to Pick One for Your SaaS

> Subscription payment gateway buyers guide for SaaS founders. What features matter, how PSPs differ from MoRs, and how to evaluate by stage and geography.
- **Author**: Ayush Agarwal
- **Published**: 2026-06-09
- **Category**: Payments, SaaS, Subscriptions
- **URL**: https://dodopayments.com/blogs/subscription-payment-gateway-saas

---

A subscription payment gateway is a payment platform that supports recurring charges, not just one-time payments. It stores customer payment credentials securely, charges them on a schedule, handles failures with retry logic, and integrates with subscription billing logic (proration, trials, upgrades, cancellations).

Almost every modern payment platform claims subscription support, but the depth varies dramatically. This guide breaks down what subscription gateways actually do, the features that matter for SaaS, and how to pick the right one for your stage and geography.

## What "subscription support" really means

At a minimum, a subscription payment gateway needs to:

- Store payment credentials (card, wallet, bank) securely with the customer's authorization
- Initiate charges on a defined schedule (monthly, annual, custom)
- Handle failed charges with retry logic
- Update the credential when the underlying card expires or is replaced
- Notify your application of subscription events via webhooks

That is the floor. Many SaaS use cases need significantly more:

- Proration when customers upgrade or downgrade mid-cycle
- Trial period handling with automatic conversion to paid
- Cancellation flows (immediate, end-of-period, custom)
- Multiple subscription products per customer (cross-sells, add-ons)
- Usage-based billing (metering, calculating overages)
- Customer portal for self-serve plan changes
- Tax calculation at renewal time
- Dunning workflows with branded communications

A "supports subscriptions" checkbox can mean any of these. Evaluate by feature, not by category claim.

## The three real categories

### 1. Pure payment gateways with subscription primitives

Platforms like Authorize.Net or Worldpay have basic recurring billing functionality. They can store a card and charge it on a schedule. They do not handle billing logic (proration, trials, plan changes), so you build that on your side.

**Fit**: Legacy enterprise that already has a custom billing engine.

### 2. PSPs with native subscription billing

Platforms like Stripe, with Stripe Billing layered on Stripe payments. They handle the full subscription lifecycle inside their product. You configure plans, set up customers, and the platform manages the rest. Stripe Billing on the Starter and Scale plans charges 0.5% to 0.8% on recurring revenue on top of payment processing.

**Fit**: Most SaaS startups and mid-market. Strong default choice.

### 3. Merchant of record platforms with subscriptions

Platforms like Dodo Payments and Paddle act as the legal seller and handle subscription billing, payment, tax, and compliance as a single integrated product. The MoR is the customer's seller of record, handles VAT/GST/sales tax registration and filing across 190+ jurisdictions, and pays you out as the underlying supplier.

**Fit**: Global SaaS that wants tax and compliance handled, or SaaS in regulated industries where seller-of-record obligations are heavy.

## Features that actually matter

### Smart retries on failed payments

Card failure rates run 5% to 10% on first attempt for monthly subscriptions. Smart retry logic recovers 60% to 80% of those failures. Platforms vary in retry quality:

- Basic: retries failed cards on day 1, 3, 7
- Better: retries with intelligent timing (when funds are likely available)
- Best: retries combined with branded customer communication and self-serve update links

A weak retry system can cost a SaaS 3% to 5% of revenue per year in unnecessary involuntary churn.

### Account updater integration

Cards expire and get replaced constantly. Account updater services (Visa Account Updater, Mastercard Automatic Billing Updater) automatically refresh stored credentials without customer involvement. A subscription gateway without account updater integration loses 1% to 2% of revenue per year to credentials going stale.

### Proration

When a customer upgrades from $50/month to $100/month on day 15, do they pay the full $100 next cycle, a prorated charge today, or some hybrid? Subscription platforms differ in how flexible they are. For B2B SaaS with frequent plan changes, proration depth matters.

### Multiple subscriptions per customer

A customer might have a core subscription plus optional add-ons (extra users, API calls, premium features). The gateway should support multiple parallel subscriptions billed on the same customer record without duplicating customer data.

### Webhook reliability

Subscription events (created, renewed, payment failed, canceled) need to fire reliably. A platform that drops 1% of webhook events will silently leak revenue or create stale customer records. Test webhook delivery aggressively before committing.

### Customer portal

A hosted portal where customers can update payment method, change plan, view invoices, and cancel reduces support burden dramatically. Building this yourself is 1 to 3 engineer-weeks of work. A subscription platform that includes it is meaningful leverage.

> The features that look the same in a vendor matrix often have 10x quality differences in practice. Smart retry quality alone can swing involuntary churn by 3 percentage points. Test what matters with real data before signing.
>
> \- Ayush Agarwal, Co-founder & CPTO at Dodo Payments

## What changes by SaaS stage

### Pre-revenue to first 100 customers

The right move is the fastest integration that does not box you in later. Stripe Billing or [Dodo Payments subscriptions](https://docs.dodopayments.com/features/subscription) cover almost every common pattern with a hosted checkout in hours. Avoid building custom billing logic at this stage.

### $20K MRR to $200K MRR

Conversion optimization starts to matter. Local payment method coverage matters if international customers are a significant share. Tax compliance starts to bite if you have sold into 10+ countries. This is the stage where MoR economics often beat PSP economics on a total-cost-of-ownership basis.

### $500K MRR and above

Custom billing logic starts to pay back. Volume-based pricing negotiations with PSPs become available. Tax compliance is either a dedicated function or fully outsourced. Hybrid setups (multiple gateways, MoR for some geographies, direct PSP for others) become viable.

## Geography considerations

### US-domestic only

A PSP is usually enough. Stripe Billing covers most needs. Tax compliance is the 45-state sales tax patchwork; a tax service like Stripe Tax, TaxJar, or Avalara can handle it.

### EU and UK heavy

VAT compliance is non-trivial. SCA (Strong Customer Authentication) requirements add friction to recurring charges. An MoR that absorbs VAT registration and SCA handling is often the cleanest path.

### India, Brazil, Southeast Asia, LATAM

Local payment methods (UPI, PIX, Boleto, OXXO, GrabPay, etc.) matter for conversion. Cards alone underperform. A platform with deep local method coverage and local entity status is significantly better than a US-centric PSP.

### Truly global SaaS

A platform that operates as merchant of record across 220+ countries and supports 30+ local payment methods (such as Dodo Payments) lets you ship one integration and accept payments globally. The alternative is multiple regional integrations.

## Cost comparison framework

Compare apples-to-apples by computing total cost of ownership over 12 months:

| Cost Component | PSP | PSP + Tax Tool | MoR |
|---|---|---|---|
| Payment processing | 2.9% + 30c | 2.9% + 30c | 4% + 40c |
| Subscription billing fee | 0.5% to 0.8% | 0.5% to 0.8% | Included |
| Tax calculation | Add 0.5% | Add 0.5% | Included |
| Tax registration + filing | $0 (DIY) or $5K-$50K/year | $5K-$50K/year | Included |
| Chargeback handling | DIY | DIY | Included |
| Local payment method gaps | Real revenue loss | Real revenue loss | Covered |

For a global SaaS, the MoR headline rate often comes out cheaper all-in once tax and compliance are factored in.

## Migration friction

Switching subscription platforms is painful. The main friction:

- Card migration (PCI-compliant transfer of stored credentials, not all gateways support this)
- Webhook event continuity (subscription state has to be reconciled)
- Customer notification (the bank statement might change appearance)
- Tax compliance handoff if changing the legal seller (MoR transitions)

This is why the initial choice matters. Picking a platform you will outgrow at $500K MRR is acceptable. Picking one you will outgrow at $50K MRR creates a migration crisis at the worst time.

## A quick decision flow

```mermaid
flowchart TD
    A[Need subscription billing] --> B{US-only or global?}
    B -->|US-only, simple| C[Stripe Billing]
    B -->|US-only, complex| D[Stripe Billing + Stripe Tax]
    B -->|Global| E{Want tax handled?}
    E -->|Yes, ship faster| F[MoR like Dodo Payments]
    E -->|No, large finance team| G[Stripe Billing + Avalara / TaxJar]
```

## FAQ

### What is a subscription payment gateway?

A payment platform that supports recurring charges, not just one-time payments. It stores payment credentials, charges customers on a schedule, retries failed payments, and integrates with subscription billing logic (proration, trials, plan changes).

### Is Stripe Billing a subscription payment gateway?

Yes. Stripe Billing layers subscription functionality on top of Stripe payments. Pricing is 0.5% to 0.8% on recurring revenue on top of payment processing, depending on plan.

### What is the difference between a subscription gateway and a merchant of record?

A subscription gateway processes recurring payments for you. A merchant of record (MoR) is the legal seller and additionally handles tax registration and filing, chargeback liability, and compliance. MoRs cost more headline but absorb more operational burden.

### How important is smart retry logic?

Very. Card failure rates run 5% to 10% on first attempt for monthly subscriptions. Smart retries recover 60% to 80% of those failures. A weak retry system can cost a SaaS 3% to 5% of revenue per year in involuntary churn.

### What is the best subscription gateway for global SaaS?

For global SaaS that wants tax and compliance handled, a merchant of record like [Dodo Payments](https://dodopayments.com) is typically the cleanest option. It supports 30+ local payment methods across 220+ countries and regions with tax handled in 190+ jurisdictions.

## Conclusion

Subscription payment gateways vary far more in quality than category claims suggest. The right platform depends on stage, geography, and whether you want tax and compliance handled for you or you have the team to do it yourself.

If you want global subscription billing with payment, tax, and compliance bundled, see [Dodo Payments](https://dodopayments.com) and [pricing](https://dodopayments.com/pricing).
---
- [More Payments articles](https://dodopayments.com/blogs/category/payments)
- [All articles](https://dodopayments.com/blogs)