How do I migrate client billing after Synthflow removed reselling?

How do I migrate client billing after Synthflow removed reselling? Move client charging to your own Stripe account or another billing system, reconcile each client’s paid period and outstanding balance, then test the replacement before enabling live charges. You can keep calls running in Synthflow while changing billing, or evaluate a different platform if you also want to change how you deliver the service.

Synthflow removed in-product reselling on 15 September 2026. Its removal notice concerns charging clients through Synthflow, not a blanket end to running an agency or commercially reselling services. Your own Synthflow subscription and parent minute pool were unchanged. Synthflow’s reselling guide

What changed, and which clients are affected?

The affected setup used your Stripe account with Synthflow’s custom pricing plans. Synthflow removed that integration and the pricing plans; customer subscriptions relying on the feature stopped working. Subaccount billing and usage pages were also removed. Subaccounts, branding, custom domains and permissions continue. Synthflow’s Stripe notice

Identify clients on those plans, including trials and overage arrangements. If you already invoiced externally without custom pricing plans, do not rebuild billing solely because of this announcement.

Do I have to move my agents too?

No. There are two separate decisions:

• Keep Synthflow for calls: operate client billing externally and maintain the required usage controls. Synthflow documents subaccount limits and usage reporting through its API, post-call webhooks or call history. Auto-overage can let usage exceed the allocation at your expense; it does not charge the client for you. Reselling migration guidance
• Move service delivery as well: evaluate the replacement’s agent behavior, integrations, telephony and billing independently. A billing change does not prove that another platform can import your agents or reproduce every workflow.

1. Build a client-by-client reconciliation sheet

Before changing anything, record:

• Client and subaccount identifiers, plus the corresponding Stripe customer and subscription identifiers
• Currency, price, billing frequency, renewal date and paid-through date
• Included usage, measurement window, timezone and overage rate
• Trial end, discount, prepaid balance, credit, refund and unpaid invoice status
• Last successful payment, final old-system usage reading and intended new billing start
• Person responsible for review, cutover status and any unresolved exception

Keep an original snapshot and a separate working copy. Use account references rather than copying card data or credentials. Verify subscription status and scheduled invoices directly in your billing account; a disconnected integration is not enough evidence that no charge can occur.

2. Decide what to reuse and what to recreate

Treat your existing records as reconciliation evidence, not proof of automatic portability. Check which customers, prices and payment methods remain usable in your own Stripe account and what the replacement integration supports before creating anything new.

Recreate or explicitly map the client’s offer, billing schedule, usage rules, portal access and account identifiers. Do not assume connecting Stripe imports subscriptions or preserves renewals, discounts and balances. Where a different processor or Stripe account is involved, payment-data migration requires its own supported process. Stripe’s migration guidance

If you also move agents, plan to rebuild and test unsupported settings and integrations. Verify phone-number ownership and routing separately. Do not promise that historical calls, recordings, credentials or agent configurations transfer automatically.

3. Test the billing before collecting money

Choose one representative client configuration and use a test environment or non-charging invoice preview. Compare the expected bill with the replacement calculation for:

• A normal renewal and a client halfway through a paid period
• Usage above the allowance and a prepaid credit
• A trial or discount ending
• A failed payment and the intended service-access response

Keep the existing service available while testing. Parallel testing means comparing calculations, not running two live subscriptions. Confirm units, rounding and time boundaries, and ensure a repeated usage event cannot create a second charge.

Preview prorations and renewal dates explicitly: Stripe documents that subscription changes can create prorations and that billing-cycle configuration affects when customers are charged. Prorations · Billing cycles

4. Cut over once, then reconcile the first invoice

Choose an exact cutoff timestamp. Assign usage before it to the old billing window and usage after it to the new one. Explain the billing change, next charge date and any required customer action; obtain any required agreement or payment authorization before charging.

Review old scheduled charges and pending invoices before enabling replacement collection. Record credits separately from usage allowances: a client’s cash credit, a Synthflow minute allocation and VoiceAIWrapper native AI credits are different balances. Do not convert or transfer them automatically.

After cutover, check the first invoice, actual payment, usage totals and client access. Keep mismatches in an exception list and pause incorrect collection while resolving them. Retain the records needed to explain the transition. Do not delete the old setup until reconciliation is complete.

Where does VoiceAIWrapper fit?

VoiceAIWrapper supports branded client portals and client billing through your own Stripe account, with native AI and supported bring-your-own-key options. Review white-label AI SaaS with client billing and test your intended billing setup before migrating clients.

PayasYouGo has no fixed subscription fee: the first client portal is included, with additional portals at $20/month each. Scale is $499/month with 20 portals included and additional portals at $12/month each. 24/7 support is available on Scale only. Scale includes 70,000 native AI credits per month, approximately 10 hours depending on the model and configuration; additional native usage requires credit top-ups. BYOK provider usage, telephony and applicable add-ons are charged separately. Check current pricing for the complete cost.

Start with one client’s tested billing and service configuration, then expand after its first invoice reconciles correctly.