Tally
The credit layer API developers actually need
Start new thread
Chukwuemeka Azubuike

Tally - The credit layer API developers actually need

byβ€’
Tally sits between your payment processor and your database. Add, deduct and refund user credits in 3 API calls. Works with Stripe and Polar out of the box. No more rebuilding the same credit logic every time you launch a new product.

Add a comment

Replies

Best
Chukwuemeka Azubuike
Maker
πŸ“Œ
Hey Product Hunt! πŸ‘‹ I'm Chukwuemeka, the founder of Tally. I built this because I kept solving the same problem. Every time I launched a new SaaS β€” whether it was an AI tool, a developer product, or anything usage-based β€” I had to rebuild the same credit infrastructure from scratch. Webhook sync. Balance table. Atomic deductions. Race condition fixes. Refund handling. Idempotency keys. Same code. Every. Single. Time. Tally packages all of that into 3 API calls: β†’ POST /credits/add β€” top up a user after payment β†’ POST /credits/deduct β€” atomic deduction, no double-spend β†’ POST /credits/refund β€” reverse any transaction by ID Point your Stripe or Polar webhook at your app's unique URL. Pass tally_user_id in the payment metadata. Tally handles the rest β€” automatically. What's included: βœ“ Full developer dashboard βœ“ Transaction history and audit log βœ“ Usage analytics per app βœ“ Plan limits and billing built in βœ“ Free to start I'd love your honest feedback β€” especially from developers who've felt this pain. What would make Tally a no-brainer for your stack? Thanks for the support πŸ™