UnitPay

been through the stripe duct tape phase twice so this one hit home. the part i actually stopped scrolling on was value receipts. everyone builds the charging side, nobody builds the part where the customers finance person opens the invoice at renewal and decides if it was worth it. that alone probably saves more accounts than any dunning email ever will. qq, can the receipt show things like documents processed or jobs completed instead of raw token counts? tokens mean nothing to the person who signs the renewal. solid launch vijay, the 10 min lovable demo is a smart flex

the margin tracking piece is the part I'd actually pay for, everyone does usage billing eventually but knowing true cost per customer when you're mixing 3 different model providers with their own pricing changes is a much harder problem. how fast does the cost side update when a provider quietly changes their per-token pricing - is that a manual entry on your end or does it pull live rate cards?

"free until $500K ARR" raises a practical question - how is that ARR figure actually determined? is it self-reported, or does UnitPay verify it against the revenue flowing through its own metering, since that's the same system tracking your usage. and when a company does cross the line, is it a clean forward-billing switch on the next cycle, or can it reach back and true-up the months you were technically over the threshold but hadn't been flagged yet

Vijay, the margin-tracking pitch is what got me. WinBidIQ runs its AI summaries/scoring through a multi-provider LLM setup (primary provider with a fallback when quota gets hit), so the actual inference cost per request isn't fixed — it depends on which provider handled that specific call. Does UnitPay's margin tracking capture the real per-request cost when it varies like that, or is it built around a single expected/blended cost per action? That distinction is exactly the kind of thing I'd have gotten wrong building this myself.

Vijay — the line in your intro that jumped out was "what if they upgrade mid-cycle with a negative balance." I run WinBidIQ (AI bid intelligence for U.S. federal contracts), and we meter AI-generated proposal drafts plus daily federal opportunity data pulls per customer. Our version of that problem is fiscal-year-driven usage bursts: a customer can blow through a month's credit allotment in one week chasing an RFP deadline, then go quiet for three. Does UnitPay support any kind of temporary overage/grace buffer before hard-stopping at zero balance, or is it strictly prepaid-and-cut-off?

Hey @vijay_gorfad2, congrats on the launch. I like the AI summary links on the website, cool touch. I modeled some customers to give you some feedback:One of the most common feedback points was that users want automated GAAP compliant revenue recognition mapping that syncs usage to their accounting tools like QuickBooks, Xero, and Sage.A number of users report already using Stripe's Metronome (metronome.com) for AI based usage billing, but uses with data sensitive products (like medical AI) say they would switch to a product that offers a self-hostable VPC gateway option with local event masking.

The part that matters for anyone shipping AI is per-token metering tied to real inference cost and margin in one ledger — most teams bolt Stripe on and never see unit economics until the invoice lands. My one edge case: when usage settles late (an async/batch job whose token cost only resolves hours after the request), does UnitPay reserve credits at request time, or reconcile against the balance at settlement — and what happens if that settlement pushes a prepaid customer negative mid-cycle?

Smart approach. Does it support metered billing rollups at custom intervals, or only monthly?

Congrats on the launch! Billing infra is such an unglamorous but critical piece — we went through our own webhook-idempotency + subscription-state-sync headaches wiring Stripe + Lemon Squeezy for CancelKit's save-offer flow, so I have a lot of respect for anyone tackling usage-based/per-token billing at this level of complexity. Does UnitPay handle its own webhook retries/idempotency, or does it sit on top of Stripe's?

Interesting launch. Like the value receipt. Most billing tools show what a customer spent, almost none show what they got back. Congrats

For the “prove value” part of UnitPay, how are you thinking about the actual proof layer? Is it more around usage and billing data, or do you help AI product teams connect outcomes back to customer-facing metrics too? Curious because pricing an AI agent or workflow tool can get messy fast when token costs, seats, and business value all point in different directions.

Congratulations on the launch! AI pricing is becoming increasingly complex as products combine multiple models and usage patterns. I like that you're tackling both billing and value measurement instead of treating them separately.I'm curious whether teams can define custom pricing metrics beyond tokens, such as API calls, workflows, or business outcomes.

@vijay_gorfad2 Congrats on bringing UnitPay to PH! 🚀For teams with an existing app already using standard Stripe subscriptions, how heavy is the lift to layer UnitPay on top for usage-based credits? Is it plug-and-play alongside Stripe, or does it work best as a complete replacement for the billing pipeline?

The “prove value” part of the UnitPay tagline is the piece I’m most curious about. Is that meant to connect usage-based billing to customer-facing reports, or more for internal teams to understand which AI features are driving revenue? For AI agents and workflow automation tools, the unit of value can be pretty different from app to app, so I’d be interested in how flexible that model is.

Proud to have been part of this journey! 🚀 I've seen firsthand how much thought and effort the team has put into building UnitPay. It's exciting to finally see it live on Product Hunt. Huge congratulations to everyone involved, and wishing you an incredible launch!