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.
@garyshenk Single points of failure get accepted everywhere in payments in a way they wouldn't in any other part of the stack. That's the gap we're going after. Thanks Gary
@sansa_grey Exactly. It never shows up on a roadmap, it shows up in an email from a risk team
Report
Maker
One major callout: If you run subscriptions, VAMP and GMAP should be on your radar.
It's Visa/MC's monitoring programs: your fraud and dispute counts get combined into one ratio, and crossing the threshold gets your processor fined for keeping you. That's why merchants get dropped "out of nowhere." Most founders hear about it for the first time in a warning email, or sometimes just get dropped with no notice.
PaymentKit attacks both sides of the ratio. Smart routing controls which processor each transaction lands on so no single account's ratio collapses, and can be adjusted in real time based on need. AI-driven dunning recovers failed payments without retry storms that inflate fraud signals. Built-in fraud controls stop disputes before they're born.
We built this running 20+ subscription brands of our own, several in high-risk categories. Ask me anything about VAMP or multi-processor setups.
Report
The independent token vault is a really interesting feature. Great idea for SaaS billing.
I like the idea of making processor choice reversible instead of turning it into a painful migration.
PaymentKit
@andrew_dale2 Reversible is the right word for it. Processor choice should be a decision you can revisit, not a one way door you walk through once
This feels especially useful for SaaS comapanies that cannot afford billing interruptions. Great concept.
PaymentKit
@simonclark55 Thanks Simon!!
A strong solution for companies managing recurring payments. Reducing single points of failure can make a big difference.
PaymentKit
@garyshenk Single points of failure get accepted everywhere in payments in a way they wouldn't in any other part of the stack. That's the gap we're going after.
Thanks Gary
Buffup.AI
Processor lock-in is easy to ignore until something breaks.
PaymentKit
@sansa_grey Exactly. It never shows up on a roadmap, it shows up in an email from a risk team
One major callout: If you run subscriptions, VAMP and GMAP should be on your radar.
It's Visa/MC's monitoring programs: your fraud and dispute counts get combined into one ratio, and crossing the threshold gets your processor fined for keeping you. That's why merchants get dropped "out of nowhere." Most founders hear about it for the first time in a warning email, or sometimes just get dropped with no notice.
PaymentKit attacks both sides of the ratio. Smart routing controls which processor each transaction lands on so no single account's ratio collapses, and can be adjusted in real time based on need. AI-driven dunning recovers failed payments without retry storms that inflate fraud signals. Built-in fraud controls stop disputes before they're born.
We built this running 20+ subscription brands of our own, several in high-risk categories. Ask me anything about VAMP or multi-processor setups.
The independent token vault is a really interesting feature. Great idea for SaaS billing.
PaymentKit
@nolanpierce03 Thanks Nolan! Appreciate it
Multi processor routing makes a lot sense for recurring businesses. Nice launch.
PaymentKit
@darly_selby Thanks!