Stable card identity
One public Passport ID carries the TCG, publisher, card name, set, collector number, printing, variant, language, and catalog references.
Mint and authenticate a physical trading card once. Then let any TCG, tournament site, deck platform, or community app check that card through a free public API—without HaloVault running the match.
No game partnership is implied. Every platform chooses which cards, mint tiers, chains, and formats it accepts.
Example only. A token proves wallet control after a fresh signature challenge; it does not by itself prove legal ownership or present physical custody.
A Card Passport is not a new TCG, a deck builder, or a game server. It is an interoperable identity and verification record for one real card.
One public Passport ID carries the TCG, publisher, card name, set, collector number, printing, variant, language, and catalog references.
The API says whether the card was self documented or physically inspected by an authorized store—and exposes the underlying HaloCert.
An external ERC-721 or other token can bind to the Passport. The mint record still works when no token exists, and HaloVault never requires NFC for online use.
Any game can look up one Passport, resolve a HaloCert or chain asset, or batch-check a deck. Public reads need no API key and support browser CORS.
Every layer answers a different question. Games can require exactly the evidence their format needs.
The collector self-documents it or brings it to an authorized store for physical inspection and a Store-Verified mint.
Confirm the game namespace, set code, collector number, printing, language, and variant. A Passport ID is issued automatically with a card mint.
Mint through any compatible provider using the Passport manifest as token metadata, record the chain asset, and verify the binding after confirmation.
The game reads the free API, challenges the player's wallet when token control is required, and applies its own card and deck rules.
Enter a real HV-CARD-… Passport ID or HV-CERT-… certificate ID. The same API is available to every integration.
Public verification reveals only the public mint, card identity, token binding, and on-chain address facts—not private vault locations, costs, notes, or account data.
| Response area | What it reports | What the game should do |
|---|---|---|
passport | Active, disputed, revoked, or retired; metadata hash and commitment. | Reject anything that is not active under the game's policy. |
card | Cross-TCG identity fields and external catalog identifiers. | Map the printing to the game's own card database. |
mint | Certificate ID, record hash, issuance time, and current integrity verdict. | Require mint.valid=true. |
authentication | Minted vs. Store-Verified, physical inspection, issuer, claim, and limits. | Choose the minimum tier for the event or queue. |
onchain | Every recorded token and whether its manifest binding was verified. | Use a verified binding when token gating matters. |
token_control | Last chain-confirmed address, chain, verification state, and check time. | Issue a fresh nonce and verify the player's wallet signature. |
The proof framework is live, but each game must choose to integrate it and decide which printings and evidence levels it accepts. HaloVault cannot make a third-party game accept a card.
It proves token control only after a fresh wallet-signature challenge. A Store-Verified mint binds the physical card's inspected identity to its Passport; neither layer alone proves legal ownership or continuous custody.
No. The ordinary card mint keeps its existing certificate ID, snapshot, hash-chain record, evidence tier, and optional-NFC behavior. A Card Passport is an additional linked interoperability record. Existing card mints can be backfilled without reissuing or rewriting their HaloCerts, and non-card minting is untouched.
No. NFC is optional and primarily useful for in-person lookup, store handoff, and tamper-resistant physical tags. Online games use the Passport, public API, blockchain binding, and wallet challenge.
No. The player controls their wallet. HaloVault records the public chain reference and reads public chain state; it does not need a private key to verify token control.
The game or tournament operator. HaloVault proves identity and trust facts; it does not maintain every game's format, ban list, deck limit, rotation, or match rules.
The open read API is free and does not require an API key. Start with one lookup, add a wallet challenge only if your experience needs token control, and keep every gameplay rule in your own system.
Read the complete integration guide