Showing results for 
Search instead for 
Did you mean: 

uestion regarding Direct Post Method - Migrating over from CyberSource

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 server. C. The server does a post directly to the site's web server. D. We send back a snipet of HTML that sends back to the user's browser to direct it back to the site's web server. E. 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.

Please format your question so it isn't one big paragraph. It's difficult to read it in its current form.

John Conde :: Certified Authorize.Net Developer (Brainyminds) :: Official Authorize.Net Blogger

NEW! Handling Authorize.Net's Webhooks with PHP

Integrate Every Authorize.Net JSON API with One PHP Class (Sample code included)

Tutorials for integrating Authorize.Net with PHP: AIM, ARB, CIM, Silent Post
All About Authorize.Net's Silent Post

Step C, which in lingo is the "relay response" page. The relay response page should receive full order information, and since you're passing the transaction ID from there to the receipt page via the URL, you could theoretically also use the Transaction Details API to look up the transaction there. Or you could even set up a silent post and have that update your database. It's up to you.