Nimbbl Server Kits are backend SDKs that simplify server-side integration with Nimbbl APIs. Instead of writing raw HTTP requests, you use language-native methods to create orders, verify payments, and manage transactions. The kits handle authentication, request formatting, and response parsing so you can focus on your application logic.
Server Kits are used alongside Standard Checkout client SDKs or directly with the API Reference for custom integrations. They cover the server-side half of the integration — creating orders, verifying payment signatures, and processing refunds.
Why use a Server Kit?
You can call Nimbbl APIs directly with raw HTTP requests, but Server Kits give you several advantages:
- Automatic authentication — the SDK manages token generation and refresh. You never construct auth headers manually.
- Less boilerplate — one method call replaces building HTTP requests, setting headers, parsing JSON responses, and handling errors.
- Type-safe methods — language-native classes and methods catch integration mistakes at development time, not in production.
- Consistent error handling — the SDK surfaces API errors as typed exceptions you can catch and handle cleanly.
Use a Server Kit when you want to move fast and keep your integration code maintainable. Use the API Reference directly when you need fine-grained control or work in a language without an SDK.
Available Server Kits
PHP SDK
The PHP SDK provides wrapper methods for all core Nimbbl API operations. It is namespaced under Nimbbl\Api and installed via GitHub releases. Works with PHP 7.4 and above.
Get started with the PHP SDK →
.NET SDK
The .NET SDK provides the same API coverage for .NET applications. It supports NuGet-based installation, async/await patterns, and optional payload encryption. Works with .NET Standard 2.0 and above.
Get started with the .NET SDK →