I'm tired of reading five different API docs just to accept payments
I built Paykit because I got tired of reading a new API doc every time I needed to integrate payments.
Stripe, Paddle, PayPal, Polar, they all have slightly different models, webhooks, and dashboards. It’s annoying if you ship a lot of small projects or handle payments across multiple platforms.
Paykit gives you: • One SDK that works with all of them. • One dashboard for revenue, customers, and webhooks. • A clean REST API so you can build your own UI if you want. • Works with shadcn/ui out of the box, feel free to check the docs for copy-paste code snippets to handle full payment integration in minutes.
Coming in V2: invoice builder, MRR screenshot tool (so you can flex your growth), and hosted billing portals for platforms that don’t have one.
It’s still early, but live here: https://usepaykit.dev
Would love feedback, especially from other devs who’ve felt this pain integrating multiple payment platforms.
https://xkcd.com/927/
But then they would have to be vendor locked to you and send all the payment information through your service. Absolutely no security conscience customer would go for it.
Can't you use stripe for everything?
Your post should be a Show HN:
Probably not if your client dictates what provider they want to use.
And in that case, would your client really want a dependency on a libration/service from an unknown indie developer when it comes to processing payments? This wouldn’t pass muster from any security audit.