looks great, though recurly has met my needs so far, not sure what would make me consider porting over to something new
Stripe: instant payment processing for developers
81–90 of 369 posts
Re: Stripe: instant payment processing for developers
#82Their signup process threw me for a loop. You just click into the dashboard, then fill in a name and password later. It looks like just visiting the front page gives you an account, because the sample code is already using some generated API tokens. I've considered doing something similar for my own side project, but went with the more standard sign up because I was worried it would be confusing (as it was to me, for…
fwiw, that design pattern is called lazy registration.
Re: Stripe: instant payment processing for developers
#83I tried stripe a couple months ago and I was unimpressed. Mostly it was the pricing ( i think at the time it was 3.9% + 30 cents ) because I was looking to do smaller transactions $4.99 a month subscription. But I got into the beta anyways and started playing with it. Within 10 minutes a rep was emailing me trying to get more information and that I wasn't ready to give out. I ended up going with Paypal's micro transa…
Our account application asks for your personal information (thinks like bank account details, home address, etc.) as part of our automated verification process. Once it gets submitted, we try to verify and approve the application as quickly as possible, hence the quick contact.
Of course, you don't have to submit this application until you're ready. You can save your account on Stripe without filling out the account app, and do as much testing as you like, forever. Once you're ready to process real payments, that is when we'll require some of this information.
Hope that helps explain things.
Re: Stripe: instant payment processing for developers
#84What about lock-in? This is awesome for getting started fast, but what happens when you have 100,000 subscribers and you want to switch to Braintree or someone to get some better pricing?
I would also like to know about this. Their solution looks great! But I'd want to ensure that if this company goes under, or if it doesn't do what it promises, there's a way for me to get ALL of my data (subscribers, past payments, other details) and switch to another provider.
Re: Stripe: instant payment processing for developers
#85This looks amazing. @boucher, sounds like support for Canada and the UK is in the pipeline, how about other EU countries such as Germany?
In the meantime, can somebody recommend a (vaguely) similar service in/for Germany, or otherwise an old-fashioned payment processor that's less painful to deal with than others?
Re: Stripe: instant payment processing for developers
#86looks great, though recurly has met my needs so far, not sure what would make me consider porting over to something new
The difference between Stripe and Recurly is that Stripe is dealing with the full payments stack for you. You don't need a separate merchant account or gateway, and it's just one flat fee of 2.9% and 30 cents per successful charge, including our subscription billing services. As a result, it's often quite cheaper than combining several separate services.
Re: Stripe: instant payment processing for developers
#87Best API ever for a payments processor - period. It literally takes a couple hours to set up begin collecting payments. If I could buy some shares right now I would. I've convinced 2 people to use it and both are in love. This startup is money.
Re: Stripe: instant payment processing for developers
#88I was under the impression that if my website is asking for a credit card number that is later used for a transaction, then it needs to be PCI compliant. Perhaps, it is a Canadian specific, but this need for the PCI compliance is the major selling argument in favor of hosted payment services.
And on a related note - is Stripe available outside of the US?
(edit) Ah, found it.
> Do I need to be in the United States to use Stripe?
> Yes.
Re: Stripe: instant payment processing for developers
#89I'm not sure about avoiding PCI compliance so easily. You're embedding their JS library on your page. That page has to be secure, otherwise if someone can inject malicious Javascript they can sniff the CC data as soon as they are entered. You might not be storing the data on your servers, or transmitting the data directly, but security failures in your setup can cause the data to be leaked. Compare this to sending th…
> I'm not sure about avoiding PCI compliance so easily. You're embedding their JS library on your page. That page has to be secure, otherwise if someone can inject malicious Javascript they can sniff the CC data as soon as they are entered.
If their credit card info doesn't touch your server, then it is out of scope as far as PCI is concerned. Yes it's BS, since the risk is essentially the same, but that's how it's currently written.
Re: Stripe: instant payment processing for developers
#90EDIT: removed so as to not hijack another announcement. Was not the intention, just wanted to offer something people thought was useful.
Do you do recurring billing? It's not clear with a quick view of the documentation. Or do you expect that individuals are provided sufficient information to build their own (easy?) recurring systems? If you do, we'll look at moving immediately. We'd not only be saving money but your API doesn't confuse the hell out of my like what we're currently using.