Changelog & versioning

Versioning policy

The SDK follows SemVer: MAJOR.MINOR.PATCH, with the version decided from Conventional Commits at release time and published to pub.dev.

• MAJOR — a breaking change (feat!: or a BREAKING CHANGE: footer). A breaking change goes straight to 1.0.0, even while the version is below 1.0.
• MINOR — a new feature (feat:).
• PATCH — a fix (fix:).

Documentation, chore, test and refactor commits do not trigger a release. The SDK makes no SUQO API calls of its own, so unlike the server-side SDKs its version is not tied to the API's path version.

Compatibility table

The full history is in CHANGELOG.md in the SDK repository.

0.1.1 - 2026-11-04

Release on GitHub · Compare on GitHub.

Changes

• Relicensed from Apache-2.0 to MIT. No API or behaviour changes.

0.1.0 - 2026-10-12

The first published version, as suqo_checkout.

Features

• SuqoCheckout.open(context, sessionId: …) pushes the full-screen checkout and completes with exactly one SuqoOutcome: SuqoSuccess, SuqoFailure or SuqoClosed. There is no provider to mount and no callbacks to wire; the awaited outcome is the result.
• SuqoProvider, optional and configuration only: app-wide defaults for mode, baseUrl, checkoutPath, title, loadingLabel, debug and onEvent, each overridable per call.
• SuqoMode.sandbox (the default) and SuqoMode.live, resolving to test.suqo.ai and app.suqo.ai, with baseUrl overriding both.
• Bank and wallet deeplinks (fonepayApp://, Android intent://) are handed to the OS; javascript:, data:, file: and blob: navigations are refused.
• Two load deadlines — 12s to the page's first signal, 25s to the block mounting — with a retry, so a page that never boots shows a loading failure rather than hanging.
• onEvent, a debug stream, and debug logging that redacts session ids, URLs and gateway params.

Requires

• Flutter >=3.3.0, Dart >=2.18.0.
• A checkout session created through the API, with a customer assigned, and its id passed to open.