SDKs
SDK updates
This page shows how to update each IZI Pay SDK and what changed in every version, newest first.
Before version 1.0
A new version can still change how something behaves. Read what changed below, update in your test environment and run your tests, then deploy.
How to update
- Python: if your
requirements.txtpins a version (izipay==0.1.0b1), change it to the new one and install again. See your version withpython -c "import izipay; print(izipay.__version__)". - .NET: the command updates the
PackageReferencein your.csprojto the newest preview. To choose a version, use--version 0.1.0-preview.3instead of--prerelease. In Visual Studio, use the NuGet Package Manager with Include prerelease ticked. - PHP:
^0.2@betafrom the install guide allows every 0.2.x version, socomposer updateis enough. Coming from 0.1.x, runcomposer require izipay/izipay-php:^0.2@betaonce (0.2 needs PHP 8.3). See your version withcomposer show izipay/izipay-php.
Versions and support
The SDKs follow Semantic Versioning:
- Before 1.0 (now): a new minor version (for example 0.1 to 0.2) can contain changes that need code changes; the table below says so in Code changes?. A new beta or preview of the same minor version only fixes problems.
- From 1.0: a patch version (1.0.1) fixes problems, a minor version (1.1) adds features without breaking anything, and only a major version (2.0) can remove or change something. Before something is removed, it is first marked as deprecated in a minor version.
- Language versions: each SDK supports the Python, PHP and .NET versions that still get security fixes from their own maintainers. When one stops getting them, a new SDK version can stop supporting it; this page says so. Today: Python 3.11 or later, PHP 8.3 or later, .NET 10.
- Fixes: fixes, including security fixes, go to the newest version. Keep your SDK up to date.
Problems with an SDK? Email suporte@izipay.ao or use Helpdesk in the IZI Pay Portal. Say which SDK and version, the environment (sandbox or production), what you did, and the error's message and trace ID. Never send your Client Secret, access tokens or webhook Access-Key.
Python
Package izipay on PyPI. Guide: Python SDK.
| Version | Date | What changed | Code changes? |
|---|---|---|---|
| 0.2.0b1 | 2026-11-22 | Needs Python 3.11 or later. Usage amounts are described correctly: they are the value of the payments counted, not your fee. | Only if you are on Python 3.10: upgrade Python, or stay on 0.1.0b2 (pip does this for you) |
| 0.1.0b2 | 2026-11-22 | Opening the connection now gives up after 15 seconds, so an unreachable IZI Pay fails within about 45 seconds instead of up to 6 minutes. Waiting for an answer still gets the full time-out. | No |
| 0.1.0b1 | 2026-11-22 | First beta. | - |
.NET
Package IziPay on NuGet. Guide: .NET SDK.
| Version | Date | What changed | Code changes? |
|---|---|---|---|
| 0.1.0-preview.3 | 2026-11-22 | Usage amounts are described correctly: UsageSummary.TotalAmount and UsageRecord.Amount are the value of the payments counted, not your fee. | No |
| 0.1.0-preview.2 | 2026-11-22 | For a payment by reference, CreatedPayment.Id is now the reference number, which GetAsync and RequestStatusSyncAsync accept. The ID returned before moves to the new ReferenceRecordId. | Only if you store Id for payments by reference: it is now the reference number. The old ID never worked with GetAsync. |
| 0.1.0-preview.1 | 2026-11-21 | First preview. | - |
PHP
Package izipay/izipay-php on Packagist. Guide: PHP SDK.
| Version | Date | What changed | Code changes? |
|---|---|---|---|
| 0.2.0-beta.1 | 2026-11-22 | Needs PHP 8.3 or later. Usage amounts are described correctly: they are the value of the payments counted, not your fee. Install with ^0.2@beta. | Only the PHP version: projects on PHP 8.1 or 8.2 stay on 0.1.x |
| 0.1.0-beta.3 | 2026-11-22 | Reports its own version correctly in the User-Agent header (0.1.0-beta.2 still said 0.1.0-beta.1). | No |
| 0.1.0-beta.2 | 2026-11-22 | Works fully with Guzzle 8: a connection that was refused is again retried and reported as ConnectionException. With 0.1.0-beta.1 and Guzzle 8 it counted as "may have been sent". | No. Recommended if you use Guzzle 8 |
| 0.1.0-beta.1 | 2026-11-22 | First beta. | - |
Last modified on