Version 4.0.0 is here!
We improved the initialization of SDK making it easier to understand the available options.
NowNASaccounts are the default instance for the SDK andABCstructure was moved to apreviousprefixes.
If you have been using this SDK before, you may find the following important changes:
- Marketplace module was moved to Accounts module, same for classes and references.
- In most cases, IDE can help you determine from where to import, but if you’re still having issues don't hesitate to open a ticket.
🚀 Please check in GitHub releases for all the versions available.
This SDK can be used with two different pair of API keys provided by Checkout. However, using different API keys imply using specific API features.
Please find in the table below the types of keys that can be used within this SDK.
| Account System | Public Key (example) | Secret Key (example) |
|---|---|---|
| Default | pk_pkhpdtvabcf7hdgpwnbhw7r2uic | sk_m73dzypy7cf3gf5d2xr4k7sxo4e |
| Previous | pk_g650ff27-7c42-4ce1-ae90-5691a188ee7b | sk_gk3517a8-3z01-45fq-b4bd-4282384b0a64 |
Note: sandbox keys have a sbox_ or test_ identifier, for Default and Previous accounts respectively.
PLEASE NEVER SHARE OR PUBLISH YOUR CHECKOUT CREDENTIALS.
If you don't have your own API keys, you can sign up for a test account here.
Default keys client instantiation can be done as follows:
ICheckoutApi api = CheckoutSdk.Builder().StaticKeys()
.PublicKey("public_key") // optional, only required for operations related with tokens
.SecretKey("secret_key")
.Environment(Environment.Sandbox)
.EnvironmentSubdomain("subdomain") // optional, Merchant-specific DNS name
.LogProvider(logFactory) // optional
.HttpClientFactory(httpClientFactory) // optional
.Build();
The SDK supports client credentials OAuth, when initialized as follows:
ICheckoutApi api = CheckoutSdk.Builder().OAuth()
.ClientCredentials("client_id", "client_secret")
.AuthorizationUri(new Uri("https://access.sandbox.checkout.com/connect/token")) // custom authorization URI, optional
.Scopes(OAuthScope.Files, OAuthScope.Flow) // array of scopes, optional
.Environment(Environment.Sandbox)
.EnvironmentSubdomain("subdomain") // optional, Merchant-specific DNS name
.LogProvider(logFactory) // optional
.HttpClientFactory(httpClientFactory) // optional
.Build();If your pair of keys matches the previous system type, this is how the SDK should be used:
Checkout.Previous.ICheckoutApi api = CheckoutSdk.Builder()
.Previous()
.StaticKeys()
.PublicKey("public_key") // optional, only required for operations related with tokens
.SecretKey("secret_key")
.Environment(Environment.Sandbox)
.EnvironmentSubdomain("subdomain") // optional, Merchant-specific DNS name
.LogProvider(logFactory) // optional
.HttpClientFactory(httpClientFactory) // optional
.Build();Then just get any client, and start making requests:
var paymentResponse = await api.PaymentsClient().RequestPayment(new PaymentRequest());The CheckoutSDK.Extensions.Microsoft package makes it easier to add the Checkout SDK to your .NET Core applications.
Initialize the Configuration of your appsettings.json file:
{
"Checkout": {
"SecretKey": "secret_key",
"PublicKey": "public_key",
"Environment": "Sandbox",
"PlatformType": "Default"
}
}You can chose PlatformType Default or Previous depending of the type of keys and account system access.
For OAuth, the configuration file should include the following properties:
{
"Checkout": {
"ClientId": "client_id",
"ClientSecret": "client_secret",
"AuthorizationUri": "https://access.sandbox.checkout.com/connect/token",
"Scopes": ["vault", "fx"],
"Environment": "Sandbox",
"PlatformType": "DefaultOAuth"
}
}Use Environment enum value to choose the desired environment for the SDK, and PlatformType value to choose between the different Account Settings. Then add the configuration:
public class Startup
{
public IConfigurationRoot Configuration { get; set; }
public Startup(IWebHostEnvironment env)
{
var builder = new ConfigurationBuilder()
.SetBasePath(env.ContentRootPath)
.AddJsonFile("appsettings.json", optional: true, reloadOnChange: true);
Configuration = builder.Build();
}
}Register the CheckoutSdk:
public void ConfigureServices(IServiceCollection services)
{
// LogFactory and HttpClientFactory are optional
CheckoutServiceCollection.AddCheckoutSdk(services, configuration, logFactory, httpClientFactory);
}Then take a dependency on ICheckoutApi in your class constructor:
public class CheckoutController : ControllerBase
{
private readonly ICheckoutApi _api;
public CheckoutController(ICheckoutApi api)
{
_api = api;
}
}Please note again that there are 2 different ICheckoutApi interfaces, depending on the way the SDK is built.
Sometimes you need a custom thread pool, or any custom http property, so you can provide your own httpClient configuration as follows.
// Create a custom class from IHttpClientFactory
private class CustomClientFactory : IHttpClientFactory
{
public HttpClient CreateClient()
{
var handler = new HttpClientHandler();
handler.DefaultProxyCredentials = CredentialCache.DefaultCredentials;
var httpClient = new HttpClient(handler);
httpClient.Timeout = TimeSpan.FromSeconds(2);
return httpClient;
}
}
ICheckoutApi api = CheckoutSdk.Builder().StaticKeys()
.SecretKey("secret_key")
.Environment(Environment.Sandbox)
.EnvironmentSubdomain("subdomain") // optional, Merchant-specific DNS name
.HttpClientFactory(new CustomClientFactory()) // optional
.Build();The SDK supports custom LogProvider that extends from Microsoft.Extensions.Logging ILoggerFactory, you need to provide your configuration as follows.
var logFactory = new NLogLoggerFactory();
_log = logFactory.CreateLogger(typeof(SandboxTestFixture));
ICheckoutApi api = CheckoutSdk.Builder().StaticKeys()
.SecretKey("secret_key")
.Environment(Environment.Sandbox)
.EnvironmentSubdomain("subdomain") // optional, Merchant-specific DNS name
.LogProvider(logFactory)
.Build();All the API responses that do not fall in the 2** status codes will cause a CheckoutApiException. The exception encapsulates
the requestId, httpStatusCode and a map of errorDetails, if available.
Once you check out the code from GitHub, the project can be built using the netcore CLI tools:
dotnet build
# run tests
dotnet test
The execution of integration tests require the following environment variables set in your system:
- For Default account systems (NAS):
CHECKOUT_DEFAULT_PUBLIC_KEY&CHECKOUT_DEFAULT_SECRET_KEY - For Default account systems (OAuth):
CHECKOUT_DEFAULT_OAUTH_CLIENT_ID&CHECKOUT_DEFAULT_OAUTH_CLIENT_SECRET - For Previous account systems (ABC):
CHECKOUT_PREVIOUS_PUBLIC_KEY&CHECKOUT_PREVIOUS_SECRET_KEY
Please refer to Code of Conduct