# Payments for SaaS and subscription businesses

Recurring billing that keeps cards working. Orchestrapay retries failed renewals on a second processor, keeps saved cards fresh with network tokens and the account updater, and runs billing on any processor you connect.

Page: https://www.orchestrapay.com/industries/saas

## Keep every renewal you have already earned.

Failed renewals quietly cancel customers who meant to stay. Orchestrapay keeps saved cards current, retries declines on another processor, and runs your billing on whichever processor approves.

## Where subscription revenue leaks.

- **Renewals fail on cards that were fine last month.** Cards expire, get reissued or hit a soft decline on renewal day. Each failure is a subscriber you lose without them choosing to leave. Fixed by [Recover renewals & reduce churn](https://www.orchestrapay.com/solutions/recover-renewals.md): Updated card details, network tokens and retries on a second processor, working together.
- **Saved cards go stale.** A card stored a year ago may have a new number and expiry today, and nobody told your billing system. Fixed by [Card Account Updater](https://www.orchestrapay.com/products/card-account-updater.md): Reissued cards update themselves in your vault before the next renewal.
- **One processor decides your churn rate.** When your only processor declines a renewal, there is nowhere else to send it. Fixed by [Smart Routing](https://www.orchestrapay.com/products/smart-routing.md): Cascade a declined renewal to a backup processor automatically.
- **Billing is welded to your processor.** Plans, invoices and coupons usually live inside the processor, so changing processor means rebuilding billing. Fixed by [Billing & Invoicing](https://www.orchestrapay.com/products/billing.md): Subscriptions, plans, invoices and a billing portal that charge through any processor.

## From signup to the hundredth renewal.

1. **Capture the card once.** The customer subscribes through the Orchestrapay payment form. The card goes into a vault you own.
2. **Bill on schedule.** Plans and invoices charge the saved card on renewal day, through the processor your routing picks.
3. **Recover what fails.** A decline cascades to a backup processor, and reissued cards are refreshed before they fail again.

## FAQ

**Can I keep my current billing system?** Yes. You can charge saved cards from your own billing logic through the API, or move plans and invoices to Orchestrapay Billing. Either way the cards live in your vault.

**What happens when a renewal is declined?** Your routing rules decide. A typical setup sends soft declines to a second processor straight away, so the renewal is approved without the customer doing anything.

**Do customers need to re-enter their card if I change processor?** No. Saved cards stay in your Orchestrapay vault and can be charged on any processor you connect.

**How do network tokens help subscriptions?** A network token is updated by Visa or Mastercard when the card is reissued, so a renewal keeps working after the plastic changes.

**Can customers manage their own subscription?** Yes. The billing portal lets customers update their card, see invoices and manage their plan.

## Related

- [Recover renewals & reduce churn](https://www.orchestrapay.com/solutions/recover-renewals.md)
- [Billing & Invoicing](https://www.orchestrapay.com/products/billing.md)
- [Network Tokens](https://www.orchestrapay.com/products/network-tokens.md)
- [Talk to sales](https://www.orchestrapay.com/contact)