HackerNews中文版

我们开发 FlyCode 的初衷是看到订阅制企业每年因支付失败而损失约 35% 的经常性收入——即使客户有其他有效的备用卡信息。*问题所在：* 当客户的主要卡支付失败时，Stripe 会重试几次，然后取消订阅。如果该客户有备用卡，系统也不会尝试使用。至少有 20% 的活跃客户拥有不止一张卡的信息，这意味着很多流失是可以避免的。*我们的解决方案：* FlyCode 能够自动识别客户是否有其他有效的备用卡信息，并在订阅支付失败时尝试使用它们。您可以配置这些重试发生的时机（在催缴期开始、中间、结束时），并定义有效性规则（例如，“卡在过去 180 天内使用过”）。它是一个 Stripe 应用——无需更改代码。我们从核心重试引擎中看到了 18%-20% 的更高恢复率，另外使用备用卡又提高了 5-10%。重要的是，退款或拒付率没有增加——事实上，这些比率低于商家平均水平。像微软和亚马逊这样的大公司已经在内部使用这种方法；我们希望让较小的 SaaS 团队也能获得相同的功能。*幕后运作：* FlyCode 监控失败的发票，通过 Stripe 的 PaymentMethod API 检查可用的备用支付方式，并系统地进行重试，从而避免服务中断或手动工作流程。我们是 Jake、Etai 和 Tzachi——我们之前在初创公司和企业中构建了支付恢复系统，这就是我们发现这个差距的原因。您可以在这里试用：[<a href="https://www.flycode.com/stripe">https://www.flycode.com/stripe</a>]我们欢迎任何处理订阅支付失败的人提供反馈。您在非自愿流失方面有什么经验？您是否考虑过利用备用支付方式？

查看原文

We built FlyCode after seeing subscription businesses lose ~35% of recurring revenue each year to failed payments — even when customers had other valid cards on file.*The problem:* When a customer's primary card fails, Stripe retries a few times then cancels the subscription. If that customer has a backup card, it isn’t tried. At least 20% of active customers have more than one card on file, which means a lot of preventable churn.*Our solution:* FlyCode automatically identifies if a customer has other valid cards on file and retries them when a subscription payment fails. You can configure when these retries happen during the dunning period (beginning, middle, end) and define validity rules (e.g. “card was used in last 180 days”). It’s a Stripe app — no code changes needed.We've seen 18%-20% higher recovery rates from our core retry engine, plus another 5–10% from using backup cards. Importantly, there was no increase in refunds or chargebacks — in fact, rates were lower than merchant averages. Big companies like Microsoft and Amazon already do this internally; we wanted to make the same capability accessible to smaller SaaS teams.*Under the hood:* FlyCode monitors for failed invoices, checks for available backup methods via Stripe’s PaymentMethod API, and systematically retries in a way that avoids service disruption or manual workflows.We’re Jake, Etai, and Tzachi — we previously built payment recovery systems at startups and enterprises, which is how we discovered this gap.You can try it here: [<a href="https://www.flycode.com/stripe">https://www.flycode.com/stripe</a>]We’d love feedback from anyone dealing with subscription payment failures. What’s been your experience with involuntary churn? Have you considered leveraging backup payment methods?

Show HN: FlyCode – 通过自动使用备用卡找回 Stripe 支付款项