Forum Moderators: buckworks
Id like to set up a merchant accoutn for this business through total merchants and authorize.net
I know Authorize.Net has an SSL page for thier cc processing, Id just like to know how this all works.
We have some pretty decent ASP.NET coders ready to go on a shopping cart, but I just have a few quick questions.
For example, say someone adds a few items to a basket, then enters their address, name, email, etc. We send that information to Authorize.Net's secure page where the buyer then puts in their credit card information. At that point an email I guess is sent to them and to the business notifying them of the order.
The question I have is how does the business know that the person didnt fill out all the information, then just close out the window with the credit card information (as in, they didnt complete the order). Can Authorize.Net pass that address information back somehow so that the order information can be placed into a database? How does that whole process work. After all the important infromation has been collected by the shopping cart, when and how do you enter that information into a database so that the business can keep track of the order and fulfill it without having the person cut out at the credit card screen and not recieve their order still.
I really deal with graphic arts, but the guy I work with and the other coders are working on some projects and asked me to help out and figure this whole thing out.
Sorry for all spelling errors,
Thanks for any help, it is greatly appreciated.
It sounds like you are sending the user off to the Authorize.Net gateway.dll page for the user to enter credit card info there. Personally, I prefer to keep the user on my sites at all times unless required otherwise. You can collect the credit card info on your page, and send it to Authorize.Net, just as you do with the other fields (and of course you have to name them what AN is expecting).
Along those lines, I prefer to NEVER send the user to the Authorize.Net pages at all. Simply POST the data to Authorize.Net within your own ASP pages. See here [webmasterworld.com] for an example.
I would suggest going through Authorize.Net's User Guide which details all the possible fields and how to use them. You'll learn quite a bit about what you can do with AN.
Im guessing that if you post the data to authorize.net, then you would have to be a secure page yourself. Does that mean you have to secure your server with SSL?
If you don't have SSL, then you would proceed the way you originally explained - send the order info to the AN pages, have the user enter CC info there, process the charge, and then handle the results coming from AN.
