You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Before creating pull requests, read [the contributors guide](CONTRIBUTING.md).
20
20
21
21
### TLS 1.2
22
-
The Authorize.Net API only support connections using the TLS 1.2 security protocol. Make sure to upgrade all required components to support TLS 1.2. Keep these components up to date to mitigate the risk of new security flaws.
22
+
The Authorize.Net APIs only support connections using the TLS 1.2 security protocol. Make sure to upgrade all required components to support TLS 1.2. Keep these components up to date to mitigate the risk of new security flaws.
23
23
24
24
25
25
## Installation
@@ -32,9 +32,9 @@ Use of this SDK and the Authorize.Net APIs requires having an account on the Aut
32
32
If you don't currently have a production Authorize.Net account, [sign up for a sandbox account](https://developer.authorize.net/sandbox/).
33
33
34
34
### Authentication
35
-
To authenticate with the Authorize.Net API, use your account's API Login ID and Transaction Key. If you don't have these credentials, obtain them from the Merchant Interface. For production accounts, the Merchant Interface is located at (https://account.authorize.net/), and for sandbox accounts, at (https://sandbox.authorize.net).
35
+
To authenticate with the Authorize.Net API, use your account's API Login ID and Transaction Key. If you don't have these credentials, obtain them from the Merchant Interface. For production accounts, the Merchant Interface is located at (https://account.authorize.net/); and for sandbox accounts, at (https://sandbox.authorize.net).
36
36
37
-
After you have your credentials, load them into the appropriate variables in your code. The below sample code shows how to set the credentials as part of the API request.
37
+
After you have obtained your credentials, load them into the appropriate variables in your code. The below sample code shows how to set the credentials as part of the API request.
38
38
39
39
#### To set your API credentials for an API request:
40
40
```csharp
@@ -46,10 +46,10 @@ ApiOperationBase<ANetApiRequest, ANetApiResponse>.MerchantAuthentication = new m
46
46
};
47
47
```
48
48
49
-
Never include your API Login ID and Transaction Key directly in a file in a publically accessible portion of your website. As a best practice, define the API Login ID and Transaction Key in a constants file, and then reference those constants in your code.
49
+
Never include your API Login ID and Transaction Key directly in a file in a publically accessible portion of your website. As a best practice, define the API Login ID and Transaction Key in a constants file, and reference those constants in your code.
50
50
51
51
### Switching between the sandbox environment and the production environment
52
-
Authorize.Net maintains a complete sandbox environment for testing and development purposes. The sandbox environment is an exact duplicate of our production environment, with simulated transaction authorization and settlement. By default, this SDK is configured to use the sandbox environment. To switch to the production environment, set the appropriate environment constant using ApiOperationBase `RunEnvironment` method. For example:
52
+
Authorize.Net maintains a complete sandbox environment for testing and development purposes. The sandbox environment is an exact replica of our production environment, with simulated transaction authorization and settlement. By default, this SDK is configured to use the sandbox environment. To switch to the production environment, set the appropriate environment constant using ApiOperationBase `RunEnvironment` method. For example:
@@ -130,7 +130,7 @@ If you have previously enabled logging in your application, configurations will
130
130
</system.diagnostics>
131
131
</configuration>
132
132
```
133
-
As of now, two types of listeners, viz. `TextListener` and `ConsoleListener` are supported with the logger. The corresponding listener types `AuthorizeNet.Util.SensitiveDataTextLogger` and `AuthorizeNet.Util.SensitiveDataConsoleLogger` mask the sensitive data before logging into log file and console respectively.
133
+
As of now, two types of listeners, viz. `TextListener` and `ConsoleListener` are supported with the logger. The corresponding sensitive listener types `AuthorizeNet.Util.SensitiveDataTextLogger` and `AuthorizeNet.Util.SensitiveDataConsoleLogger` mask the sensitive data before logging into log file and console respectively.
134
134
135
135
The sensitive fields that are masked during logging are:
0 commit comments