[podingx]

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.

[qeorge]

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?

[podingx]

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.

[mahmoudimus]

I'm confused, have you looked @ balancedpayments.com? We offer this out of the box without you having to go through this and we're YC W2011.