payabli / payabli
Payabli PHP Library
Installs: 6
Dependents: 0
Suggesters: 0
Security: 0
Stars: 1
Watchers: 0
Forks: 0
Open Issues: 0
pkg:composer/payabli/payabli
Requires
- php: ^8.1
- ext-json: *
- guzzlehttp/guzzle: ^7.4
Requires (Dev)
- friendsofphp/php-cs-fixer: 3.5.0
- phpstan/phpstan: ^1.12
- phpunit/phpunit: ^9.0
README
The Payabli PHP library provides convenient access to the Payabli APIs from PHP.
Documentation
API reference documentation is available here.
Requirements
This SDK requires PHP ^8.1.
Installation
composer require payabli/payabli
Usage
Instantiate and use the client with the following:
<?php namespace Example; use Payabli\PayabliClient; use Payabli\MoneyIn\Requests\RequestPayment; use Payabli\MoneyIn\Types\TransRequestBody; use Payabli\Types\PayorDataRequest; use Payabli\Types\PaymentDetail; use Payabli\Types\PayMethodCredit; $client = new PayabliClient( apiKey: '<value>', ); $client->moneyIn->getpaid( new RequestPayment([ 'body' => new TransRequestBody([ 'customerData' => new PayorDataRequest([ 'customerId' => 4440, ]), 'entryPoint' => 'f743aed24a', 'ipaddress' => '255.255.255.255', 'paymentDetails' => new PaymentDetail([ 'serviceFee' => 0, 'totalAmount' => 100, ]), 'paymentMethod' => new PayMethodCredit([ 'cardcvv' => '999', 'cardexp' => '02/27', 'cardHolder' => 'John Cassian', 'cardnumber' => '4111111111111111', 'cardzip' => '12345', 'initiator' => 'payor', 'method' => 'card', ]), ]), ]), );
Exception Handling
When the API returns a non-success status code (4xx or 5xx response), an exception will be thrown.
use Payabli\Exceptions\PayabliApiException; use Payabli\Exceptions\PayabliException; try { $response = $client->moneyIn->getpaid(...); } catch (PayabliApiException $e) { echo 'API Exception occurred: ' . $e->getMessage() . "\n"; echo 'Status Code: ' . $e->getCode() . "\n"; echo 'Response Body: ' . $e->getBody() . "\n"; // Optionally, rethrow the exception or handle accordingly. }
Advanced
Custom Client
This SDK is built to work with any HTTP client that implements Guzzle's ClientInterface.
By default, if no client is provided, the SDK will use Guzzle's default HTTP client.
However, you can pass your own client that adheres to ClientInterface:
use Payabli\PayabliClient; // Create a custom Guzzle client with specific configuration. $customClient = new \GuzzleHttp\Client([ 'timeout' => 5.0, ]); // Pass the custom client when creating an instance of the class. $client = new PayabliClient(options: [ 'client' => $customClient ]); // You can also utilize the same technique to leverage advanced customizations to the client such as adding middleware $handlerStack = \GuzzleHttp\HandlerStack::create(); $handlerStack->push(MyCustomMiddleware::create()); $customClient = new \GuzzleHttp\Client(['handler' => $handlerStack]); // Pass the custom client when creating an instance of the class. $client = new PayabliClient(options: [ 'client' => $customClient ]);
Retries
The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).
A request is deemed retryable when any of the following HTTP status codes is returned:
Use the maxRetries request option to configure this behavior.
$response = $client->moneyIn->getpaid( ..., options: [ 'maxRetries' => 0 // Override maxRetries at the request level ] );
Timeouts
The SDK defaults to a 30 second timeout. Use the timeout option to configure this behavior.
$response = $client->moneyIn->getpaid( ..., options: [ 'timeout' => 3.0 // Override timeout to 3 seconds ] );
Contributing
While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!
On the other hand, contributions to the README are always very welcome!