Latest Tech News

Stay updated with the latest in technology, AI, cybersecurity, and more

Filtered by: retries Clear Filter

Show HN: FlyCode – Recover Stripe payments by automatically using backup cards

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

Retry Loop Retry

Retry Loop Retry Some time ago I lamented that I don’t know how to write a retry loop such that: it is syntactically obvious that the amount of retries is bounded, there’s no spurious extra sleep after the last attempt, the original error is reported if retrying fails, there’s no code duplication in the loop. https://matklad.github.io/2023/12/21/retry-loop.html To recap, we have fn action () E ! T { ... } fn is_transient_error (err: E) bool { ... } and we need to write fn action_with_r