Currently with CyberSource, the payment process goes like this: • User fills in the fields in their browser and clicks a submit button. • User's browser sends an HTML POST to CyberSource. • CyberSource responds with the results in hidden fields in a form, with an onload that causes the form to post to our web server (the customer sets the URL for this is defined in the parameters in CyberSource's business center web site). • The web server gets the posted data and calls the web routine to record the results of the transaction. With authorize net, if I'm reading their spec right, the submit process works like this: A. User fills in the fields in the form and clicks a submit button. B. User's browser sends an HTML POST to the authorize.net server. C. The authorize.net server does a post directly to the site's web server. D. We send back a snipet of HTML that authorize.net sends back to the user's browser to direct it back to the site's web server. E. authorize.net responds to the pose the user's browser did in step B above with the code it got back from the sites web server in step D above. Which step in this process contains the data about the transactions (success/failed status, etc)? Step C or step E? This process is described in the DirectPost_guide.pdf file at the beginning of the Conceptial Overview section. The steps in the process I'm questioning are C and D in the pdf file.