Skip to content

Commit a9ed8ad

Browse files
authored
Merge pull request #5 from CyberSource/cybersource-rest-client-readme-changes
Cybersource rest client readme changes
2 parents 2a413a2 + 6f9f1ae commit a9ed8ad

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ An authentication test sample is provided and can be run with the following comm
3434
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.
3535

3636
### 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:
3838
```javascript
3939
// For PRODUCTION use
4040
ctrl.setEnvironment(SDKConstants.endpoint.production);
@@ -45,12 +45,12 @@ API credentials are different for each environment, so be sure to switch to the
4545

4646
## SDK Usage Examples and Sample Code
4747
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)
4949

5050
In that respository, we have comprehensive sample code for all common uses of our API:
5151

5252
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)
5454

5555
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.
5656

@@ -64,7 +64,7 @@ The API Reference Guide provides examples of what information is needed for a pa
6464
`mocha test/<testfile>`
6565

6666
### 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.
6868

6969

7070
## License

0 commit comments

Comments
 (0)