Inttegro demos 1.2.3

Inttegro demos 1.2.3

This patch release gives every order-producing demo a proper merchant order
number and restores a clean Spring Boot build.

Changes

• Sends story-specific, human-readable order numbers from every hosted web
  backend and from the shared Next.js mobile backend.
• Keeps each demo order number stable across an idempotent retry by deriving it
  from the validated logical checkout attempt.
• Uses KORA-… for Kora Market, AFTERGLOW-… for Afterglow Sessions, and
  INV-2048-… for Ledgerline instead of allowing the generated Inttegro or_…
  identifier to become the order number.
• Documents the boundary between merchant order numbers, idempotency keys,
  invoice numbers, Inttegro order IDs, and proof of payment for both people and
  machine readers.
• Fixes a shadowed lambda parameter that prevented the Spring Boot demo from
  compiling with the released Java SDK.
• Advances immutable suite, per-demo, and deployment references to version
  1.2.3. Version 1.2.2 remains unchanged for existing permalinks.

Verification

The Next.js and Nuxt demos passed type checking, tests, and production builds.
Express, Django, FastAPI, Go, Rails, Laravel, and Spring Boot passed their
framework-specific test suites using the exact SDK versions declared by each
demo. The repository-wide demo contract check also passed.

The live checkout verification creates a finalized order and confirms that the
returned order carries the expected merchant number. Verification stops before
payment authorization; no real payment is made.

Release safety

Order numbers contain only story prefixes and opaque checkout-attempt data.
They contain no customer names, email addresses, phone numbers, credentials,
or payment details. The dedicated API key remains in deployment secret stores
and is not included in source, artifacts, tags, or browser/mobile bundles.

Inttegro demos 1.2.2

Inttegro demos 1.2.2

This patch release completes the first-party live demo set and fixes the two
runtime compatibility issues found while exercising the container deployments.

Changes

• Publishes stable inttegro.dev live URLs for Django, FastAPI, Go, Rails, and
  Laravel, backed by isolated Railway services and a narrow Cloudflare edge
  router.
• Makes Django honor the trusted HTTPS proxy boundary so production form posts
  pass CSRF validation without weakening host or origin checks.
• Updates the Go demo to Inttegro SDK 4.4.1 for canonical Product decoding,
  active-price validation, and optional billing details.
• Separates verified first-party hosting from reader-owned provider templates in
  deployment metadata. A live Railway service does not imply that a public
  Railway template has been published.
• Advances every immutable suite tag, per-demo tag, deployment ref, Studio
  source permalink, and reader-owned deploy button to version 1.2.2.

Production verification

The five container-hosted demos returned healthy responses through their public
Cloudflare origins. Their configured Product and Price pairs were resolved on
the trusted server, and their checkout routes were exercised through the
Inttegro-hosted invoice handoff.

Verification stopped before payment authorization. No real payment was made.

Release safety

The dedicated API key remains only in Railway's encrypted service variables. No
credential is embedded in source, Worker configuration, build output, release
metadata, deployment refs, browser assets, or mobile bundles. Version 1.2.1
remains immutable and continues to resolve for existing Studio permalinks.

Inttegro demos 1.2.1

Inttegro demos 1.2.1

This patch release makes the production Cloudflare deployments match the
portable server configuration contract documented by the Next.js and Express
demos.

Changes

• Explicitly maps Cloudflare Worker text and secret bindings into
  process.env for the Next.js and Express runtimes.
• Adds a repository check that prevents either Worker configuration from
  dropping the required compatibility flag.
• Records the Next.js, Nuxt, and Express Cloudflare deployments as verified
  after exercising their production checkout routes.
• Advances every immutable suite tag, per-demo tag, deployment ref, Studio
  source permalink, and reader-owned deploy button to version 1.2.1.

Production verification

The three Cloudflare-hosted web demos each resolved their configured Inttegro
Product and Price, created a production Order, and redirected to an
Inttegro-hosted invoice. The shared Next.js mobile endpoint also created a
finalized production Order for the dedicated demo Customer.

Verification stopped before payment authorization. No real payment was made.

Release safety

The dedicated API key remains only in Cloudflare's encrypted secret bindings.
No credential is embedded in source, build output, release metadata,
deployment refs, browser assets, or mobile bundles. Version 1.2.0 remains
immutable and continues to resolve for existing Studio permalinks.

Inttegro demos 1.2.0

Inttegro demos 1.2.0

This minor release makes the V1 suite catalog-backed and prepares the public
Cloudflare demos for real end-to-end Inttegro checkout.

Changes

• Resolves a configured Inttegro Product and Price on the trusted server in all
  nine hosted-web frameworks before creating an Order.
• Keeps product identity, price identity, currency, and amount out of untrusted
  browser and mobile requests.
• Validates product publication and the configured product-price relationship,
  then snapshots the authoritative catalog fields into the Order for consistent
  behavior across current SDK releases.
• Documents the direct product_id + price_id alternative for SDKs whose typed
  order model exposes that catalog-reference shape.
• Adds Product and Price environment requirements to local examples, Cloudflare
  deploy-button bindings, Vercel buttons, Render Blueprints, the deployment
  matrix, and the generated demo catalogue.
• Improves missing-configuration guidance so a reader can identify every value
  required for a working checkout.

Production demo resources

The Inttegro-hosted deployments use three dedicated GHS 50.00 products aligned
with the suite's stories: the Kora Market Dawn Brew Set, Afterglow Sessions
Courtyard Admission, and the August Studio Retainer for Ledgerline. The Next.js
companion backend also uses a dedicated demo Customer for the four mobile SDK
examples. One dedicated server-side API key can be rotated without changing the
public source or reader-owned deployment templates.

The public web demos create production Orders and stop at Inttegro-hosted
payment selection during release verification. Verification does not authorize
a real payment.

Release safety

No API key or customer data is embedded in source, release metadata, deployment
branches, browser assets, or mobile bundles. Product and Price IDs are
non-secret deployment configuration, but checkout endpoints never accept them
from the public request. Published suite tags, per-demo tags, and deployment
refs remain immutable.

Inttegro demos 1.1.3

Inttegro demos 1.1.3

This patch release supersedes 1.1.2 without moving or replacing any published
tag. It aligns the public catalogue with the now-published release and makes
prepared provider configurations directly launchable by readers.

Changes

• Labels the active suite as a published release rather than a release
  candidate.
• Enables deployment links for both prepared and verified provider targets
  while keeping blocked and template-pending targets unavailable.
• Adds contract assertions for both catalogue behaviors.
• Retains the live-tested Nuxt Cloudflare compatibility fix from 1.1.2.

Release safety

Prepared means that the provider configuration is checked in and launchable;
it does not claim that a checkout using reader-owned credentials has passed the
full verification gate. Deploy flows request the reader's own Inttegro test
key, and no credential or provider secret is embedded in source or release
metadata.

Inttegro demos 1.1.2

Inttegro demos 1.1.2

This patch release supersedes 1.1.1 without moving or replacing any published
tag. It carries the Cloudflare compatibility setting proven during the live
Nuxt deployment.

Changes

• Keeps Nitro's generated Node shims isolated from Cloudflare's default Node
  compatibility layer, preventing a node:buffer startup validation failure.
• Adds a contract assertion so the verified Nuxt Worker compatibility flags
  cannot regress silently.
• Retains the catalogue, active inttegro.dev host plan, portable provider
  targets, setup guidance, and signed immutable deployment-ref workflow from
  1.1.1.

Release safety

Deploy buttons request the reader's own Inttegro test key. No credential or
provider secret is embedded in source, query parameters, generated catalogue
metadata, or release files. Reader manifests remain host-neutral;
Inttegro-owned custom hosts are attached only during release deployment.

Inttegro demos 1.1.1

Inttegro demos 1.1.1

This patch release supersedes 1.1.0 without moving or replacing its signed
tags. It corrects deployment-ref preparation and completes the reader-owned
deployment experience introduced in 1.1.0.

Highlights

• Fixes silent Git command handling in the signed deployment-ref preflight.
• Publishes a polished catalogue for the demos.inttegro.dev home.
• Adds release-aware deployment metadata and active
  {framework}-demo.inttegro.dev hostnames while keeping reader manifests
  host-neutral.
• Prepares Cloudflare Workers deployments for Next.js, Nuxt, and Express.
• Prepares framework-native Vercel deployments for Next.js and Nuxt.
• Adds container, Render Blueprint, and Railway configuration for Express,
  Django, FastAPI, Rails, Laravel, Go, and Spring Boot.
• Documents provider trade-offs, environment contracts, verification gates,
  and immutable generated deployment refs for humans and machine readers.
• Records the current Python Workers transport incompatibility and Java SDK
  publication gate rather than presenting non-working deploy buttons.

Release safety

Deploy buttons request the reader's own Inttegro test key. No credential or
provider secret is embedded in source, query parameters, generated catalogue
metadata, or release files. Render examples disable automatic upstream deploys;
generated deployment refs are versioned and immutable.

The inttegro.dev domain is active on Cloudflare. Inttegro-owned custom hosts
are attached during release deployment and are deliberately absent from the
configurations cloned by readers.

Inttegro demos 1.1.0

[!IMPORTANT]

This release is preserved for permalink integrity and is superseded by v1.1.1, which fixes deployment-ref preparation.

Inttegro demos 1.1.0

This release turns the demo suite into a reader-owned deployment experience.

Highlights

• Publishes a polished catalogue for the demos.inttegro.dev home.
• Adds release-aware deployment metadata and active
  {framework}-demo.inttegro.dev hostnames while keeping reader manifests
  host-neutral.
• Prepares Cloudflare Workers deployments for Next.js, Nuxt, and Express.
• Prepares framework-native Vercel deployments for Next.js and Nuxt.
• Adds container, Render Blueprint, and Railway configuration for Express,
  Django, FastAPI, Rails, Laravel, Go, and Spring Boot.
• Documents provider trade-offs, environment contracts, verification gates,
  and immutable generated deployment refs for humans and machine readers.
• Records the current Python Workers transport incompatibility and Java SDK
  publication gate rather than presenting non-working deploy buttons.

Release safety

Deploy buttons request the reader's own Inttegro test key. No credential or
provider secret is embedded in source, query parameters, generated catalogue
metadata, or release files. Render examples disable automatic upstream deploys;
generated deployment refs are versioned and immutable.

The inttegro.dev domain is active on Cloudflare. Inttegro-owned custom hosts
are attached during release deployment and are deliberately absent from the
configurations cloned by readers.

Inttegro demos 1.0.0

Inttegro demos 1.0.0

This is the first versioned release of the complete Inttegro demo suite. It
provides production-shaped payment integrations, realistic product stories,
framework-native structure, and stable source references for Inttegro Studio.

Included demos

• Next.js, Nuxt, Rails, and Laravel: Kora Market hosted checkout.
• Express, Django, and FastAPI: Afterglow Sessions ticket checkout.
• Go and Spring Boot: Ledgerline invoice payment.
• SwiftUI, Jetpack Compose, Flutter, and React Native with Expo: Kora Market
  native payment sheet.

Every demo is versioned 1.0.0. The canonical suite tag is v1.0.0; each demo
also has an immutable {demo}-v1.0.0 alias for framework-specific Studio
permalinks. All 14 tags resolve to the same release commit.

Integration guidance

The release includes extensive source commentary and a shared decision guide
covering hosted checkout, mobile backend boundaries, secret handling,
idempotency, customer and catalog alternatives, finalization, return URLs,
correlation, verification, reconciliation, safe errors, and observability.

integration-decisions.json provides the same
rationale in a structured form for machine readers.
releases/v1.0.0.json maps each demo to its immutable tag and
integration entry points.

Verification

The repository contract suite, Next.js, Nuxt, Express, Django, FastAPI, Rails,
Go, React Native, and the SwiftUI simulator build passed for this source state.
Android requires a configured Android SDK. Flutter/Dart, Maven, and PHP/Composer
checks require their respective toolchains.

Spring Boot currently resolves the Java SDK from the parent Commerce checkout
until Java SDK 5.0.0 is available from Maven Central. Flutter and React Native
also require their documented native development-build setup.