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