|
1 | 1 | package net.authorize; |
2 | 2 |
|
3 | | -/** |
4 | | - * Determines which environment to post transactions against. |
5 | | - * By placing the merchant's payment gateway account in Test Mode in the |
6 | | - * Merchant Interface. New payment gateway accounts are placed in Test Mode |
7 | | - * by default. For more information about Test Mode, see the Merchant |
8 | | - * Integration Guide at http://www.authorize.net/support/merchant/. |
9 | | - * |
10 | | - * When processing test transactions in Test Mode, the payment gateway will |
11 | | - * return a transaction ID of "0." This means you cannot test follow-on |
12 | | - * transactions, for example, credits, voids, etc., while in Test Mode. |
13 | | - * To test follow-on transactions, you can either submit x_test_request=TRUE |
14 | | - * as indicated above, or process a test transaction with any valid credit card |
15 | | - * number in live mode, as explained below. |
16 | | - * |
17 | | - * Note: Transactions posted against live merchant accounts using either of |
18 | | - * the above testing methods are not submitted to financial institutions for |
19 | | - * authorization and are not stored in the Merchant Interface. |
20 | | - * |
21 | | - * If testing in the live environment is successful, you are ready to submit |
22 | | - * live transactions and verify that they are being submitted successfully. |
23 | | - * Either remove the x_test_request field from the transaction request string, |
24 | | - * or set it to "FALSE;" or, if you are using Test Mode, turn it off in the |
25 | | - * Merchant Interface. To receive a true response, you must submit a |
26 | | - * transaction using a real credit card number. You can use any valid credit |
27 | | - * card number to submit a test transaction. You can void successful |
28 | | - * transactions immediately to prevent live test transactions from being |
29 | | - * processed. This can be done quickly on the Unsettled Transactions page of |
30 | | - * the Merchant Interface. It is recommended that when testing using a live |
31 | | - * credit card, you use a nominal value, such as $0.01. That way, if you forget |
32 | | - * to void the transaction, the impact will be minimal. For VISA verification |
33 | | - * transactions, submit a $0.00 value instead, if the processor accepts it. |
34 | | - */ |
| 3 | +/*================================================================================ |
| 4 | +* |
| 5 | +* Determines the target environment to post transactions. |
| 6 | +* |
| 7 | +* SANDBOX should be used for testing. Transactions submitted to the sandbox |
| 8 | +* will not result in an actual card payment. Instead, the sandbox simulates |
| 9 | +* the response. Use the Testing Guide to generate specific gateway responses. |
| 10 | +* |
| 11 | +* PRODUCTION connects to the production gateway environment. |
| 12 | +* |
| 13 | +*===============================================================================*/ |
35 | 14 | public enum Environment { |
36 | 15 | SANDBOX("https://test.authorize.net","https://apitest.authorize.net","https://test.authorize.net"), |
37 | | - SANDBOX_TESTMODE("https://test.authorize.net","https://apitest.authorize.net","https://test.authorize.net"), |
38 | | - PRODUCTION("https://secure.authorize.net","https://api.authorize.net","https://cardpresent.authorize.net"), |
39 | | - PRODUCTION_TESTMODE("https://secure.authorize.net","https://api.authorize.net","https://cardpresent.authorize.net"), |
| 16 | + PRODUCTION("https://secure2.authorize.net","https://api2.authorize.net","https://cardpresent.authorize.net"), |
40 | 17 | LOCAL_VM(null,null,null), |
41 | 18 | HOSTED_VM(null,null,null), |
42 | 19 | CUSTOM(null,null,null); |
|
0 commit comments