Allow Authorize.net (or other payment processors) at the Agency SaaS level — not just V2 SaaS
T
Trevor Berke
While Authorize.net and NMI support has been added for V2 SaaS mode, this doesn’t help agencies already running clients under the original Agency SaaS plan using Stripe.
What’s still missing:
We need the ability to use Authorize.net (or NMI, etc.) for SaaS re-billing at the Agency level, just like Stripe currently is.
----
⚠️ Why this matters:
There is no clean way to migrate existing clients from an Agency SaaS plan (re-billed via Stripe) to a V2 SaaS plan (billed via Authorize.net). Here’s why:
• Clients must go through a new checkout for the new V2 SaaS plan.
• Agencies must then create custom automations or use Zapier to provision the new sub-account.
• Even if we use snapshots to copy their old sub-account, not everything transfers over.
• The client now has to abandon their old account and operate from a new one — which is disruptive and often a non-starter.
For agencies, this means a logistical nightmare and a poor client experience, just to change the payment processor.
----
✅ The Ideal Solution:
Allow Authorize.net (or NMI) to be used directly at the Agency SaaS level, just like Stripe.
This would enable us to:
• Keep clients on their existing sub-accounts
• Switch billing processors without rebuilding their setup
• Ensure continuity and simplicity for both agency and client
----
This would save dozens of hours of work for each migration and help agency owners avoid the risk of Stripe’s shutdowns, rolling reserves, or geographic limitations — without needing to rework every client relationship from scratch.
Please consider this a vital feature for long-term platform sustainability and flexibility. Happy to collaborate or provide more specifics.
Log In