We have an app (http://tulasoftware.com) that yoga studios use to run their business and we're able to compete with some very well funded companies in no small part because of our Stripe integration.
We've been guiding people through the stripe account creation process though, and having them manually enter their API keys. This basically eliminates the need for any manual intervention at all.
It's relatively smooth, but definitely not as smooth as this new feature allows for.
Well done to Stripe for such experience-focused feature releases.
Can anyone more knowledgeable (who knows about this industry or finance) enlighten me regarding what could be the possible reasons that may be stopping this company from doing so despite all this demand?
They could be in Asia and the entire EU in under a year, I'm pretty sure. Their platform would implode and we'd all talk about how Stripe used to be good, and now it's worse than PayPal and how the executives screwed the pooch.
To do things right takes time. Months, even years. If Stripe isn't available in your country, maybe you should build it.
Disclosure: I do not work for Stripe, but I've worked with their API as well as the APIs of Piryx/Rally and PayPal. Stripe's is the best (Piryx is a close second but they've transitioned to Rally and last I checked Rally didn't have an API), and I'm as huge a fan as I could be having never processed a penny of real money through their servers.
I am genuinely curious as to what is stopping them from doing it (considering Paypal, 2checkout, etc are already doing it). I think I have some understanding about it now after reading SoftwareMaven's comment.
> It's a hell of a lot easier for someone in Germany to rip off Stripe and comply with all the German regulations than it is for Stripe to come in with no assets on the ground and figure it all out.
Unfortunately, that is just as bad and does not solve the problem, because most online businesses cater to a global audience (unless dealing in tangible products) so any payment processor just limited to Germany can never fully compete or replace competitors who do.
It could be a similar turning point from Stripe as well. Every time this comes up a good portion of the thread is dedicated to them not being International. Maybe if they just started doing this on a trial basis they will see how much business they have untapped. Or maybe some other business can use this leverage to offer similar services to instantly enter the market.
Sometime "launch it and hope for the best" is not the right answer (though it very often is).
Startup idea: Set up US based company that redirects money to countries outside USA.
I know it's a bit of a leap to get someone willing to sign up for my service just to have to say "okay, now you just need to sign up for this other service you've never heard of..."
We've tried to make it as seamless as possible for your users to create an account; it's baked right into the authentication flow instead of having them separately register. Hopefully that helps, would love to hear your thoughts here (email@example.com).
AWS and PayPal seem like the only viable options for us, at this point, but I anxiously await the day that Stripe rolls out a micropayment pricing tier.
My understanding until now was that only developers of websites would have a need for a Stripe account, and if I merely purchased something via CC on a Stripe-enabled website, I did not have a Stripe account. So as a marketplace, I have to encourage/demand that my sellers create an account with a third party that they haven't heard of before.
Given that I would want to use Stripe if I were building Dawdle from scratch again, is there a way to have them create a Stripe account without them knowing they're creating a Stripe account?
Check out https://stripe.com/docs/connect#payments-flow, for example. A logged-in user will see the page on the left, while a new user will see the page on the right.
That make sense?
I think your copy needs some improvement for clarity.
FYI, for Rails developers, there's a nice Omniauth/Stripe strategy:
If you're using our application_fee parameter to take your own fee out of a transaction, you get the full amount you request. Both that full amount, and the Stripe fee for the charge, are subtracted from the total amount paid to the seller.
To illustrate, a $100 charge with a $1 application fee would end up sending $1 to the application, $3.20 to Stripe, and $95.80 to the seller.
If there are multiple parties involved in referring the sale, I will be charged not one but a multiple of the Stripe fees whenever money is disbursed to appropriate parties involved in one single sale.
Furthermore, because I have to process returns I will not be able to send the payment directly to the seller immediately. The payment would be retained in my account after a period of time before I could transfer it to the sellers.