The logo looks almost identical to the old celery (task queue) logo. Not sure how the word "celery" relates to payments, but the name of the task queue is not random: rabbits like celery (rabbitmq.com).
I feel compelled to say this as a rabbit owner; they do like celery (because they like most things) but eating too much or too large pieces can lead to digestion problems because of the strings in the celery. The more you know.
i always thought of the physical structure of celery and how it splits and is stringy - reminds my of piping tasks through a distributed task queue. i like the rabbit connection too though!
I did the same, it seemed odd to be showing HN as if it were a new launch, but already in NYT and Forbes. Couldn't find any articles anywhere but then noticed on the about page that it's YC/SV Angel backed.
I'm missing something. Can you explain this to me as if I were five? I'm really gun shy with anything involving my customers CC data, and I suspect others are too.
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!
In the case of pre-ordering, Celery doesn't make any authorizations/holds upon the creation of the order. We use Stripe to make sure the card is valid and the charge is processed at a later time.
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.
Whoa - you need to make it clear that I have to bring my own Stripe account. Nowhere is that mentioned on your page. So the 256-bit encryption you're touting on your homepage is really Stripe's 256-bit encryption? Not cool.
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?
Thanks for the questions. We're working to update the FAQ and site to make all of this more clear. My personal belief is that there's more to commerce than just payments (order management, inventory management, analytics, supporting web and native mobile/tablet apps, etc). It may look simple now, but these are the types of challenges we're in the process of tackling.
> 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.
According to their demo product page[0], your card is only charged when the product ships. Is that your concern?
I second qeorge's concerns about PCI compliance and credit card storage.
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.
One of the main reasons I feel comfortable about using Kickstarter is the fact that I know my funds won't get released to the company/person unless enough people "fund" it. Once enough people back it then I'm not as worried about losing my money (probably more psychological than anything) because I feel like there would be a huge uproar if someone tried running off. This doesn't really seem to give me as the "pre-orderer" any security. Also...who really loves Celery?
75% of Kickstarter funded campaigns don't ship on time (research by Ethan Mollick from UPenn). Since my money is committed, I'm not sure if that gives me comfort either :)
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'm part of a team building distributed crowd funding tools that focus on these problems for independent sellers. Some similarities to Celery, just in terms of product.
I'd like to know the following: can't you already do this with Stripe? They seem to use stripe as their backend, so how is this different than me doing this with stripe on my own (i.e. collect charge tokens, charge later)? Or do stripe's tokens expire after a short period of time, I haven't looked into that yet.
I genuinely want to know because I'm potentially interested.
No, you can create a customer token and that token will forever refer to the credit card details the user entered. The only way you could consider that they "expire" is if the card as-entered expires, or if the user cancels that card. But even in this case your token still works, it just points to data that isn't valid anymore.
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.
You could do it yourself, but there's a lot of people who don't have the technical knowledge to do so. This is my understanding from speaking with independent makers and builders (e.g., Kickstarter grads) over the past year. Payments is only one part of commerce. Our mission is to package everything together (order management, analytics, a commerce API, etc).
Is it me, or is the grammar on this page very confusing. I had to reread sentences multiple times to understand their meanings. I understand it's a marketing page, but it seems like the author is more focused on dropping buzzwords instead of explaining the product
Maybe I'm the odd man out, but I am so sick and tired of company names that are absolutely unrelated to their purpose. Celery? Seriously? If you're not a fresh vegetable delivery service, GTFO.
So this seems to go against what I read earlier where charges are only made when the item ships - but it seems the Boosted Board takes a $200 deposit instead of just saving your card for the full amount?
Not so much emphasis with Kickstarter please. A lot of people won't go the Kickstarter route (non-US residents being among them). Being able to take pre-orders is the magic words, and won't alienate prospects.
[1] http://www.celeryproject.org/