You need to state your pricing structure clearly. Saying that you charge 2% over what Stripe charges makes it seem like you are hiding the total cost of transactions. Using Helium would cost people 4.5% plus 25 cents, am I right?
I also see that you are testing the response from HN. Well done. But the landing page for HN and regular visitors are the same. Why not run some quick tests with all the traffic?
You might have branding issues with the project Blimp (getblimp.com). The founders are really cool guys, but do chat with them about it.
The design is top-notch, though a button or link that scrolls down to the area with more information should be tested. Right now, the first impression you get is that this is an empty landing page.
Regarding pricing: We talked about the wording internally. It was decided that different people pay different stripe fees (eg volume discounts) and stripe may change their fees in the future w/o notice, so it's best to simply state what we charge. I've added a link to Stripe's pricing page to make things a little more clear.
The page itself is loaded via HTTP, but all credit card information is transferred to Stripe & Helium via HTTPS. Again, with Helium, no payment information actually needs to hit your servers (Sam's blog, in this case).
I think this is a valid concern. IIRC such payment-related Javascript code should only be included in https:// context as other script code might interact with the payment form.
You could always just put it in the first go, then if you get any traffic, replace it with a more efficient option. Most people never get enough traffic for percent cuts to matter anyway.
Comments
You need to state your pricing structure clearly. Saying that you charge 2% over what Stripe charges makes it seem like you are hiding the total cost of transactions. Using Helium would cost people 4.5% plus 25 cents, am I right?
I also see that you are testing the response from HN. Well done. But the landing page for HN and regular visitors are the same. Why not run some quick tests with all the traffic?
You might have branding issues with the project Blimp (getblimp.com). The founders are really cool guys, but do chat with them about it.
The design is top-notch, though a button or link that scrolls down to the area with more information should be tested. Right now, the first impression you get is that this is an empty landing page.
A demo would also be nice.
Regarding pricing: We talked about the wording internally. It was decided that different people pay different stripe fees (eg volume discounts) and stripe may change their fees in the future w/o notice, so it's best to simply state what we charge. I've added a link to Stripe's pricing page to make things a little more clear.
Regarding the demo: we're planning on adding one to the home page. Until then I added the button to my blog: http://sam.odio.com/2012/10/31/buy-me-beer/
I'd be loath to put my credit card info there since it's on an HTTP (not HTTPS) page. How is this remotely secure?
The page itself is loaded via HTTP, but all credit card information is transferred to Stripe & Helium via HTTPS. Again, with Helium, no payment information actually needs to hit your servers (Sam's blog, in this case).
I think this is a valid concern. IIRC such payment-related Javascript code should only be included in https:// context as other script code might interact with the payment form.
It's actually against the stripe Terms of Service to use live mode keys on a non-https site.
but if your target audience is the long-tail (especially folks without websites), odds are a good proportion of them won't even know what Stripe is..
Considering they link to Stripe's pricing page right there it should be ok.
You could always just put it in the first go, then if you get any traffic, replace it with a more efficient option. Most people never get enough traffic for percent cuts to matter anyway.