Skip to content

Inttegro demos 1.2.0

Choose a tag to compare

View all tags
@yaw-zebo yaw-zebo released this 06 Sep 14:46
· 5 commits to main since this release
Immutable release. Only release title and notes can be modified.
v1.2.0
This tag was signed with the committer’s verified signature.
yaw-zebo Yaw Boakye at Zebo
GPG key ID: 9F839226255443B5
Verified
Learn about vigilant mode.
b818dcc
This commit was signed with the committer’s verified signature.
yaw-zebo Yaw Boakye at Zebo
GPG key ID: 9F839226255443B5
Verified
Learn about vigilant mode.

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.

Assets 3
Loading