Wispr Flow: Dictation That Works EverywhereStop typing. Start speaking. 4x faster.
Promoted
PaymentKit is a multi-processor billing platform for SaaS and e-commerce. It routes payments across processors, vaults tokens independently, and keeps subscriptions billing even if a MID gets shut down. No code to launch, full API when you need it.
PaymentKit
Hey everyone, Diego here from the PaymentKit team.
Quick story on where this came from, because it explains most of the product.
PaymentKit didn't start as a startup idea. We built it for ourselves. Our parent company runs a portfolio of subscription brands, and for years we kept hitting the same three problems: billing lived in one tool, payments in another, and revenue data in a third. Every processor change meant a migration. Every decline was money we never saw again. And all of it sat on top of a single processor whose risk team could change our business overnight.
We couldn't find anything that solved all three together, so we built it and ran our own volume through it before selling it to anyone.
What it actually does:
Payment orchestration: Connect the processors you already use. Every transaction routes to the one most likely to approve it, and soft declines cascade to the next one automatically instead of turning into lost revenue.
Independent vaulting: The part we care most about. Cards, Apple Pay and Google Pay are all vaulted as network tokens under your control, not your processor's. You can add or drop a processor without asking a single customer to re enter anything, and if a MID gets shut down your subscribers never feel it.
Subscription billing: Flat, tiered, usage based or hybrid pricing. Hosted checkout and self service portals, live without writing code.
Revenue metrics: One dashboard across every processor, so you can compare success rates and fees side by side instead of stitching exports together.
What that actually produces: More than 10% lift in authorization rates on average after merchants switch.
It comes from three things stacked: routing each transaction to the processor most likely to approve it, cascading soft declines instead of eating them, and network tokens that keep cards on file alive longer. One merchant went from 63% to 76%. There's also a risk side that most people only learn the hard way. Visa dropped the excessive VAMP threshold from 2.20% to 1.50% on April 1st this year across the US, Canada, Europe and Asia Pacific, and the ratio is measured per MID, not per company. If all your volume sits in one account, one bad month becomes a company level problem. Running multiple processors means you see the ratio per MID instead of hearing about it from your acquirer after the fact, and you can rebalance volume before any single account gets near the line.
Why I think this community in particular might care: a lot of you are running SaaS or digital products on a single processor, or on a merchant of record that owns your customer data and your tokens. That works right up until it doesn't. We're the layer that makes that decision reversible.
It goes live in under an hour on top of what you already have, and there's a free trial if you want to poke at it.
Would really like to hear from anyone who's been through a processor shutdown, a rolling reserve, or a migration that broke their subscriptions. What did you wish existed at that moment?
@diego_vidal10 Upvoted PaymentKit. The independent vaulting is particularly compelling, especially for subscription businesses where processor changes can become painful migrations. The ability to keep customer payment credentials portable seems like a meaningful advantage.
@diego_vidal10 Congrats on the launch, and very cool product! The fact you built this for yourselves first says a lot.
Stripe is working on multi-processor routing, and it's in beta: https://docs.stripe.com/payments/orchestration/route-payments. I'm sure there are differences in the approach, can you explain those? When would it make sense to use Stripe multi-processor vs PaymentKit?
PaymentKit
Thanks @benbartling!! Good question. The main difference is where the vault sits.
With Stripe's orchestration, Stripe stays the system of record. You can route to other processors, but the tokens and the dependency stay with Stripe. With PaymentKit the vault is independent, so no processor is the center of the stack. That distinction matters the day a risk team makes a decision about your account.
The other difference is scope. We're not only routing. Billing, payments and revenue data live in the same place, which was the actual problem we had internally. We're built for the case where you don't want any single processor to be the foundation
Interesting idea, but curious how refunds, disputes, and reporting work when everything is spread across multiple processors.
PaymentKit
@evan_taft1 Refunds run from PaymentKit, full or prorated, and the subscription stays in sync.
Reporting consolidates into one dashboard, so you compare processors side by side on success rate and cost instead of exporting from each one and reconciling by hand.
Disputes are the honest exception. They're resolved by the acquirer that processed that specific transaction, that's how the card networks work, and no orchestration layer changes it. What we do is upstream, with fraud rules that block the transactions most likely to become disputes: country, card brand, card type, amount or BIN, etc. Thanks for taking the time to comment Evan!
@diego_vidal10 Got it, thanks for clarifying. The reporting side makes a lot of sense, especially having everything in one place instead of pulling data from different processors.
The token ownership piece is probably the most interesting part here. Being able to switch processors without impacting existing subscriptions solves a pretty painful problem for subscription businesses.
This could be useful for SaaS companies handling subscriptions across different regions.
PaymentKit
@daniel_carter19 That's one of the clearer use cases. You can route by geography, so EU payments go to one processor and US to another, same integration and same subscription logic (since local acquiring usually approves more)
@diego_vidal10 That makes sense. Being able to route payments by region without changing the whole setup is a pretty useful advantage for SaaS teams expanding globally. Thanks for explaining!
How much control do we get over feedback attempts?
PaymentKit
@jonathan_hayes3 Unlimited control. You can use our smart dunning where our system takes into account time of day, card type, processor, etc and does the retry when the system thinks it's most likely to go through. There's proprietary AI used there. If you want to use a manual, custom schedule you can do that as well.
I’m curious whether routing can be based on processor fees too, orif it's mainly designed for reliability nd availability.
PaymentKit
@lonny_shatzel You can definitely do this. Since you know your bank rates you can have certain cards tried on certain processors first where fees are lower, then have a higher fee processor second or third in priority in your payments routing stack.
Can I test a new processor with a small slice of traffic?
PaymentKit
@violet_amelia Yes. Today you'd do it by carving out a segment with a routing rule, so one country, one card brand or one payment method goes to the new processor, and everything else stays in your default one. Real volume on the new one without betting the whole book