Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
cybersource-rest-client
Advanced tools
The CyberSource Node client provides convenient access to the CyberSource REST API from your Node application.
npm install cybersource-rest-client
Use of this SDK and the CyberSource APIs requires having an account on our system. You can find details of getting a test account and creating your keys here
Remember this SDK is for use in server-side Node applications that access the CyberSource REST API and credentials should always be securely stored and accessed appropriately.
To get started using this SDK, it's highly recommended to download our sample code repository:
In that respository, we have comprehensive sample code for all common uses of our API:
Additionally, you can find details and examples of how our API is structured in our API Reference Guide:
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.
A Meta Key is a single key that can be used by one, some, or all merchants (or accounts, if created by a Portfolio user) in the portfolio.
The Portfolio or Parent Account owns the key and is considered the transaction submitter when a Meta Key is used, while the merchant owns the transaction.
MIDs continue to be able to create keys for themselves, even if a Meta Key is generated.
Further information on MetaKey can be found in New Business Center User Guide.
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, set the runEnvironment
in the SDK Configuration. See our sample at https://github.com/CyberSource/cybersource-rest-samples-node/blob/master/Data/Configuration.js.
// For TESTING use
const RunEnvironment = "cybersource.environment.sandbox";
// For PRODUCTION use
const RunEnvironment = "cybersource.environment.production";
API credentials are different for each environment, so be sure to switch to the appropriate credentials when switching environments.
This repository is distributed under a proprietary license. See the provided LICENSE.txt
file.
FAQs
Node.js SDK for the CyberSource REST API
The npm package cybersource-rest-client receives a total of 1,823 weekly downloads. As such, cybersource-rest-client popularity was classified as popular.
We found that cybersource-rest-client demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.