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
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ An authentication test sample is provided and can be run with the following comm
34
34
You should never include your Login ID and Transaction Key directly in a file that's in a publically accessible portion of your website. A better practice would be to define these in a constants file, and then reference those constants in the appropriate place in your code.
35
35
36
36
### Switching between the sandbox environment and the production environment
37
-
Authorize.Net maintains a complete sandbox environment for testing and development purposes. This sandbox environment is an exact duplicate of our production environment with the transaction authorization and settlement process simulated. By default, this SDK is configured to communicate with the sandbox environment. To switch to the production environment, call `setEnvironment` on the controller variable before execute. For example:
37
+
Cybersource maintains a complete sandbox environment for testing and development purposes. This sandbox environment is an exact duplicate of our production environment with the transaction authorization and settlement process simulated. By default, this SDK is configured to communicate with the sandbox environment. To switch to the production environment, call `setEnvironment` on the controller variable before execute. For example:
@@ -45,12 +45,12 @@ API credentials are different for each environment, so be sure to switch to the
45
45
46
46
## SDK Usage Examples and Sample Code
47
47
To get started using this SDK, it's highly recommended to download our sample code repository:
48
-
*[Authorize.Net Node.js Sample Code Repository (on GitHub)](https://github.com/AuthorizeNet/sample-code-node)
48
+
*[Cybersource Node.js Sample Code Repository (on GitHub)](https://github.com/CyberSource/cybersource-rest-samples-node)
49
49
50
50
In that respository, we have comprehensive sample code for all common uses of our API:
51
51
52
52
Additionally, you can find details and examples of how our API is structured in our API Reference Guide:
53
-
*[Developer Center API Reference](http://developer.authorize.net/api/reference/index.html)
53
+
*[Developer Center API Reference](https://developer.cybersource.com/api/reference/api-reference.html)
54
54
55
55
The API Reference Guide provides examples of what information is needed for a particular request and how that information would be formatted. Using those examples, you can easily determine what methods would be necessary to include that information in a request using this SDK.
56
56
@@ -64,7 +64,7 @@ The API Reference Guide provides examples of what information is needed for a pa
64
64
`mocha test/<testfile>`
65
65
66
66
### Testing Guide
67
-
For additional help in testing your own code, Authorize.Net maintains a [comprehensive testing guide](http://developer.authorize.net/hello_world/testing_guide/) that includes test credit card numbers to use and special triggers to generate certain responses from the sandbox environment.
67
+
For additional help in testing your own code, Authorize.Net maintains a [comprehensive testing guide](https://developer.cybersource.com/hello-world/testing-guide.html) that includes test credit card numbers to use and special triggers to generate certain responses from the sandbox environment.
0 commit comments