Payment orchestration for SaaS and subscriptions

What goes wrong without orchestration

• A renewal is declined for insufficient funds at three in the morning, nobody retries it, and the customer is cut off by breakfast.
• The vendor’s only acquirer loses a card BIN range, and every subscriber of that bank churns in the same week.
• Finance cannot say which charge, retry or refund belongs to which subscription without exporting three dashboards.

What orchestration changes

Recurring charges by a stored token on Visa, Mastercard, Apple Pay, Google Pay and UPI; the first payment with 3-D Secure, the renewals as merchant-initiated charges; retries of a declined renewal on a schedule before the subscription is cancelled; routing of the first payment by BIN and country to the acquirer that approves it, with cascading on a decline; SEPA Instant for annual invoices and top-ups in the EU; every charge, retry, refund and chargeback journaled for five years with a trace. The vendor’s PSP enables the methods from the catalogue; the licensed provider settles the funds.

Recurring payments

• Cards and wallets: Visa and Mastercard, Apple Pay and Google Pay — recurring in every market of the catalogue; an expired card is marked before the renewal date, not on it.
• India: UPI with a mandate for the subscription; payouts and refunds on the same rail.
• EU: SEPA Instant for invoices and top-ups; no scheduled charges.