QR Code Resolver Domain

By default, your GS1 Digital Link QR codes point to a TrackVision resolver URL like dpp-example.tvai.me. With a custom domain, your QR codes use your own brand URL instead — e.g., dpp.mybrand.com.

This matters because the resolver URL is printed on physical products via QR codes. Once printed, it can't be changed. Using your own domain gives you control over the URL your customers see when they scan.

How It Works

Consumer scans QR code
        │
        ▼
https://dpp.mybrand.com/01/09506000134352
        │
        │  CNAME → dpp-example.tvai.me
        ▼
TrackVision Resolver
        │
        ├── Accept: application/ld+json → JSON-LD DPP (gs1:dpp)
        └── Default → 302 redirect to product page (gs1:pip)

Your custom domain is a CNAME alias to your TrackVision resolver. All GS1 Digital Link resolution, DPP delivery, and scan analytics continue to work — the domain is just a branded front door.

Step 1: Choose Your Domain

Pick a subdomain you'll use for QR codes. Common choices:

Domain	Notes
dpp.mybrand.com	Clear purpose, recommended
id.mybrand.com	Short, good for small QR codes
scan.mybrand.com	Consumer-friendly
link.mybrand.com	Generic

Important

Once you print QR codes with a domain, changing it means reprinting. Choose carefully.

Step 2: Get Your Resolver Address

Your TrackVision resolver hostname is shown in the platform under Settings → Reference URLs.

It follows the format:

{your-account}.tvai.me

For example: dpp-acme.tvai.me

Step 3: Add a DNS Record

In your DNS provider's control panel, add a CNAME record:

Type	Name	Value	TTL
CNAME	dpp	dpp-acme.tvai.me	3600

This makes dpp.mybrand.com resolve to your TrackVision resolver.

Root domains

If you want to use a root domain (e.g., mybrand.com without a subdomain), use an ALIAS or ANAME record instead of CNAME. Not all DNS providers support this — check your provider's documentation.

Step 4: Configure in TrackVision

1. Go to Settings → Reference URLs in the TrackVision platform
2. Set your Resolver Domain to your custom domain (e.g., dpp.mybrand.com)
3. Click Save

TrackVision will use this domain when generating GS1 Digital Links for your QR codes.

Step 5: Verify

Test that your custom domain resolves correctly:

# Test the resolver redirect (gs1:pip)
curl -I https://dpp.mybrand.com/01/09506000134352
# Should return HTTP 302 with Location header

# Test the DPP response (gs1:dpp)
curl -H "Accept: application/ld+json" \
  https://dpp.mybrand.com/01/09506000134352
# Should return JSON-LD Verifiable Credential

# Verify DNS resolution
dig dpp.mybrand.com CNAME
# Should show CNAME pointing to dpp-acme.tvai.me

GS1 Digital Link Format

With your custom domain, your GS1 Digital Links look like:

https://dpp.mybrand.com/01/{gtin}
https://dpp.mybrand.com/01/{gtin}/21/{serial}
https://dpp.mybrand.com/01/{gtin}/10/{lot}

These are printed as QR codes on your products. When scanned:

• Consumers get redirected to your product landing page (gs1:pip)
• Systems requesting application/ld+json get the JSON-LD DPP (gs1:dpp)
• All scans are tracked in your analytics dashboard

DID Web Impact

If you use Ed25519 DPP signing, the issuer field in your Verifiable Credentials uses your resolver domain:

{
  "issuer": "did:web:dpp.mybrand.com"
}

The DID document is served at https://dpp.mybrand.com/.well-known/did.json automatically by the resolver. Third parties verifying your DPP signatures will resolve your custom domain — no additional setup needed.