We're building Chaser because we got incredibly frustrated with how standard dunning and billing recovery tools treat customer relationships.
Most platforms blindly spam automated emails the second a payment fails. But if a temporary bank decline or insufficient funds glitch hits a high-value enterprise contract or a VIP account, aggressive automated pestering risks burning precious relationship equity.
We built Chaser to fix this balance. It pairs an optimized, multi-day adaptive retry engine for standard users with an explicit "Human-in-the-Loop" safety net queue. When an enterprise account hits a billing snag, Chaser holds the automation back, drafts a warm, concierge-toned personal message via AI, and flags it for an operations lead or founder to review and send with 1 click.
Because we are dealing with sensitive billing infrastructure, security was our baseline requirement, not an afterthought:
- We treat credential safety with absolute isolation infrastructure.
- Stripe API keys and webhook tokens are securely sandboxed, fully encrypted, and strictly isolated with owner-only Row Level Security (RLS) database policies.
- No customer credit card data is ever seen or stored by our systems; Stripe handles the financial vaulting entirely.
We are currently 2 weeks away from opening our closed beta. We built the entire front-end tour to be fully interactive so you can play with a live sandboxed command center, and see the sequence timeline analytics without needing to hook up your own data yet.
For the HN community, if you want to jump into the closed beta, just drop a message to our support queue inside the app mentioning "HN 90" and we’ll manually upgrade your backend account to an extended 90-day free trial so you can run it through three full billing cycles.
I would love to get your brutal feedback on the workflow logic, the interactive sandbox UX, and our approach to handling automated vs. manual billing queues!
Chaser – Stripe-native revenue recovery with a human-in-the-loop queue · HackerTrans
We're building Chaser because we got incredibly frustrated with how standard dunning and billing recovery tools treat customer relationships.
Most platforms blindly spam automated emails the second a payment fails. But if a temporary bank decline or insufficient funds glitch hits a high-value enterprise contract or a VIP account, aggressive automated pestering risks burning precious relationship equity.
We built Chaser to fix this balance. It pairs an optimized, multi-day adaptive retry engine for standard users with an explicit "Human-in-the-Loop" safety net queue. When an enterprise account hits a billing snag, Chaser holds the automation back, drafts a warm, concierge-toned personal message via AI, and flags it for an operations lead or founder to review and send with 1 click.
Because we are dealing with sensitive billing infrastructure, security was our baseline requirement, not an afterthought: - We treat credential safety with absolute isolation infrastructure. - Stripe API keys and webhook tokens are securely sandboxed, fully encrypted, and strictly isolated with owner-only Row Level Security (RLS) database policies. - No customer credit card data is ever seen or stored by our systems; Stripe handles the financial vaulting entirely.
We are currently 2 weeks away from opening our closed beta. We built the entire front-end tour to be fully interactive so you can play with a live sandboxed command center, and see the sequence timeline analytics without needing to hook up your own data yet.
For the HN community, if you want to jump into the closed beta, just drop a message to our support queue inside the app mentioning "HN 90" and we’ll manually upgrade your backend account to an extended 90-day free trial so you can run it through three full billing cycles.
I would love to get your brutal feedback on the workflow logic, the interactive sandbox UX, and our approach to handling automated vs. manual billing queues!