peekypeeky008

Thanks for the feedback. We have strict compliance and legal terms in place to prevent any misuse of this. This is being used by Amazon, Netflix and other top merchants. It’s all a matter of user communication and terms you have with your customers. Thanks

We do prove it with the data but as mentioned the merchants notify customers before. Thanks

I’m Tzachi, one of the cofounders here at FlyCode. It’s great to see the discussion here. It’s really helpful for us and we’re taking everything under consideration. It’s interesting for me to see the “consumer” perspective vs. the merchants (our customers) perspective that use this product at scale for failed payments. Thanks

Our goal as a product is never to reach the stage of subscription cancellation, and definitely not debt collection. We’re saving failed payments from being canceled.

Our merchants have thousands of customers. This is not a debt collection use case. It is about saving good payments that should go through. It is about fighting broken bank models with our models for payment recovery

Sure, we email customers about failed payments. They can always cancel but please remember that those are payments that should have gone through anyway

Not at all. SaaS customers are doing the full process in notify their customers first. The reduce chargebacks is happening because those are "good" payments that should go through anyway. The customer never intended to cancel the subscription from a failed payment

Yeah, we're all coming from a FinTech background so it was a better fit for us

Stripe offer a basic payment recovery, it's up to the merchants to offer more advanced way for their customers to pay. You can check out our Stripe app

The service didn't stop. You subscribe to a product that you're using but the bank declines the payment (happens every time to almost 30%+ of customers). The customer never intended to churn.. they can always go and cancel. It's good customers with legitimate payments.

Thanks for the comment. Happy that someone brought this up. Before it works, our merchants complete the full process of making sure their terms are up to date and they notify their customers. It's all from cards the customers have on file. Try to look at it from the customer's point of view: they didn't actively want to cancel their subscription. The bank declined a good transaction

Thanks for the comment. We help subscription-based businesses in SaaS and eCommerce. The average results show a boost of 20-25% in the recovery rate

In 2022 we launched our dev tool and then shifted to payments. It took us 1 year so far

Looks great

Permissions are a nightmare. Great to see this

Hey, thanks for the feedback. Yea sounds similar goal but different: (1) no integration with us (no API just Git connection) (2) we keep your code ownership - continue to edit from your code, no need to change your infra (3) we are not a CMS -> we connect and extract from the code directly so the capabilities are different

Last thing - git work flow. Your code -> you are approving the same way you work today

Thanks for the feedback. We hire devs based on talent not language so feel free to apply. FlyCode is able to identify changes made in a commit and identify a text is the same according to the semantic structure of the code but of course it is not 100%. In many cases though texts stay in about the same place and when moved they change their meaning and should be treated differently

Tzachi, cofounder at FlyCode here - thanks a lot for the feedback :)