Seat-based SaaS worked on one assumption. Serving one more user cost almost nothing, so a flat monthly fee covered it.
Inference broke that. Every request carries real compute cost, which pushes AI products toward metered and hybrid pricing whether their founders wanted it or not. A billing stack built to charge the same amount every month cannot meter tokens accurately enough to invoice on.
Payment integration used to mean dropping a gateway SDK into the codebase. Compliance rules, regional payment methods, and constant pricing experiments turned it into an architecture decision. The PaymentKit platform sits between your product and whichever processors, tax engines, or analytics tools you run, combining billing, orchestration, tokenization, dunning, and checkout.
Six situations make that consolidation worth the migration.
1. SaaS Products With Recurring Subscriptions
Subscription businesses grow when customers can start small, upgrade quickly, and downgrade without calling support.
First-generation gateways handle seed stage fine. They usually expose one or two price types and skip trial management entirely. PaymentKit separates price, plan, and feature into independent objects, which lets teams add quarterly plans, student discounts, or grandfathered tiers without a schema migration. Trials, mid-cycle upgrades, pauses, and prorations become parameters rather than new code.
Normalized line-item data flows to finance tools, simplifying revenue recognition under ASC 606. Clean records matter more as volume rises, and AI bookkeeping inherits whatever mess the billing layer produces.
Implementation note. Create Subscription and Preview Invoice return hydrated JSON matching the dashboard, which helps server-side rendering and testing. Plan changes now run through Subscription Change Requests, with Preview Change Request showing the effect first. The older Change Plan endpoint carries a deprecation notice.
2. AI and API-Based Usage Billing
Inference platforms and public APIs cannot predict next month’s consumption.
Revenue mixes a platform fee with metered calls, tokens, or compute seconds. Counters hard-coded into the application layer create two failure modes: double charges when a request retries, and missed usage during an outage. Both erode trust faster than any pricing mistake.
PaymentKit handles this through Meters and meter events. Ingest Meter Event records individual usage, while Ingest Meter Events Batch handles volume. Meters group by metric, customer, and timeframe, apply tiered or volume pricing, and produce draft invoices that finance approves or finalises automatically.
Keeping the meter outside your product database matters. Redefining a metric or changing a sampling interval stops requiring a migration. Get Meter Usage Summary and Get Meter Usage Daily feed a self-service portal, which reduces bill shock, the most common complaint against usage pricing.
Buyers already expect this. AI SaaS buyers increasingly want outcome-linked or consumption-linked contracts rather than flat licences, and a vendor who cannot meter accurately cannot offer either.
3. Businesses Running Multiple Payment Processors
Expansion into new regions brings cross-border fees and payment methods your primary gateway does not support.
PaymentKit’s orchestration layer connects processors through adapters and evaluates currency, issuer country, transaction size, and live success rate before routing. Business users change rules in the dashboard rather than shipping code, which matters during a processor outage.
The platform reports authorization rates rising 10% or more on average after switching, with one customer citing a move from 63% to 76%. Treat vendor-reported figures as directional, though the mechanism is sound: a declined card retried on a second processor sometimes approves.
Because tokens live in PaymentKit’s independent vault, moving a traffic slice to a new provider skips re-collecting cards. Chargeback and settlement data arrive in one normalized schema.
Implementation note. Create Processor Route and Create Routing Rule define the logic. Routing Pins hold a specific subscription on a chosen processor, and Get Processor Route Audit Log records who changed what.
4. Subscription Businesses Fighting Involuntary Churn
Card failures cancel customers who still use the product daily.
A failed renewal moves into past-due and enters a retry schedule timed against the issuer decline code. Recovery emails carry one-click pay links honouring the customer’s saved currency and tax profile. PaymentKit reports failed-payment recovery improving by 12.4% on average.
Growth teams adjust intervals inside a Dunning Profile, so experiments need no deployment. Webhook events push status changes into CRM or Slack, letting account managers intervene on high-value accounts before suspension.
Implementation note. Create Profile defines the recovery sequence, Assign Profile attaches it to plans, and account-level dunning settings control defaults. Recovery metrics surface in the revenue dashboard alongside passive churn.
5. Products That Change Pricing Often
Pricing rarely stays still in a competitive market.
PaymentKit supports flat, volume, graduated, usage, and hybrid models, and more than one can appear on a single invoice. Product managers create or update Price objects in the dashboard, see which customers a change affects, and schedule activation for a specific date.
Testing is where this gets interesting. The Simulations API creates a scenario, advances time forward, and returns a timeline of resulting invoices and subscription states. Teams watch a year of billing behaviour play out before a price reaches production.
Multi-currency plans store daily exchange rates, protecting gross margin from drift. Historical invoices stay intact for audit after a test ends.
Pricing pressure is not unique to software. AI marketing agencies hit the same wall when hourly billing stopped reflecting delivered value, and the fix looked similar: price the outcome, then rebuild billing to support it.
Implementation note. Preview Price returns net, tax, and discount amounts per tier, which powers live calculators in a customer portal. Bulk Migrate Prices moves existing subscribers between price objects.
6. Businesses That Want Portable Tokens
Processor-stored cards lock merchants in, because exporting tokens usually means proprietary formats.
PaymentKit vaults credentials independently and shares network tokens with any connected processor. Finance can renegotiate fees or add a regional acquirer without a re-carding campaign. Enterprise contracts with data-portability clauses get satisfied through an authenticated export.
Apple Pay and Google Pay device tokens map to network tokens, so switching acquirers avoids wallet reauthorization. Token events flow through webhooks, keeping ERP and fraud analytics in sync.
The underlying argument is about leverage. A merchant who can move processors next quarter negotiates differently from one who cannot.
Implementation note. Create Payment Method generates a customer token once, and it attaches to any connected processor. Confirm the vault’s specific compliance certifications with PaymentKit directly if your procurement process requires documentation.
Where This Does Not Fit
Three situations argue for staying put.
A single-product business selling one plan in one currency through one processor gains little. The orchestration layer solves problems it does not have.
Very early-stage products should ship with whatever gateway takes an afternoon. Billing architecture matters once pricing complexity or processor risk appears, not before.
Teams with no finance function to own dunning policies and price experiments will under-use most of the platform. The dashboard removes engineers from the critical path, which only helps when somebody else takes the wheel.
What About Agentic Payments?
Worth watching rather than building for today.
AI agents increasingly initiate transactions on a user’s behalf, which raises questions about authorization, spending limits, and who bears liability for a wrong purchase. Any system letting software spend money needs approval gates and hard ceilings, which is the same discipline AI agent architecture applies to every high-consequence action.
Metering infrastructure built for usage billing happens to be the right foundation. Accurate per-event records and real-time balance visibility are prerequisites either way.
FAQs
Q. What problem does a billing platform solve that a gateway does not?
Gateways move money. Billing platforms manage subscriptions, metering, pricing logic, dunning, and reporting across however many gateways you run.
Q. When should a SaaS company move off its first gateway?
Usually when pricing complexity, multi-currency needs, or processor concentration risk appears. Plenty of teams move after a single processor outage or account review.
Q. How does usage-based billing for AI actually work?
The application sends usage events to a meter. The meter aggregates by customer and period, applies tiered pricing, and generates invoices.
Q. Does switching processors mean customers re-enter cards?
Not when tokens sit in an independent vault above the processor layer. That portability is the main argument for orchestration.
Q. Can pricing changes be tested before going live?
Yes. Simulations advance time against a scenario and return the resulting invoices, so teams see a full billing cycle before shipping.
Q. Is multi-processor routing worth the complexity?
For businesses with cross-border volume or processor risk, generally yes. For a single-market product on one gateway, usually not.
Conclusion
Billing requirements move faster than most codebases.
Subscriptions, usage metering, multi-processor routing, payment recovery, flexible pricing, and token portability each justify a consolidated platform on their own. Together they describe a company that outgrew its first gateway some time ago.
Start with one capability and expand as complexity arrives. Incremental adoption limits risk while returning something measurable early. Then check whether the remaining five map to next year’s revenue plan, because the ones that do are not worth migrating for yet.
