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

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.




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

Search: