I wonder what the advantage is of a blood based test over existing saliva based hereditary cancer screens (that do genome sequencing instead of 23andme type array testing).
I’m curious if there is a user segment truly interested in this feature/product and what their use case is. Naively this feels like a situation of “why on earth would you do this?”
I wouldn’t hold out on paypal coming to US Stripe integration. I believe it’s available in Europe because of legislation requiring Paypal to support this.
I agree with some of the sentiment here, but at the end of the day i’m not sure i’d be able to make a clean cut like OP suggests.
Python is used in so many places that’s it’s part of the lingua franca of programming. I’ve worked at multiple ruby shops over the last few years and pythons still been there in force for data applications.
I much prefer other languages (Ruby, Kotlin), but at the end of the day i need to be comfortable with the language that will be spoken for years to come.
Your internal data might not be consistent with what is stored in Stripe. Since Stripe is the one processing the payments, it is ultimately the source of truth for all data regarding whether or not transactions went through, failure reasons, disputes... etc.
The act of reconciling the list of transactions you have stored in your database with what the source of truth has is an important process for finance teams.
1- When customers repay their loans, they can be eligible for larger loans at lower rates (it is almost unheard of for payday lenders to offer better terms).
2- In the top half of our Ladder, customers have the option to have their payments reported to the credit bureaus (payday lenders don’t report).
3- When customers need more time to repay, we don’t charge them extra (payday lenders use rollovers to make more money when their customers struggle).
4- When customers make successful repayments, many can become eligible for a credit card (which is essentially an interest-free short-term loan, if paid on time and in full).