Skip to main content
The Hellgate Cloud Web SDK Demo is a hosted front-end that drives the Web SDK flows end to end. Paste a session_id from your server, submit a card, and confirm the resulting token — all without building a browser integration first. Reach for it when you want to verify a session from your backend before wiring up the SDK in your own application. The workbench covers four flows, exposed as tabs at the top of the page: Card Tokenization, CVC2 Refresh, Card Elements, and 3DS. This page walks through the default Card Tokenization flow; the other tabs consume the same session and backend configuration.

​
Prerequisites

A session_id from your backend — see the Guardian and Commerce v2 examples on the right. 
curl --request POST \
  --url https://<your-cluster>.on-hellgate.cloud/api/pci/tokens \
  --header 'content-type: application/json' \
  --header 'x-api-key: hlg-sbx-...' \
  --data '{ "source": "session" }'

{
  "id": "a9f4e2c0-12d0-4b73-8e8c-0f0f0f0f0f0f",
  "session_id": "7f2c9460-7e2e-403f-a08a-bc58cdcaea83",
  "status": "pending"
}

​
Steps

1

Open the workbench

Visit https://demo.hellgate.dev/card. The page loads the same Web SDK you would embed in your own application.
2

Set the Backend Service URL

Use the Backend Service URL dropdown at the top of the page to match the environment that issued your session.There are built-in options (e.g. Sandbox (Shared Commerce v2)), which target the Test tier of the shared Hellgate Commerce v2 platform.For any other deployment — a dedicated Commerce v2 cluster or a Guardian cluster — enable the Custom URL toggle and enter the base URL of your backend (for example https://<your-cluster>.on-hellgate.cloud).
3

Paste the Session ID

Paste the session_id into the Session ID field.
4

(Optional) Adjust form options

The remaining controls change how the SDK renders the card form. Leave them at their defaults unless you want to preview a specific layout:
  • Schemes — restrict the accepted card networks.
  • Card Layout — render the card fields as Single-line or Multi-line.
  • Expiration Fields — Combined month/year field or Separate fields.
5

Submit the card

Click Test Card, fill in the card details in the rendered form, and submit.
6

Inspect the result

On success the workbench shows the resulting token. Confirm the same record through your own integration — for example by fetching it through the relevant product’s API or viewing it in the Hellgate dashboard.

​
Next steps

Once the workbench flow succeeds, port the same session-plus-SDK pattern into your own application: