I would like to see the payment processing portion of the
checkout process be developed as a configurable
pipline. I envision a xml config file for pipelines which
defines the pipeline for different portions of the
application. For the checkout portion of the application
this would include, for a simple example, the following
pipeline:
1) enter shipping information
2) enter billing information
3) enter payment information
4) approve all information
5) reciept
or a more complex example:
1) enter shipping information for subset of products (loop
until all products have shipping info associated)
2) enter coupon code
3) enter paymentinformation
4) if payment info does not cover full amount (ie. gift
card) enter the rest of the payment information - loop
until covered.
5) enter billing information for each payment type
6) approve all information
7) reciept
8) digital delivery
The pipeline should allow different routing through the
pipeline based on return codes. example: if coupon code
from above example covers the full amount of purchase
goto billing info, otherwise get more payment info. etc.
We need to talk more about this obviously. If anyone
has any comments we should hear them soon. This is a
pretty imporntant part of this cart.
MikeD