Difference between revisions of "Configuring Authorize.NET"
LeonTorres (talk | contribs) (→Test Mode using Test Account) |
LeonTorres (talk | contribs) (→Test Mode using Test Account) |
||
| Line 11: | Line 11: | ||
=== Test Mode using Test Account === | === Test Mode using Test Account === | ||
| − | This mode is where you use a separate Authorize.NET testing account on | + | This mode is where you use a separate Authorize.NET testing account on a special test Authorize.NET server. |
Unlike the previous mode, this one creates test transactions that can be authorized, captured, voided and refunded. This mode should be used for development purposes and for trial runs of the production system. It can be used only with a separate testing account distinct from the one used for production. A testing account can be obtained from the following URL, | Unlike the previous mode, this one creates test transactions that can be authorized, captured, voided and refunded. This mode should be used for development purposes and for trial runs of the production system. It can be used only with a separate testing account distinct from the one used for production. A testing account can be obtained from the following URL, | ||
| Line 17: | Line 17: | ||
http://developer.authorize.net/testaccount/ | http://developer.authorize.net/testaccount/ | ||
| − | To properly configure this mode, you need to log into your Authorize.NET test account with the login name and password provided by Authorize.NET and turn test mode off. The | + | To properly configure this mode, you need to log into your Authorize.NET test account with the login name and password provided by Authorize.NET and turn test mode off. (This test server behaves like the real thing with the exception that it never sends info to financial institutions, thus it has a test mode just like the live site.) The information for accessing your account is provided after you finish registration. |
Furthermore, you will need to change the gateway URL in payment.properties to the following, | Furthermore, you will need to change the gateway URL in payment.properties to the following, | ||
payment.authorizedotnet.url=https://test.authorize.net/gateway/transact.dll | payment.authorizedotnet.url=https://test.authorize.net/gateway/transact.dll | ||
Revision as of 23:40, 14 November 2007
Testing Setup
Authorize.NET has two very different settings with regards to testing,
Test Mode using Live Credentials
This mode is where you use your actual credentials on the live Authorize.NET server. It is activated by passing a special flag.
No actual transactions will be created by Authorize.NET in this mode. That means it is unsuitable for testing authorizations, captures, refunds and voids. It should be treated only as a way to ensure that a connection with the live server is established.
Test Mode using Test Account
This mode is where you use a separate Authorize.NET testing account on a special test Authorize.NET server.
Unlike the previous mode, this one creates test transactions that can be authorized, captured, voided and refunded. This mode should be used for development purposes and for trial runs of the production system. It can be used only with a separate testing account distinct from the one used for production. A testing account can be obtained from the following URL,
http://developer.authorize.net/testaccount/
To properly configure this mode, you need to log into your Authorize.NET test account with the login name and password provided by Authorize.NET and turn test mode off. (This test server behaves like the real thing with the exception that it never sends info to financial institutions, thus it has a test mode just like the live site.) The information for accessing your account is provided after you finish registration.
Furthermore, you will need to change the gateway URL in payment.properties to the following,
payment.authorizedotnet.url=https://test.authorize.net/gateway/transact.dll
