04 / In-game integration

The button lives inside the game.

LootID plugs into the publisher's own inventory UI. Eligible items get a verified badge; a single action turns the digital object into a registered physical collectible — without leaving the client.

Example publisher inventory UI showing the Emberfall Blade item marked eligible for LootID, with an Order Physical LootID action.
Example partner build · Not final artItem · LOOT-0001-EMB · Ashen Crown Studios
What the player sees

Four surfaces. All native to the game client.

01 · Eligibility badge

“Eligible for LootID”

Publisher-controlled flag on each asset. Only items you approve show the mark. Nothing else appears anywhere in the UI.

02 · Verified item

“Verified item · Ashen Chain”

Confirms the asset is a real, registry-linked instance — not a duplicate or exploit. Includes publisher, edition and item ID.

03 · Order physical LootID

One-tap physicalization

The action opens LootID's checkout flow inside a publisher-branded panel. Manufacturing, QC, encasement and shipping are handled by us.

04 · Learn how it works

Trust as a first-class link

A quiet secondary CTA that explains identity, provenance and transfer — for the collector who wants to understand before they commit.

The flow

From inventory slot to registered object.

  1. Step 01

    Item

    Player owns the eligible asset in-game.

  2. Step 02

    Order

    One-tap request from the inventory panel.

  3. Step 03

    Create

    LootID manufactures, encases, chip-verifies.

  4. Step 04

    Register

    Object enters the public LootID registry.

  5. Step 05

    Own

    Ship to the collector. Transferable, inheritable.

Publisher control

You decide what's eligible. Everything else stays hidden.

The badge, the CTA and the entire flow are gated by a single eligibility signal you own. Turn it on per asset, per edition, per region — or turn it off entirely at any time.

Integration modes
  • Native SDK
    Drop-in component for Unity / Unreal / Web clients.
  • Server API
    REST endpoints if you'd rather render the UI yourself.
  • Webhook fallback
    Trigger orders from your own storefront or launcher.

Native to your client · Invisible until eligible

Publisher benefit ↑