Hi guys
Firstly awesome work Stephen! Mezzanine & Cartridge are exactly what I was
looking for.
Have you guys made any progress on the merging the cart and order? I am
also in the process of implementing an external payment via direct POST,
and also need the order id before payment is
Lots of good points there.
I suppose I have unconsciously been thinking about this from the
perspective of someone who needs to take payments via external POST, and
also happens to want the unfinished orders hanging around as well. So
cleaning up and hiding the unfinished orders didn't occur to
I like the idea of having an order ID before payment (for the reasons you
outlined) but I'd be curious to hear if Steve had any particular reason for
not doing this when he originally created Cartridge.
Also, in case you haven't seen it you might want to look at
Hi Josh,
I'm interested to hear from Steve too. Since Cartridge was initially
written to call payment processors from the server, only creating the
orders after payment was submitted makes sense it makes sense – doing so
earlier does introduce a bit of extra complexity. Keeping the cart in sync
There was a lengthy mailing list discussion on this years ago where
everyone agreed that there shouldn't be unfinished orders floating around
in the database.
I still agree with that and I'm not particularly keen on the idea of having
to maintain this as an option and feature. Cartridge is
My understanding is that if CC details touch your server, even in memory,
you need to be compliant. The official PCI body says The DSS globally
applies to *all* entities that store, process or transmit cardholder data
at https://www.pcisecuritystandards.org/pdfs/pci_ssc_quick_guide.pdf
I agree
