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[0], 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.
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!