Skip to main content

​
What It Does

The MintID Resolver provides a permanent, public URL for every product identifier. When a barcode is scanned or a link is followed, the resolver maps the identifier to the correct product — even if the identifier has since been retired.

​
Who It’s For

Supply chain participants, consumers scanning product codes, and systems integrating with GS1 Digital Link standards.

​
How It Works

​
Permanent Brand Domain

Every brand on MintID is assigned a permanent resolver subdomain: 
<brand-subdomain>.mintid.ai
This is the canonical domain for all public scan paths. It does not change, even if the brand’s display name is updated. The resolver supports the GS1 Digital Link URI structure: 
https://<brand>.mintid.ai/01/<GTIN>
Optional path segments are also supported:
  • /10/<batch> — batch/lot number
  • /21/<serial> — serial number
Example: 
https://acme.mintid.ai/01/05060012345678
https://acme.mintid.ai/01/05060012345678/10/LOT-A/21/001

​
Resolution Strategy

The resolver uses a deterministic fallback strategy:
  1. Active identifier first — if the GTIN is currently active on a product, it resolves immediately.
  2. History fallback — if no active match exists, the resolver falls back to the most recently retired match.
  3. UUID only — the resolver returns the product’s UUID only. No product data is exposed publicly.
The resolved product ID is used to redirect to /p/<product-id>.

​
Wrong Domain Behaviour

If a scan request arrives on a platform host (e.g. app.mintid.ai, docs.mintid.ai, or the root mintid.ai), the resolver does not process it. These hosts serve the application, documentation, or marketing site respectively — not product resolution.

​
Query String Preservation

Any query parameters appended to the scan URL are preserved through the redirect. This allows downstream systems to pass tracking or context parameters.

​
Limits & Notes

  • The resolver is public — no authentication is required.
  • Only the product UUID is returned; no product details, pricing, or sensitive data is disclosed.
  • The resolver currently supports GTIN-based paths (/01/...). EAN and UPC public entrypoints are planned for a future release.
  • Batch (/10/...) and serial (/21/...) segments are captured but resolution is GTIN-based.

​
FAQ

The resolver falls back to the most recently retired match. Old printed codes remain functional — they still resolve to the correct product.
No. The resolver returns only the internal product UUID and issues a redirect. No product names, descriptions, pricing, or other data is disclosed.
The resolver uses the permanent brand subdomain on mintid.ai. Custom domain support for resolver paths is not currently available.
Scan requests arriving on platform hosts (app, docs, www, root) are not processed by the resolver. Only the brand’s assigned subdomain handles resolution.