SDKs
SDKs
IZI Pay has official libraries (SDKs) for Python, .NET and PHP. They all do the same things and behave the same way, so pick the one in your application's language. Each one talks to the Payment API for you.
| Python | .NET | PHP | |
|---|---|---|---|
| Package | izipay on PyPI | IziPay on NuGet | izipay/izipay-php on Packagist |
| Needs | Python 3.11 or later | .NET 10 or later | PHP 8.3 or later, Composer |
| Fits well with | Django, Flask, FastAPI, Odoo, scripts | ASP.NET Core, worker services, console apps | Laravel, Symfony, plain PHP |
| Sync or async | Both: IziPay and AsyncIziPay | Async (await every call) | Sync |
| Guide | Python SDK | .NET SDK | PHP SDK |
Install
What every SDK does
- Gets the access token with your Client ID and Client Secret, and renews it before it expires.
- Creates payments with every method: payment by reference, Multicaixa Express purchase on the customer's phone, QR Code, Webframe checkout page, and authorization with capture.
- Reads, lists and follows payments, and manages payment references, refunds, terminals and your IZI Pay bill.
- Retries temporary failures only when repeating the request cannot charge or refund twice, and sends an idempotency key with every new payment.
- Turns every API error into one family of exceptions, with IZI Pay's own error code and a trace ID for support.
- Checks and reads the webhooks IZI Pay sends you, and builds the answer IZI Pay expects.
- Never writes tokens, secrets, request bodies or phone numbers to your logs.
Versions
All three SDKs are in beta or preview: method names can still change before version 1.0. Each guide names the exact version it describes. Install that version and keep it fixed in your project until you have tested a newer one.
Using WooCommerce or Odoo?
You don't need an SDK: the ready-made plugins connect your shop to IZI Pay without writing code.
To call the API without an SDK, start with Authentication and the Payment API reference.
Last modified on