The pattern mature SaaS platforms recognize too late
A SaaS platform launches. Payments are added — Stripe, or a BaaS provider, or a processor chosen for developer experience and speed. The product grows. The platform now processes $5M, $10M, $20M monthly in payment volume.
Somewhere in a finance review, someone calculates the effective take rate on payments. It is 15–30 basis points. A conversation with an operator who has done this before reveals that well-designed programs at the same volume generate 80–120 basis points. The gap is $500,000–$1,500,000 annually in economics that the platform is not capturing.
This is the moment that triggers the economics recovery conversation. The platform has been leaving money on the table since it launched, and the question now is: what does recovery actually look like?
Diagnosing before recovering
Economics leakage in a live payment program comes from several sources, and the recovery strategy differs depending on which ones apply. Treating all leakage as the same problem — "we need to switch processors" — is the most common mistake in the recovery process.
The four primary leakage sources for mature SaaS platforms, in order of frequency:
Processor spread. Flat-rate pricing (Stripe, similar) creates a silent margin capture by the processor on every transaction. Recovery requires migrating to interchange-plus pricing, either with the existing processor or a new one. This is the lowest-complexity change with the most immediate economics impact.
BaaS middleware margin. If the platform is on a BaaS program (Synapse, Unit, Treasury Prime, Synctera), the middleware is taking a share of interchange before it reaches the platform. Recovery requires renegotiating the BaaS agreement or migrating to a more direct model. Timeline: 6–18 months depending on contract terms and integration complexity.
Float economics uncaptured. Customer balances in FBO accounts are generating yield that the bank or BaaS provider is retaining. Recovery requires renegotiating float terms — often possible without changing the program model. Timeline: 1–3 months with the right sponsor bank relationship.
Level 2/3 data not transmitted. B2B card volume is not receiving the interchange optimization available when enhanced data is transmitted. Recovery requires processor configuration changes. Timeline: 2–6 weeks with processor cooperation.
The recovery sequence that works
The correct recovery sequence moves from lowest-complexity changes to highest. This matters because each stage funds and validates the next.
Stage 1 (weeks 2–6): Transmit Level 2/3 data on all eligible B2B card transactions. This is a processor configuration change with near-zero integration risk. For B2B-heavy platforms it generates 30–50 basis points of immediate improvement. No program model change required.
Stage 2 (weeks 4–12): Migrate from flat-rate to interchange-plus pricing. Either renegotiate with the existing processor or move to one that supports interchange-plus. This requires re-underwriting and potentially customer re-enrollment but no sponsor bank change. Generates 20–60 basis points depending on card mix.
Stage 3 (months 2–6): Renegotiate float economics with the sponsor bank. This is a contractual negotiation, not a technical migration. Float yield on customer balances is available in most sponsor bank relationships but is not surfaced without asking. Generates material yield income at meaningful balance levels.
Stage 4 (months 6–18): Evaluate program model migration — BaaS to direct, or restructuring the sponsor bank relationship for better interchange terms. This is the highest-complexity recovery stage and should only be undertaken after Stages 1–3 are implemented, because those stages validate the economics case for the deeper investment.
What to avoid
The most expensive recovery mistake is starting at Stage 4 — treating the solution as a program model migration before diagnosing which specific leakage sources apply. Many platforms spend 12–18 months on a full program restructuring when the majority of the economics gap was recoverable in Stages 1 and 2.
The second most expensive mistake is recovering economics without designing for what comes next. A platform that migrates from BaaS to direct, captures the improved economics, but doesn't design the compliance framework and operating model for the next stage of growth will find itself back in the same conversation 24 months later.
If your payment program is live and the economics aren't where they should be, the leakage calculator can estimate your gap by leakage category. Or talk with us directly — we can usually identify which stages apply to your program in 30 minutes.