Skip to main content

Production Update 1.2.9

Environment:Production
Released:4 October 2026 at 22:34 UTC+7
Version:1.2.9
Status:Released
Deployment window:04 Oct 17:43 – 22:34
Verification:Pending Verification

Summary

A shop can be opened on more than one address. Admin registers each base domain, and each base keeps its own Cloudflare zone, token, and Pages project. The shop keeps one label, and that label is created on every active base. Players who register on any of those addresses join that shop. Emails and the poster use the address the shop marks as the main URL.

Added

  • Shop base domains sits at the top of Admin → Domain Management → Domains. System Admin and Super Admin can add a base, turn it off, turn it back on, or remove it from the list.Module: Domains · Portal: Admin
  • On Shop → Settings → Kiosk URL, the shop chooses which address is the main URL. Credential emails and the promo poster use that address.Module: Kiosk URL · Portal: Shop
  • Each shop base domain stores its own Cloudflare zone, API token, Pages account, Pages project, and CNAME target. Saving those fields writes that shop's addresses into that base's Cloudflare account. The token is saved and is not shown again.Module: Domains · Portal: Admin

Changed

  • One subdomain label is created on every active base. A player who registers on any of those addresses joins that shop. The other addresses stay open after the shop picks a main URL.Module: Kiosk URL · Portal: Shop, Player
  • Saving a new label renames every address for that shop. The main URL stays on the same base. Old bookmarks stop working once the new name has propagated.Module: Kiosk URL · Portal: Shop
  • The game list on one of a shop's addresses is copied onto that shop's other addresses. Editing the list on one address updates the others.Module: Game list · Portal: Admin, Player

Affected Modules

  • Domains
  • Cloudflare
  • Kiosk URL
  • Player registration
  • Player credentials
  • Shop poster
  • Game list

Affected Portals

  • Admin Portal
  • Shop Portal
  • Player Portal
Last updated on 5 October 2026 at 01:51 UTC+7 by Product Team

A shop used to have one kiosk address. The ending of that address was fixed by the platform, and the shop typed only the part before the first dot. Emails and the poster used that same address.

This build keeps one label per shop, and puts that label on every base Admin has turned on. Players can register on any of the resulting addresses and still join that shop. Emails and the poster follow the one address the shop marks as Main URL. Each base keeps its own Cloudflare account, so a shop address is written only into the zone of the base it belongs to.

Who: System Admin and Super Admin, on Admin → Domain Management. A Shop, on Settings → Kiosk URL. Finance Admin, Operation Admin, Platform Admin, and Support Admin do not have Domain Management. Opening that page says you don't have permission to manage domains.


Shop base domains (Admin)​

Where: Admin → Domain Management → the Domains tab. The new card is Shop base domains, above the existing domain list.

What it is for: Each row is a suffix, such as vaultplay.co. A shop label mystore then exists as mystore.vaultplay.co on every base that is Active. The card says a shop subdomain is created on every active base, each base domain keeps its own Cloudflare zone, token, and Pages project, and the API token is saved and is not shown again.

Add a base​

  1. Type the base. The field placeholder is vaultplay.co. You can paste a full address. https://, a path, and a port are stripped. What is saved is the host, in lowercase.
  2. Fill the Cloudflare fields for that base. The placeholders are Zone ID, API token, Pages account ID, Pages project name, and CNAME target. The token field hides what you type.
  3. Press Add base domain. The button stays off while the base field is empty, and while a save is in progress. The Cloudflare fields can be left blank and filled in later.
  4. The new base is Active. Every shop that already has a label receives that label on this base. When Zone ID, API token, and CNAME target are filled in, a DNS name is created for each of those addresses, in that base's zone. When Pages account ID, Pages project name, and the API token are filled in, each address is attached to that Pages project.
  5. The base field and the Cloudflare fields clear. The base appears in the list. The token is not shown again.

If some shops cannot receive the new address, the base is still saved. The page says Saved, but N shop hostname(s) could not be created. The count is how many shops were skipped. A shop whose new address is already owned by another shop is skipped. The other shops still get theirs. An address that exists and is not assigned to any shop is given to the shop with that label, and that shop's game list is copied onto it.

The list​

Each row shows the base, Active or Inactive, and two buttons. Under that, the same Cloudflare fields are shown again, with Save. An empty list says No base domains yet.

ButtonWhat it does
DeactivateThe base stays in the list and reads Inactive. New labels are not created on it. Addresses already created stay in place, and players can still open them.
ActivateThe base reads Active again. Shops that are missing this address get it now. Addresses already on this base are written into this base's Cloudflare account when the fields below are filled in.
SaveStores Zone ID, Pages account ID, Pages project name, and CNAME target for this base, then writes the shop addresses already on this base into that Cloudflare account.
RemoveAsks Remove base domain and then the name. The question says existing shop hostnames stay in place. Confirming takes the base off this list. It does not delete addresses shops already have, and it does not delete their DNS names.

Cloudflare for that base​

vaultplay.co and kioskservice.club are separate Cloudflare accounts. A shop address is created only in the account of the base it ends with. It is not created in the other base's zone.

FieldWhat it is for
Zone IDThe Cloudflare zone this base's shop addresses are written into.
API tokenThe token for that zone and that Pages project. After it is saved, the field is empty and the placeholder reads Token saved. Leave it blank and press Save to keep the token already stored. Type a new token to replace it.
Pages account IDThe Cloudflare account that owns the Pages project.
Pages project nameThe Pages project the shop address is attached to.
CNAME targetWhere the DNS name points, such as the Pages hostname for that project.

A shop address still exists on the platform when these fields are empty. DNS and Pages are skipped until Zone ID, API token, and CNAME target are saved, and until Pages account ID and Pages project name are saved for the Pages attachment. Press Save after filling them in. Shops that already have a label on this base get those DNS names then.

What is accepted​

RuleWhat you see
ShapeA base such as vaultplay.co. A single word, a blank value, or a name with * is refused: “Enter a base domain such as vaultplay.co.”
CharactersLetters, digits, dots, and hyphens. Anything else, a base longer than 253 characters, or a double dot is refused: “Base domain contains invalid characters.”
Already in the list“This base domain is already registered.”
MessageWhat to do
Failed to load base domainsReload the page.
Could not add base domainRead the message on the card. If it names the rule above, fix the value and add again.
Saved, but N shop hostname(s) could not be created.The base is on. Open the shop list for a shop that did not get the new address, or pick a label that is free on that base.
Could not update base domainPress Deactivate or Activate again.
Could not save Cloudflare settingsPress Save again. A blank token field does not clear a token that is already saved.
Could not remove base domainPress Remove again.

Kiosk URL (Shop)​

Where: Shop → Settings → Kiosk URL.

What changed: The page used to preview one address, with one fixed ending. It now previews one address per active base, from the same label. After the URL exists, Main URL chooses which address goes on credential emails and the promo poster.

If no base is registered, the page says No shop base domain is registered yet. Ask an admin to add one. There is nothing to type until Admin adds a base.

Create the label​

The heading is Kiosk URL. The introduction says one label is created on every shop base domain, players who register on any of those URLs belong to this shop, and one hostname is the main URL for credential emails and posters.

Preview lists https:// and then the label, a dot, and each active base. While the field is empty, each line starts with …..

  1. Under Subdomain label, type the label. The placeholder is e.g. mystore.
  2. The note under the field says lowercase letters, numbers, and hyphens between segments, and that one label is used on every base domain.
  3. Press Create kiosk URL. While it saves, the button reads Creating….
  4. The success message is Kiosk URL created.

The button stays off until the field has something in it.

A shop that already has a URL cannot create a second label. Changing the name is Edit, below.

Choose the main URL​

After the URL exists, Main URL lists every address this shop has, each with https:// in front. The note says credential emails and the shop poster use this hostname.

Select the address. The success message is Main URL updated. Emails and posters will use it.

That choice does not close the other addresses. A player who opens any of them and registers still joins this shop.

The promo poster on this page, and the login link in a player's credential email or text, use the selected address. Switch the main URL before you download a new poster or send credentials, if those should show a different address.

Change the label​

Press Edit.

  1. Change subdomain shows the current label.
  2. A note says changing the URL may break old bookmarks until DNS updates propagate.
  3. Cancel puts the old label back and leaves edit mode. Nothing is saved.
  4. Save new label renames the label on every active base. While it saves, the button reads Saving…. The success message is Kiosk URL updated.

The address that was the main URL stays the main URL, on the same base, under the new label. Example: if mystore.vaultplay.co was main, saving mystore2 makes mystore2.vaultplay.co the main URL. The old names are replaced. They are not kept as extra addresses.

What the label may be​

RuleWhat you see
Only the labelDo not type the full address. A value with a dot is refused: “Enter only the subdomain label, not the full hostname.”
Length1 to 63 characters. “Subdomain must be 1–63 characters.”
CharactersLowercase letters, digits, and a single hyphen between segments. “Subdomain may only use lowercase letters, digits, and single hyphens between segments.” The page lowercases what you type in the preview.
Taken“This subdomain is already in use”, and the address that is taken when one base is the problem.
Reserved“This subdomain is reserved.” Reserved labels are www, api, admin, mail, ftp, localhost, cdn, static, assets, app, dashboard, shop, agent, cashier, client, play, super-agent, telegram-client, and dev-admin.
MessageWhat to do
Could not load kiosk URLReload the page.
Could not createRead the rule in the message and try another label.
Could not updateThe old addresses are unchanged. Fix the label and press Save new label again.
Could not set the main URLSelect the address again.
This shop already has a kiosk domainUse Edit. Do not create a second label.
No kiosk domain to updateCreate the URL first.

Shops that already had a URL​

Nothing has to be retyped.

When this update is applied, each suffix already used by a shop address is registered under Shop base domains, and it is Active. The same label is then created on every one of those bases. A shop whose address cannot be read as a label plus a base is left as it was.

A base that was already in the list starts with the Cloudflare fields empty. Open that row, fill Zone ID, API token, Pages account ID, Pages project name, and CNAME target, then press Save. Shop addresses already on that base are written into that base's Cloudflare account. Until those fields are saved, this card does not create a DNS name for them.

The address the shop already had stays the Main URL. Emails and posters keep using it until someone on that shop selects a different address.

A shop that had no kiosk URL is unchanged until someone opens Kiosk URL and presses Create kiosk URL.


Games on those addresses​

Each address can carry a game list. A new address for a shop starts with the same games as that shop's other address.

On Admin → Domain Management, changing the game list on one of a shop's addresses writes that same list onto the shop's other addresses. Players on any of the shop's addresses then see the same games.

A player who registers on any of the shop's addresses joins that shop. Picking a Main URL does not change that.