CHAPTER 20 ?– PROCESSING CREDIT CARD TRANSACTIONS 641
Going Live
Moving from the test account to the live one is now simply a matter of replacing the DataCash
login information in include/config.php with real-world values. After you set up amerchant
bank account, you can use the new details to set up a new DataCash account, obtaining new
client and password data along the way. You also need to change the URL for the DataCash
server that you send data to, because it needs to be the production server instead of the testing
server. Other than removing the test user accounts from the database and moving the web
site to an Internet location, this is all you need to do before exposing the newly completed
e-commerce application to customers.
Working with Authorize.net
To test Authorize.net, you need to apply for a test account at http://developer.authorize.net/
testaccount/. The main page where developers can get information on Authorize.net integration
is http://developer.authorize.net/.
Communicating with Authorize.net is different from communicating with DataCash. Instead
of sending and receiving XML files, we send strings consisting of name-value pairs, separated by
ampersands (&). Effectively, we use a similar syntax to query strings appended to URLs.
Authorize.net returns the transaction results in the form of a string that contains the return
values (without their names) separated by a character that we will specify when making the
initial request.
Pages:
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758