Hacker News new | past | comments | ask | show | jobs | submit login

@devbug I work at Stripe. nope—neither, we’ve worked with Visa and Mastercard to get funds on to debit cards instantly. This isn’t a refund or a loan. Without getting too into the weeds, in the same way you can make a payment at 10PM on a Sunday, you’re able to be paid out instantly through Instant Payouts.



If the customer issues a chargeback, who ultimately owns the liability? The person corresponding to the managed account, or the owner of the marketplace that manages the accounts?

Will the owner of the marketplace be held responsible for the requirements like maintaining a low chargeback percentage, or is that requirement passed on to the managed account (which could be closed if that becomes an issue)?


With managed accounts the platform owns ultimate liability. This is because with managed accounts we agree not to contact the account holder directly under normal circumstances, so we are more limited in our ability to ask for more information or quickly shut down potentially fraudulent accounts.

As for things like chargeback rate, it depends more on your type of business than the particular Stripe product you use. For example, if you are running a shopping cart hosting service, we recognize that each of your stores are different, and will consider them somewhat separately. However, as the direct line to your customers, if you're attracting a huge amount of fraud on your platform, we would expect you to take steps to reduce that, and would work with you to figure out what the best steps may be.

We are working to figure out the best balance between giving platforms control and using our expertise to help them with challenges like fraud. If you have any suggestions on how we could improve this balance I'd love to hear them, either here or via email at bkrausz@stripe.com


Sure, I can imagine both scenarios coming up. On the one hand, if the builder of a platform sets it up in a way that makes fraud quite likely, then that's the platform builder's problem. On the other hand, if the builder of the platform takes reasonable steps to make fraud unlikely, but occasionally some user does things they shouldn't, that should ideally be passed through to that user and that user can have their account terminated.


You're using https://developer.visa.com/products/visa_direct & the MC equivalent to accomplish this, right?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: