Framer AI AgentsDesign and publish professional sites with AI
Launching today
PaymentKit
Billing that survives a processor shutdown
658 followers
Billing that survives a processor shutdown
658 followers
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.
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?
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.
I've dealt with payment migrations before. getting customers to update cards is painful, so this solves a real headache.
PaymentKit
@grant_w1 Exactly it. Card re collection is where most migrations quietly die. With network tokens under your control the customer never sees a new form
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)
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
Can recurring billing switch processors without touching customers?
PaymentKit
@yara_simone Yes, that's the core of it. The tokens are vaulted with us as network tokens instead of living inside the processor, so the next renewal just runs on the new one. No email, no update card form, no re-authentication. From the customer's side nothing happened
Independent vaulting is the claim I'd want spelled out. Network tokens are provisioned against a token requestor, so whether they're portable depends entirely on who the requestor of record is, and Apple Pay and Google Pay DPANs make that messier rather than cleaner. If it's you and not the processor, put that sentence on the page, it's the difference between a real escape hatch and a vault you still can't leave with. Worth naming which processors you've actually moved live volume between too, not which ones you support.