An official PHP SDK for interacting with Xsolla API
This SDK can be used for:
- obtaining an authorization token
- processing of basic webhooks (user_validation, payment, refund, etc)
- Full customisation of Payment UI with the help of different methods of getting token.
- Client for all API methods, making your integration easy and convenient. You can use it for setting up and updating virtual currency, items and subscription plans, for managing the users balance, for checking the finance information with the help of Report API and so on.
- Convenient webhook server:
- To start you need only one callback function.
- All security checking already implemented: signature authentication and IP whitelisting.
- Full customisation of notification processing logic, if standard server class doesn’t suit you.
- SDK is built on Guzzle v3, and utilizes many of its features, including persistent connections, parallel requests, events and plugins (via Symfony2 EventDispatcher), service descriptions, over-the-wire logging, caching, flexible batching, and request retrying with truncated exponential back off.
- PHP ^7.3 or ^8.0
- The following PHP extensions are required:
- curl
- json
Please register your Publisher Account and create the project. In order to use the PHP SDK Library you'll need:
- MERCHANT_ID
- API_KEY
- PROJECT_ID
- PROJECT_KEY
You can obtain these parameters using the information in your Company Profile and Project Settings.
The recommended way to install Xsolla SDK for PHP is through Composer.
$ cd /path/to/your/project
$ composer require xsolla/xsolla-sdk-phpAfter installing, you need to require Composer's autoloader:
require '/path/to/vendor/autoload.php';You can download the packaged phar and include it in your scripts to get started:
require '/path/to/xsolla.phar';You can download the zip file, unzip it into your project to a location of your choosing, and include the autoloader:
require '/path/to/xsolla-autoloader.php';To integrate Payment UI into your game you should obtain an access token. An access token is a string that identifies game, user and purchase parameters.
There are number of ways for getting token. The easiest one is to use the createCommonPaymentUIToken method, you will need to pass only ID of project in Xsolla system and ID of the user in your game:
<?php
use Xsolla\SDK\API\XsollaClient;
$client = XsollaClient::factory(array(
'merchant_id' => MERCHANT_ID,
'api_key' => API_KEY
));
$paymentUIToken = $client->createCommonPaymentUIToken(PROJECT_ID, USER_ID, $sandboxMode = true);Render Payment UI script in your page:
<html>
<head lang="en">
<meta charset="UTF-8">
</head>
<body>
<button data-xpaystation-widget-open>Buy Credits</button>
<?php \Xsolla\SDK\API\PaymentUI\PaymentUIScriptRenderer::send($paymentUIToken, $isSandbox = true); ?>
</body>
</html>There is a build in server class to help you to handle the webhooks.
<?php
use Xsolla\SDK\Webhook\WebhookServer;
use Xsolla\SDK\Webhook\Message\Message;
use Xsolla\SDK\Exception\Webhook\XsollaWebhookException;
$callback = function (Message $message) {
switch ($message->getNotificationType()) {
case Message::USER_VALIDATION:
/** @var Xsolla\SDK\Webhook\Message\UserValidationMessage $message */
// TODO if user not found, you should throw Xsolla\SDK\Exception\Webhook\InvalidUserException
break;
case Message::PAYMENT:
/** @var Xsolla\SDK\Webhook\Message\PaymentMessage $message */
// TODO if the payment delivery fails for some reason, you should throw Xsolla\SDK\Exception\Webhook\XsollaWebhookException
break;
case Message::REFUND:
/** @var Xsolla\SDK\Webhook\Message\RefundMessage $message */
// TODO if you cannot handle the refund, you should throw Xsolla\SDK\Exception\Webhook\XsollaWebhookException
break;
default:
throw new XsollaWebhookException('Notification type not implemented');
}
};
$webhookServer = WebhookServer::create($callback, PROJECT_KEY);
$webhookServer->start();Once you've finished the handling of notifications on your server, please set up the URL that will receive all webhook notifications on the Settings page for your project.
You can find solutions for the most frequently encountered errors in our documentation.
Please take a look at the CONTRIBUTING.md to see how to get your changes merged in.