As for your specific case, please email me at anurag@stripe.com and we can try to figure out if Stripe can somehow work for you.
2,188 karma · joined July 1, 2009
• Previously engineer #5 and (later) Head of Risk at Stripe
As for your specific case, please email me at anurag@stripe.com and we can try to figure out if Stripe can somehow work for you.
If you do receive chargebacks, I'd recommend keeping extensive records that you can later upload as a PDF file as part of the dispute process.
Things like:
- IP addresses, logins, usernames and other proof that the customer used the product.
- User correspondence acknowledging the purchase.
- All invoices sent to the user.
- Emails or other documentation displaying cardholder consent for the transaction.
While it isn't always easy to win disputes for SaaS business, submitting comprehensive evidence in your dispute response significantly improves your chances.
If you have thoughts on how we can improve this process further, we'd really appreciate hearing from you. Email me at anurag@stripe.com.
1. This failure mode existed up until a few months ago, but has since been fixed. In order to avoid anyone wasting time, we have systems that alert us to potential ToS violations as soon as someone sets up their account. We review these alerts right away, and reach out to users well before they've started accepting payments.
2. We never cancel or refund transactions that have even a remote chance of being legitimate. For cases where we have to stop accepting payments for a website because of ToS issues, we're always happy to give users as much time as they need to transition off of Stripe if they've already started accepting payments through us.
If you're aware of recent cases where we haven't done this, I'd really appreciate knowing about them. You can reach me at anurag@stripe.com.
That's fair (and thanks!)
Depending on the context, we use both individual merchant accounts as well as shared accounts with unique merchant identifiers. I should add that this model isn't unique to Stripe, but it's still a relatively new model in the industry.
A Stripe account is perhaps best thought of in terms of its properties rather than as a traditional, segregated merchant account or a shared account. The typical benefits of a traditional merchant account are:
1. Your name shows up on customers' statements.
2. Your funds are clearly segregated from those belonging to other users (and from the payment provider's as well).
3. Your account's reputation is independent of other users.
Let me know if I've missed any properties that you think are important. Stripe gives you all of these properties, with the added bonus of not requiring a lengthy form faxed in with a copy of your driver's license.
I completely agree with the concerns around merchant accounts. It's probably worthwhile noting that even with a segregated merchant account, it's important to make sure you're actually getting all the properties mentioned above.
In fact, thinking about merchant accounts for your Stripe account is like thinking about the physical address of one of your AWS instances - it doesn't really matter.
Separately, Stripe is allowed to transfer customer data to other PCI-compliant providers. So if you ever want to move to another provider, we'll happily move your customer information to your new payment provider (or your own systems, if you are PCI-certified): https://stripe.com/us/help/faq#export-card-data
A lot of PayPal's issues stem from the draconian fraud measures they need to employ to handle user-to-user payments. Our business and fraud problems are fundamentally different because we don't support this use case.
Additionally, we've been really careful to grow slowly, and to make sure the experience for our users remains great. We've been in invite-only mode for well over a year before opening up today, and intend to monitor (and, if necessary, limit) our growth so that this doesn't happen.
We'd rather be small than suck.
They've already acquired companies to directly compete with both OnLive and Steam: http://www.engadget.com/2011/04/01/gamestop-details-plans-fo...
set pastetoggle=<F3>
http://vim.wikia.com/wiki/Toggle_auto-indenting_for_code_pas...
Regarding your second point - tying into existing identity providers like Facebook would have little overhead beyond the initial implementation. If you wanted to go a step further, you could create an automated phone verification system, like the one Google uses for new accounts. Again, the intent would be to make it harder to comment or upvote anonymously, not impossible.
http://logoworks.com/client-app/showPackageSelection.do?new=...
In the agency model, publishers force retailers to sell ebooks at pre-defined (and usually unjustifiably high) prices. All the large publishing houses are quite uncomfortable with the rise of ebooks because consumers expect ebooks to cost less and increased ebook adoption would mean lower profits for publishers.
This article goes into more detail: http://www.teleread.com/paul-biba/why-smashwords-moved-to-ag...