Sandbox Accounts vs. Live Accounts – Which Does What Anyway?

by Administrator Administrator on ‎01-10-2011 01:55 PM - last edited on ‎03-11-2014 03:04 PM by Administrator Administrator (87,535 Views)

Testing is a crucial part of getting your payment gateway account set up. As such, Authorize.Net offers a few different ways for you to test your connection. We offer sandbox accounts in a testing environment that mimics the functionality of our production environment. You can test your connection and submit transactions to the sandbox, but as it is only a test environment, no transaction data will ever be sent on to a bank.


We also offer a Test Mode option on all live accounts which allows you to test connecting to the production environment. All new production accounts are automatically placed in Test Mode, which must be turned off before you can process real transactions.


By far, the most common and recommended way of testing is to build your connection using a sandbox account and test in the sandbox environment. Then when you’re ready to go live, you simply change the API Login ID and Transaction Key from your sandbox credentials to your production credentials, and change the posting URL from the sandbox URL to the production URL, and you’re ready to go.


Common Questions
As you do your testing, you will inevitably encounter some questions and areas of confusion. Here are some of the most common issues we see:

  • The sandbox and production environments are completely separate. You cannot use your sandbox account API Login ID and Transaction Key on the production server, nor can you use your prodicution account’s credentials with  the sandbox. If you do, you will receive an Error 13. Always make sure that if you are posting to the sandbox (https://test.authorize.net/gateway/transact.dll) that you are using your sandbox account’s API Login ID and Transaction Key. If you are posting to the production server (https://secure.authorize.net/gateway/transact.dll) then you must use your production account’s credentials.
  • There is no reason to place your sandbox account into Test Mode.
  • Transactions that are run in the production environment in Test Mode are not stored anywhere and will return a transaction ID of zero. There will be no history of them. However, transactions run in the sandbox is available in the transaction history, which is another reason why a sandbox  is the recommended method of testing.
  • In the sandbox, any transactions run whether using a test credit card or a real account will NEVER actually be charged. The sandbox environment does not send data to any banks.
  • On that note, test credit cards are real card numbers but they are not actually linked to a credit card account.

 

Key Differences

  • eChecks do not settle in the sandbox.
  • All sandbox accounts have eCheck.Net enabled by default, whereas if you would like eCheck.Net in your live account, you will need to apply for it.

Lastly, one thing that you can do with your sandbox account that you cannot do with your live account is trigger certain transaction responses, namely declines, AVS/CCV responses and partial authorization responses. Visit the Error Generation Guide page for more details. 

 

Hopefully this post will help in your future testing. Thanks for reading!

Comments
by indra-int
on ‎05-16-2013 11:25 PM

I am now using the live account without test mode. But when I give the test credit card details authorize.net returns the subscription id like this 5225885028. Why it is returns the subscription id instead of error that I an using the invalid credit card details? When I loggedin to my account the transaction status is showing General Error. But every time I got the subscription id.

 

 

CAn anybody help?

by jlarheir
on ‎11-05-2015 11:50 AM

Thanks for this post, very helpful.  I have one basic question as we move a project into the production side of authorize.net...  Are there *test* credit cards that we can use in production *not* in test mode?  Or is the practice to use one of the Sandbox test credit cards (http://developer.authorize.net/hello_world/testing_guide/, it doesn't say it doesn't work in prod) in test mode, then switch to production and test with a real card? 

 

Thanks,

Jim

by Administrator Administrator
on ‎11-05-2015 12:16 PM

Hello @jlarheir

 

Test credit cards will only work in the sandbox, they cannot be used in your production gateway.

 

Richard

by pzelnip
on ‎02-12-2016 04:14 PM

For the new changes to urls to make use of Akamai, the blog post (http://www.authorize.net/support/akamaifaqs/#newurls) mentions a new production server url.

 

Is there a corresponding new sandbox url?  I want to ensure my integration works with Akamai, but there's no sandbox url to test that with mentioned.

by davidgauvreau1
on ‎02-24-2016 12:49 PM

I have the same question as pzelnip. 

 

In the Akamai blog post there is the following statement : Akamai is available for testing now in our sandbox environment.

 

Do I have to use a different sandbox url to test the Akamai integration or the following url is the one to use : https://test.authorize.net/gateway/transact.dll

 

by xucaen
on ‎09-23-2016 11:33 AM

How exactly do I turn on "Live Mode"? 

by Nilam
on ‎11-08-2016 08:21 PM

Can anyone tell me which link can i use for JSOn request to authorize.net chargecreditcart method ?