Escharts support. Finished the payment handling. Working on the prepayment code - which involves expanding the web page to accommodate a payment provider selection, and underlying code to do what's needed (as per register.aspx) for each payment provider. Currently the page
only supports a single provider - so I need to split out the invoice and order generation code from the page load code, and stick in a couple of post back buttons (one for each provider) and do provider specific stuff in the postback handling code for each button.
Creating a win 2003 server VM, running 2 websites, one for charts.bubble.com and another for escharts.bubble.com.
Tuesday, August 04, 2009
Monday, August 03, 2009
Callbacks and state variables (20090731)
Matching Worldpay callback code - making sure to exclude/extract code for other operations - cancellations etc.
Slight hiccup in the PayPal/MIS implementation is that as I uncover each requirement from the existing code, and implement it for PayPal/MIS, I discover a bunch more requirements. All of this makes trying to determine how far there is left to go rather difficult.
Worldpay also supports accepting any number of passthrough variables (and values) which the shop code uses to sling a bunch of state data and flags around. PayPal doesn't support this - so all this information will have to be saved into the DB before any call to PayPal. This I will make as generic as possible.
Slight hiccup in the PayPal/MIS implementation is that as I uncover each requirement from the existing code, and implement it for PayPal/MIS, I discover a bunch more requirements. All of this makes trying to determine how far there is left to go rather difficult.
Worldpay also supports accepting any number of passthrough variables (and values) which the shop code uses to sling a bunch of state data and flags around. PayPal doesn't support this - so all this information will have to be saved into the DB before any call to PayPal. This I will make as generic as possible.
Subscribe to:
Posts (Atom)