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
Next revision
Previous revision
Next revision Both sides next revision
developer:guide:testaccount [2008/10/07 16:15]
vladg added why a developer needs a sandbox account
developer:guide:testaccount [2008/10/07 16:36]
vladg why test mode is the way it is
Line 3: Line 3:
   - To obtain a test account on our sandbox test server please go to the following URL: https://​www.usaepay.com/​developer/​login   - To obtain a test account on our sandbox test server please go to the following URL: https://​www.usaepay.com/​developer/​login
   - This will bring you to a log in page.    - This will bring you to a log in page. 
-  - Please click on “sign up” and fill out the form completely ​to obtain your login credentials. ​+  - Please click on “sign up” and fill out the form COMPLETELY ​to obtain your login credentials
 +  - Leaving any fields blank will delay your account from being setup, regardless of the "​required"​ note
   - Once you hit register you will be inside the developer section. ​   - Once you hit register you will be inside the developer section. ​
   - Please click on “Request Test Account” or the direct URL is: https://​www.usaepay.com/​developer/​request_test_acct.php   - Please click on “Request Test Account” or the direct URL is: https://​www.usaepay.com/​developer/​request_test_acct.php
Line 11: Line 12:
 ====== Why you need a test (developer a.k.a. sandbox) account ====== ====== Why you need a test (developer a.k.a. sandbox) account ======
  
-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
  
developer/guide/testaccount.txt · Last modified: 2018/05/04 08:15 by kat

Page Tools