developer:guide:testaccount

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
developer:guide:testaccount [2017/04/04 14:15]
kat
developer:guide:testaccount [2018/05/04 08:15] (current)
kat
Line 14: Line 14:
   * If you are a developer and your client, the merchant, has not setup a live gateway account a sandbox account will allow you to develop your application without delay. The sandbox environment mimics the Merchant Console (live account) exactly so you can expect the same results when switching to the live account once it's setup. Your application will only need to swap the source key from the developer one to the live one.    * If you are a developer and your client, the merchant, has not setup a live gateway account a sandbox account will allow you to develop your application without delay. The sandbox environment mimics the Merchant Console (live account) exactly so you can expect the same results when switching to the live account once it's setup. Your application will only need to swap the source key from the developer one to the live one. 
   * Test Mode on our live servers is extremely limited and unfriendly in terms of developing an application. It does not generate a fake approval code other than TESTMD and it does not store a transaction record for you to look up. Further most of the result fields come back blank. This was done on purpose to keep our live server clean of test transactions and reserved for actual live transactions only. A sandbox account will generate approval codes for you, return all the variables you request as well as store a transaction record for you to report on. We keep test mode functional on the live servers because it is a legacy feature that older customers are used to.    * Test Mode on our live servers is extremely limited and unfriendly in terms of developing an application. It does not generate a fake approval code other than TESTMD and it does not store a transaction record for you to look up. Further most of the result fields come back blank. This was done on purpose to keep our live server clean of test transactions and reserved for actual live transactions only. A sandbox account will generate approval codes for you, return all the variables you request as well as store a transaction record for you to report on. We keep test mode functional on the live servers because it is a legacy feature that older customers are used to. 
 +  * The sandbox does not support encrypted swipe or EMV testing. It does support un encrypted and manual entries on the devices. ​
  
 ====== Switching over from Development to Production ====== ====== Switching over from Development to Production ======
 When testing and development is completed switch the source key to the key generated from the live account and change the processing URL from **sandbox**.usaepay.com/​gate to **www**.usaepay.com/​gate When testing and development is completed switch the source key to the key generated from the live account and change the processing URL from **sandbox**.usaepay.com/​gate to **www**.usaepay.com/​gate
developer/guide/testaccount.txt ยท Last modified: 2018/05/04 08:15 by kat

Page Tools