One API surface
The SDK follows the same public Inttegro contract as every official server client. Language choice does not change platform capability.
Swift SDK
Server-side Swift for macOS and Linux.
01
About this SDK
An asynchronous server-side Swift package, separate from the native iOS Checkout SDK and safe for secret-key use.
The SwiftPM package brings async resource operations to trusted macOS and Linux services; iOS applications should use the separate native Checkout SDK instead.
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.
- Added payment receipt data separately from invoice data.
- Breaking: replaced the legacy flat payout minimum with typed
- 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.
- Added the required application-scoped customer fingerprint to typed customer responses for possible duplicate-record detection.
- Breaking: replaced payout
balanceTransactionsID strings with typed contribution values containing the source transaction's original amount and the exact amount allocated to the payout. - Added complete payment balance-transaction allocation history together with available, pending, and spent amount partitions.
- Breaking: replaced payout
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.