HackerNews中文版

我们创建FlyCode是因为我们发现订阅业务每年因支付失败而损失约35%的经常性收入——即使客户的账户中还有其他有效的信用卡。 *问题：* 当客户的主卡支付失败时，Stripe会尝试几次后取消订阅。如果客户有备用卡，则不会进行尝试。至少20%的活跃客户在账户中有多张卡，这意味着有很多可避免的流失。 *我们的解决方案：* FlyCode会自动识别客户是否有其他有效的卡片，并在订阅支付失败时进行重试。您可以配置这些重试在催款期内的发生时间（开始、中间、结束），并定义有效性规则（例如：“卡片在过去180天内使用过”）。这是一款Stripe应用，无需代码更改。我们从核心重试引擎中观察到18%-20%的更高恢复率，使用备用卡则增加了另外5%-10%。重要的是，退款或拒付的比例没有增加——实际上，退款率低于商家平均水平。像微软和亚马逊这样的大公司已经在内部执行这一策略；我们希望将同样的能力提供给较小的SaaS团队。 *技术细节：* FlyCode监控失败的发票，通过Stripe的PaymentMethod API检查可用的备用支付方式，并以避免服务中断或手动工作流程的方式系统性地进行重试。我们是Jake、Etai和Tzachi——我们曾在初创公司和大型企业构建支付恢复系统，这也是我们发现这一空白的原因。您可以在这里试用：[https://www.flycode.com/stripe](https://www.flycode.com/stripe) 我们希望听到任何处理订阅支付失败的人的反馈。您在非自愿流失方面的经验如何？您是否考虑过利用备用支付方式？

查看原文

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?

展示HN：FlyCode – 通过自动使用备用卡恢复Stripe支付