Inttegro Engineering

About this SDK

Java builders, domain types and HTTP integration for services running on the JVM.

The Java SDK favors explicit builders and named domain values, giving service code a clear boundary around request construction and API failures.

Changelog

Recent releases.

01
10.0.0
2026-10-14
- 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.
02
9.0.0
2026-10-05
- Breaking: replaced the payout status invalid with failed.
- 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.
03
8.3.0
2026-10-03
- Added typed hosted Buy-page text overrides to Purchase Intent create, update, and response models, including explicit default restoration through the wire-shaped update overload.
04
8.2.0
2026-10-01
- Added typed fixed and customer-selected catalog price definitions, suggested contribution amounts, and order line items that couple a catalog price with the amount selected by the customer.
05
8.1.0
2026-09-27
- Added the required application-scoped customer fingerprint to typed customer responses for possible duplicate-record detection.

Shared guarantees

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

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

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

04 / Read, inspect, contribute