It looks solid.
I see that you mention that you have had quite a lot of press coverage for this.. by the "As Featured In".
I can't find any related articles though and I'd be interested in reading them :)
Plus site:techcrunch.com trycelery.com doesn't work, and neither can I find any articles on BetaBeat, Forbes or the NYT?
If you are truly backed by YCombinator (which I have no reason to doubt), I'd have expected to be able to read some coverage?
Some of my concerns:
1) Authorize now but only charge when actually shipping is standard Visa policy. Doing it any other way is not allowed. Your system seems like a workaround for that, which raises my alarm bells.
2) To be clear - you are storing the credit cards in your vault (not Stripe's vault), and then running them through your Stripe account later as normal transactions? And this is cool with Stripe/Visa?
3) What do you mean PCI compliant? Do you think you are, or are you being regularly audited? Where are your servers? Credit cards are serious business; we need to know.
4) I'd expect a ton of chargebacks. How are those handled? What do the chargeback fees look like?
5) Is this Amazon Payments without the branding?
I want to love your product, but I wonder these things. Please help me understand!
Celery does not store the credit cards and all payment information transferred is encrypted with SSL. The cards are held within Stripe's vault. Each seller uses their own Stripe token.
The chargebacks would affect the seller, since the payments are linked to their Stripe account. It's important that seller is able to actually ship the item if they decide to charge the buyer. Otherwise, they would need to refund or risk getting hit with chargebacks.
Is the "Embeddable Checkout Overlay" really Stripe Checkout too? Which of your features are you actually providing and which are really Stripe?
Right now this looks like a simple wrapper around Stripe Connect that waits X days to bill, plus a basic Bootstrap template you can use. What am I missing?
According to their demo product page, your card is only charged when the product ships. Is that your concern?
Futhermore, credit card processors and banks do not want to be on the hook for what happens when the items do not ship in these pre-order scenarios. The CCs are all about limiting their exposure to risk and this opens them up to a number of issues regarding products not shipped on time, not as advertised, etc.
Personally, I feel better knowing that I won't be charged at all until the item is shipped. And in the worst case, I would request a refund or issue a chargeback if I felt the seller was being "sketchy".
I genuinely want to know because I'm potentially interested.
Unless celery does anything else on top of this (auto notifies customers if the cc expires in the interim, provides them a way to update details without you needing to do anything) then I don't see any compelling reason to use it.
> Spend less time on tracking down lost orders and focus on building great products.
It should be "Spend less time tracking down..."
The bigger issue is that nearly every sentence breaks in awkward places due to the layout of the site.
Safely hold payment information
without charging until you're ready
Our checkout design is responsive
so your product sells itself on any
desktop, mobile, or tablet device.
Allow purchasing directly on your
site with an embedded checkout
overlay that’s elegant and secure
Similarly, none of the emphasis phrases should start halfway through a line and break:
orders in person