我厌倦了为了接受支付而阅读五份不同的API文档。

2作者: devodii1 天前原帖
我创建Paykit是因为每次需要集成支付时,我都厌倦了阅读新的API文档。<p>Stripe、Paddle、PayPal、Polar,它们都有稍微不同的模型、Webhook和仪表板。如果你经常发布小项目或在多个平台上处理支付,这真的很烦人。<p>Paykit为你提供: • 一个可以与所有平台兼容的SDK。 • 一个用于收入、客户和Webhook的统一仪表板。 • 一个简洁的REST API,让你可以根据需要构建自己的用户界面。 • 开箱即用与shadcn/ui兼容,随时查看文档获取复制粘贴的代码片段,以便在几分钟内完成完整的支付集成。<p>即将推出的V2版本包括:发票生成器、月 recurring 收入截图工具(让你可以展示你的增长)以及为没有账单门户的平台提供的托管账单门户。<p>虽然还处于早期阶段,但可以在这里访问:https://usepaykit.dev<p>非常希望能得到反馈,特别是来自那些在集成多个支付平台时感受到这种痛苦的开发者。
查看原文
I built Paykit because I got tired of reading a new API doc every time I needed to integrate payments.<p>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.<p>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&#x2F;ui out of the box, feel free to check the docs for copy-paste code snippets to handle full payment integration in minutes.<p>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.<p>It’s still early, but live here: https:&#x2F;&#x2F;usepaykit.dev<p>Would love feedback, especially from other devs who’ve felt this pain integrating multiple payment platforms.