Go SDK

Explicit resource clients for concurrent Go services.

Context-aware resource packages, Go-native domain types and direct control over concurrency and transport behavior.

Resource packages keep domain names short and focused, while context-aware operations and configurable transports fit naturally into long-running Go services.

Recent releases.

Read the complete changelog
  1. 01

    12.0.0

    • Breaking: changed the module and import path to github.com/inttegro/inttegro-sdk-go/v12.
    • Breaking: replaced the legacy flat payout minimum with typed Limits.Amount.Min and Limits.Amount.Max values.
    • 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.
  2. 02

    11.0.1

    • Corrected release verification and provenance metadata for the new github.com/inttegro/inttegro-sdk-go/v11 module path.
  3. 03

    11.0.0

    • Breaking: replaced the payout status invalid with failed.
    • Breaking: changed the module and import path to github.com/inttegro/inttegro-sdk-go/v11.
    • 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.
  4. 04

    10.4.0

    • Added typed hosted Buy-page text overrides to Purchase Intent create, update, and response models, including explicit default restoration.
  5. 05

    10.3.1

    • Restored the SDK's broad Inttegro API positioning while keeping the concrete checkout examples in the integration guide.
01

One API surface

The SDK follows the same public Inttegro contract as every official server client. Language choice does not change platform capability.

02

Explicit operations

Typed domain values, idempotent mutations and structured failures keep uncertain commerce outcomes visible to application code.

03

Application-owned telemetry

Operational hooks integrate with the application's observability stack without exporting credentials, request bodies or resource identifiers.

04 / Read, inspect, contribute

Use the SDK.