Version 3.0.0 is here!
We improved the initialization of SDK making it easier to understand the available options.
NowNAS
accounts are the default instance for the SDK andABC
structure was moved to aprevious
prefixes.
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.
{
"require": {
"php": ">=5.6",
"checkout/checkout-sdk-php": "version"
}
}
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:
$checkoutApi = CheckoutSdk::builder()->staticKeys()
->publicKey("public_key") // optional, only required for operations related with tokens
->secretKey("secret_key")
->environment(Environment::sandbox()) // or production()
->logger($logger) //optional, for a custom Logger
->httpClientBuilder($client) // optional, for a custom HTTP client
->build();
$paymentsClient = $checkoutApi->getPaymentsClient();
$paymentsClient->refundPayment("payment_id");
The SDK supports client credentials OAuth, when initialized as follows:
$checkoutApi = CheckoutSdk::builder()->oAuth()
->clientCredentials("client_id", "client_secret")
->scopes([OAuthScope::$Gateway, OAuthScope::$Vault]) // array of scopes
->environment(Environment::sandbox()) // or production()
->logger($logger) //optional, for a custom Logger
->httpClientBuilder($client) // optional, for a custom HTTP client
->build();
$paymentsClient = $checkoutApi->getPaymentsClient();
$paymentsClient->refundPayment("payment_id");
If your pair of keys matches the Previous type, this is how the SDK should be used:
$checkoutApi = CheckoutSdk::builder()
->previous()
->staticKeys()
->environment(Environment::sandbox()) // or production()
->publicKey("public_key") // optional, only required for operations related with tokens
->secretKey("secret_key")
->logger($logger) //optional, for a custom Logger
->httpClientBuilder($client) // optional, for a custom HTTP client
->build();
$paymentsClient = $checkoutApi->getPaymentsClient();
$paymentsClient->refundPayment("payment_id");
For operations that require file upload (Disputes or Marketplace) the configuration extension=fileinfo
must be enabled in the php.ini
.
All the API responses that do not fall in the 2** status codes, the SDK will throw a CheckoutApiException
.
The exception encapsulates http_metadata
and $error_details
, if available.
Once you checkout the code from GitHub, the project can be built using composer:
composer update
The execution of integration tests require the following environment variables set in your system:
- For Default account systems:
CHECKOUT_DEFAULT_PUBLIC_KEY
&CHECKOUT_DEFAULT_SECRET_KEY
-
- For Previous account systems:
CHECKOUT_PREVIOUS_PUBLIC_KEY
&CHECKOUT_PREVIOUS_SECRET_KEY
- For Previous account systems:
Please refer to Code of Conduct