One API surface
The SDK follows the same public Inttegro contract as every official server client. Language choice does not change platform capability.
Dart SDK
A server-side Dart client, independent of Flutter.
01
About this SDK
A standalone server client with typed resource libraries; it does not depend on Flutter or expose a payment sheet.
Use it in trusted Dart VM services. Resource libraries provide the namespace boundary, while the Flutter SDK remains a separate customer-facing Checkout product.
02
Changelog
Recent releases.
Read the complete changelog- Breaking: replaced the legacy flat payout minimum with typed
limits.amount.minandlimits.amount.maxvalues. - Breaking: reshaped application placement relationships around a typed parent identity.
- Added typed payment and payout capability lookup for the authenticated app.
- Breaking: replaced the legacy flat payout minimum with typed
- Breaking: moved contract models into public resource libraries such as
package:inttegro/payment.dartandpackage:inttegro/financial_account.dart, with concise resource-scoped type names such aspayment.Statusandfinancial_account.CreateRequest. - Moved model sources from the internal
generatednamespace into first-class, concise resource paths underlib/src; serialization and runtime behavior are unchanged.
- Breaking: moved contract models into public resource libraries such as
- Added typed payment receipt and hosted receipt-format models separately from order invoices.
- Split generated models into resource modules with one top-level type per file. This changes source organization without changing runtime behavior.
- Breaking: replaced the payout status
invalidwithfailed. - Added typed payout failure details with a stable reason, caller-safe detail, retry guidance, and a separate lifecycle timestamp.
- Added the application-scoped financial-account fingerprint to typed responses.
- Breaking: replaced the payout status
- Added typed hosted Buy-page text overrides to Purchase Intent create, update, and response models, including explicit default restoration.
03
Shared guarantees
Explicit operations
Typed domain values, idempotent mutations and structured failures keep uncertain commerce outcomes visible to application code.
Application-owned telemetry
Operational hooks integrate with the application's observability stack without exporting credentials, request bodies or resource identifiers.