The CyberSource .NET client provides convenient access to the CyberSource REST API from your .NET application.
- .NET Standard 2.0
- Nuget Package Manager
PM> Install-Package CyberSource.Rest.Client.CoreUse 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 .NET 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.
OAuth enables service providers to securely share access to customer data without sharing password data.
The CyberSource OAuth2.0 Authorization Server (or API Auth Service) will issue access tokens (based on merchant user credentials) to CyberSource or third-party Applications. These applications can access CyberSource APIs on the merchant's behalf, using the access tokens.
During application registration, third-party application developers are issued a client_id and optionally a client_secret (if they can be considered a confidential client, for example a web application).
These values will be used when the merchant application wants to request an access token and/or a refresh token. This is explained in more detail in Requesting the Access and Refresh Tokens.
For more detailed information on OAuth, refer to the documentation at Cybersource OAuth 2.0.
In order to use OAuth, set the run environment to OAuth enabled URLs. OAuth only works in these run environments.
// For TESTING use
_configurationDictionary.Add("runEnvironment", "api-matest.cybersource.com")
// For PRODUCTION use
// _configurationDictionary.Add("runEnvironment", "api-ma.cybersource.com")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 property in the SDK Configuration. See our sample at the Configuration.cs class in the Sample Codes repository.
// For TESTING use
_configurationDictionary.Add("runEnvironment", "apitest.cybersource.com");
// For PRODUCTION use
// _configurationDictionary.Add("runEnvironment", "api.cybersource.com");API credentials are different for each environment, so be sure to switch to the appropriate credentials when switching environments.
The base repository uses NLog as a hard dependency instead of using the most common ILogger interface allowing consumers to select their own framework. Most people do not want NLog as a dependency conflicting with their selected logging library, for this reason, this .NET Standard fork removes NLog completely, you're welcome. Errors are already thrown as exceptions so the extra logging (same message) is pointless since the caller can log this.
This repository is distributed under a proprietary license.