pc

17 ms·

1. 61.▲
   by pc 6y ago

   Hah. This is in fact a problem area that our Billing ( https://stripe.com/billing ) team is actively thinking about. You should reach out to ark@stripe.com if you want to discuss -- he can connect you with the right folks.
2. 62.▲
   by pc 6y ago

   I think that the infrastructure market naturally breeds a lot of products for pretty specific/narrow use cases, whereas our strategy is more about marrying financial capabilities with very broad/flexible APIs. Given that, we'
3. 63.▲
   by pc 6y ago

   Yes, the world certainly hasn't yet nailed this playbook. AWS has , I would contend, objectively done an incredible job in this synthesis. (How many other businesses have grown to $40B+ of revenue with self-serve product adoption fron
4. 64.▲
   by pc 6y ago

   We're excited to hire Mike in part because AWS has been one of the very best examples ever of simultaneously selling to the largest companies in the world while not giving up on a strong self-serve product. So many B2B companies end
5. 65.▲
   by pc 6y ago

   It's not super fun per se but Stripe is an important infrastructure service and scrutiny comes with the territory. I'm always happy to answer questions.
6. 66.▲
   by pc 6y ago

   Hey, that's not how arguments on the internet are supposed to go :-).
7. 67.▲
   by pc 6y ago

   > Is Stripe's valuation significantly predicated on revenue it can extract from the surveillance data it's collecting?" No, it's not. This telemetry is useful for helping businesses avoid crippling fraud losses and we
8. 68.▲
   by pc 6y ago

   Oh, offer was made in case GP wants to have a deeper discussion/back-and-forth than is readily achievable with an online forum. Timing constraints notwithstanding, we work hard to answer questions on HN too.
9. 69.▲
   by pc 6y ago

   This is a fair call-out. We have actually worked pretty hard to ensure that our Privacy[1] and Cookies[2] policies are clear and easy-to-read, rather than filled with endless boilerplate jargon. But we still did make a mistake by not have a
10. 70.▲
    by pc 6y ago

    https://stripe.com/privacy describes what we do in some detail (including disclosing that we use this kind of browsing data). More broadly, I assure you that Stripe.js and our fraud prevention technologies are very carefull
11. 71.▲
    by pc 6y ago

    Thanks! Very glad it worked out for you. I quoted you in my response at the top -- hope you don't mind. (Can remove if you prefer.)
12. 72.▲
    by pc 6y ago

    Definitely no dismissiveness intended -- apologies. While Stripe has been in business for 10 years, Radar (our fraud prevention tool) has only existed for 3.5. We've made a good deal of progress in that time and I would guess that it&#
13. 73.▲
    by pc 6y ago

    Sure -- one very common form of attack is "card testing". Here's a quick summary: https://www.forbes.com/sites/tomgroenfeldt/2017/05/02/card-t... .
14. 74.▲
    by pc 6y ago

    I apologize that anything about the pricing change felt sneaky. (We tried to do the opposite: we emailed every single impacted customer!) I posted a few thoughts about the refund change here: https://news.ycombinator.com/ite
15. 75.▲
    by pc 6y ago

    Hi ddevault -- we would like to do this, and I'm very supportive in principle (and, per GP, we are perfectly fine with anyone not using Stripe.js), but our current product/engineering focus is on trying to build better tools for t
16. 76.▲
    by pc 6y ago

    Indeed -- although our business model is, I think, more closely aligned with our users. We serve only one kind of customer: businesses receiving payments with Stripe. Our revenue is a roughly linear function of that of our customers.
17. 77.▲
    by pc 6y ago

    I'm sorry to hear that! Feel free to email me (patrick@stripe.com) and I'll connect you with the team if you'd like us to do a deeper dive. But, yes, part of the intent here is to enable us to achieve better ROC[1] in our mod
18. 78.▲
    by pc 6y ago

    We build models that predict P(payment charged back as 'fraudulent') and then let small random samples through in order to test the accuracy of our predictions. This calibration means that we can compute a pretty accurate "tr
19. 79.▲
    by pc 6y ago

    I'll ask our legal team if we can somehow contractually preclude ourselves from sharing this data in the case of liquidation or otherwise bind ourselves in a useful fashion... To your question about what the data actually includes and
20. 80.▲
    by pc 6y ago

    Not sure what verifiable stats could look like here, I'm afraid... but I can assure you that it is in fact true!
21. 81.▲
    by pc 6y ago

    Yes.
22. 82.▲
    by pc 6y ago

    Glad you're liking Radar! You're right that, if you don't use Stripe.js, PCI compliance will be more work. And, yes, you can definitely include Stripe.js only on a single page.
23. 83.▲
    by pc 6y ago

    Yep, certainly open to that. We'll address that in the page we put together about this.
24. 84.▲
    by pc 6y ago

    Yes, this is a good point.
25. 85.▲
    by pc 6y ago

    Stripe cofounder here. The question raised ("Is Stripe collecting this data for advertising?") can be readily answered in the negative. This data has never been, would never be, and will never be sold/rented/etc. to adve
26. 86.▲
    by pc 6y ago

    Thank you for your work on Covid-19!
27. 87.▲
    by pc 6y ago

    Thanks! Very helpful on all counts. (And thank you for the kind words on the Dashboard... the team has made a lot of progress there.)
28. 88.▲
    by pc 6y ago

    We just revamped our Connect docs... would love to hear any thoughts you have on the revised version. (Feel free to email me directly -- patrick@stripe.com -- and I'll forward your thoughts to the team.)
29. 89.▲
    by pc 6y ago

    We added that last year! (Or maybe the year before...)
30. 90.▲
    by pc 6y ago

    That sounds concerning -- could you email mjahr@stripe.com with more details?