> ## Documentation Index
> Fetch the complete documentation index at: https://developer.hellgate.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloud Platform Updates

> New releases and improvements of the Cloud Platform.

<Update label="August 3, 2026" tags={["Improvement"]}>
  ## Hellgate Web SDK (v3.11.0)

  ### Central Control Over Card Saving

  Decide once, when you create a session, whether cards are saved — always,
  never, or left to the cardholder — and the SDK enforces that policy at
  checkout. Your card-retention rules stay consistent across every page that
  embeds the SDK, with nothing extra to implement in each frontend. The SDK
  also tells you which policy is active, so you can show a "Save my card"
  checkbox only when the cardholder really has the choice.

  ### Improvements and bugfixes

  * A cardholder's decision not to save their card is now always honored.
    Previously, in some integrations, declining to save a card could still
    result in a saved card.
</Update>

<Update label="July 14, 2026" tags={["New Release"]}>
  ## Link documentation now public

  [Link](/products/link/overview) — the protocol-abstraction runtime of the
  Composable Payment Architecture — now has public documentation. Link is the
  platform's PSP and provider connectivity layer: define a versioned API
  contract (a **protocol**) once and bind it to any provider through
  declarative **backends**, so integration becomes configuration, not code. It
  is the component [Commerce](/products/commerce/v2/overview) routes through to
  reach acquirers and PSPs, and that [Specter](/products/specter/overview)
  reaches through to call external risk engines.

  Explore the [overview](/products/link/overview),
  [core concepts](/products/link/concepts/protocols), and the
  [API reference](/products/link/api-reference/getting-started).
</Update>

<Update label="May 21, 2026" tags={["New Release", "Improvement"]}>
  ## Hellgate Web SDK (v3.10.0)

  ### Cardholder-Aware Token Lifecycles

  Align token retention with what your cardholder actually agreed to. A new optional
  `ephemeral?: boolean` argument on `process()` and `tokenize()` defaults to `true`,
  meaning the cardholder is *not* remembered. Flip it to `false` only on explicit
  consent — for example, when a customer ticks a "Save my card" box at checkout.

  ### Smarter Scheme Validation

  Allowed card schemes configured on the session now flow through to client-side
  card number validation. Cardholders see scheme errors immediately, before the
  request ever leaves the browser.

  ### Improvements and bugfixes

  * Empty `card_schemes` configuration now correctly allows all schemes.
  * Separate expiry month/year inputs now treat `'1'` as a valid month and
    properly reject past-expiry dates.
  * Demo: a new "Save my card" checkbox in the tokenization demo wires straight
    into the new ephemeral toggle so you can try it end-to-end.
</Update>

<Update label="March 5, 2026" tags={["Improvement"]}>
  ## Hellgate Web SDK (v3.9.1)

  Security improvements.
</Update>

<Update label="November 8, 2025" tags={["New Release"]}>
  ## Hellgate Web SDK (v3.9.0)

  Added support to split the expiriy input fields in the Web SDK.
</Update>

<Update label="October 6, 2025" tags={["Maintenance"]}>
  ## Hellgate Web SDK (v3.8.1)

  September cleanup and maintenance release for our SDKs.
</Update>

<Update label="August 8, 2025" tags={["Improvement"]}>
  ## Hellgate Web SDK (v3.8.0)

  Validate CVC length based on card scheme in multi-line forms.
</Update>

<Update label="June 5, 2025" tags={["New Release", "Improvement"]}>
  ## Hellgate Android SDK (v1.1.0)

  The Android SDK now encrypts the full payload — including any additional data —
  into a single JWE and returns it to your app, instead of calling the tokenization
  backend directly. This simplifies your integration and keeps sensitive data
  encrypted end to end.

  ### Improvements and bugfixes

  * Additional cardholder data is now encrypted as part of the JWE token.
  * Hellgate error responses now surface with clearer, more actionable detail.
  * Removed support for tokenizing through an external token provider.
  * Updated environment URLs.
</Update>

<Update label="May 7, 2025" tags={["Improvement"]}>
  ## Hellgate Web SDK (v3.7.0)

  Add 'onSessionComplete' handler to Hellgate® client with result data.
</Update>

<Update label="April 8, 2025" tags={["Improvement"]}>
  ## Hellgate Web SDK (v3.5.3)

  Improved the SDK with small but important fixes:

  * Fix masked input behaviour
  * Reject cardHandler.process() promise if BE responds 40x / 50x status code
  * Await cardHandler.process() throws exceptions if card date is not complete or invalid
  * Show full CVC code up to 4 digits
  * Card scheme validation by default
  * UnionPay card number input

  Added some new features:

  * Encrypt additional\_data payload on tokenize
  * User can refresh CVC2 code of a token from WebSDK
</Update>

<Update label="May 17, 2024" tags={["New Release"]}>
  ## Hellgate iOS SDK (v1.0.0)

  The first release of the Hellgate® iOS SDK brings cardholder data tokenization
  to native iOS apps. Collect and tokenize the card number, CVC, and expiration
  date, and attach additional fields to capture cardholder information — so raw
  card data never touches your own backend.
</Update>

<Update label="April 12, 2024" tags={["New Release"]}>
  ## Hellgate Android SDK (v1.0.0)

  The first release of the Hellgate® Android SDK brings cardholder data
  tokenization to native Android apps.
</Update>