Step 1
See the badge
Customer sees the live card, compact pill, static link, or QR card beside the claim.
Trust Badge display guide
Display live proof
Use a live embed, direct link, or QR route so customers can check the current Qubicbox record. A screenshot is never proof.
Recommended setup
Live card plus QR fallback
Badge ID
QBX-TB-2026-000001
Customer action
Open live record before relying
Domain control
Exact approved hostnames only
Fallback
Direct link or QR, not screenshots
Customer journey audit
Keep every Trust Badge route connected
The customer path should never end at an image. Each surface must lead from the visible badge to the live Qubicbox record, then to a clear report route when something does not match.
Step 2
Open Qubicbox
The badge resolves to Qubicbox so the customer can see the current status and holder details.
Step 3
Compare context
The customer compares holder name, domain, profile, badge ID, scope, and last checked date.
Step 4
Act or report
If the record does not match, the customer pauses and reports the concern with the badge ID.
Distribution asset pack
Copy, download, and publish the governed assets
Use these assets together: live embed for websites, static link for restricted surfaces, QR card for offline handover, and misuse reporting for copied or suspicious badges.
Report misuse route
Send customers here if a badge appears as a screenshot, wrong-domain embed, copied image, or suspicious profile claim.
Report screenshot misuseScript embed
Live card
Primary website and storefront proof where scripts are allowed.
Shows current status, approved-domain controls, and the live Qubicbox record link.
Static HTML link
Compact pill
Headers, listing rows, marketplace bios, signatures, and tight layouts.
Keeps the badge visible without pretending that a copied image is live proof.
Downloadable print asset
QR card
Packaging, invoices, receipts, handover notes, and in-person checks.
Pairs the QR code with the badge ID so the customer can compare the scanned page.
Prefilled customer link
Report route
Support pages, dispute replies, display guidance, and copied-badge warnings.
Sends suspicious use into TrustOps with the category and badge ID already captured.
Live website snippet
<div class="qubicbox-trust-badge" data-badge-id="QBX-TB-2026-000001" data-endpoint="public" data-domain-binding="required" data-approved-domains="example.com"></div>
<script async src="https://www.qubicbox.com/trust-badge/embed.js"></script>Compact pill snippet
<a class="qubicbox-trust-badge-pill" href="https://www.qubicbox.com/trust-badge/verify/badge/QBX-TB-2026-000001" target="_blank" rel="noopener noreferrer">
Trust Badge active: QBX-TB-2026-000001
</a>Static fallback snippet
<a href="https://www.qubicbox.com/trust-badge/verify/badge/QBX-TB-2026-000001" target="_blank" rel="noopener noreferrer">Verified: QBX-TB-2026-000001</a>QR handover copy
Trust Badge: QBX-TB-2026-000001
Scan or open: https://www.qubicbox.com/trust-badge/verify/badge/QBX-TB-2026-000001
A screenshot is not proof. Check the live Qubicbox record before relying.Approved-domain checklist
- Confirm the exact approved domain before publishing the live embed.
- Keep the badge ID visible near every QR code or static link.
- Use the static link only where scripts are blocked.
- Include the misuse report route anywhere customers may see a copied badge.
Display options
Choose the right surface
Live website card
Profile pages, storefronts, listings, directories, and partner pages.
Use this when the customer has enough space to read status, evidence scope, and the live record link.
Compact website pill
Headers, listing rows, product cards, signatures, and account summaries.
Use this when space is tight but the Trust Badge still needs to resolve through Qubicbox.
Static fallback
Platforms that block scripts, marketplace descriptions, email footers, and CMS fields.
Use a direct link to the public record. The text must not imply that a static image is current proof.
QR handover
Packaging, receipts, invoices, in-person handover, print cards, and social posts.
Pair the QR code with the badge ID so customers can compare the scanned page with the displayed claim.
Approved domains
Keep the badge bound to the right website
Use the exact hostname that serves the badge, such as example.com or shop.example.com.
Do not enter full paths, query strings, or temporary preview URLs as approved domains.
Review approved domains after a website migration, storefront change, or agency handover.
If the domain is not approved, the customer should use the live Qubicbox record before relying on the claim.
Customer checklist
What customers should check
Open the live Qubicbox record before paying, releasing goods, or relying on a badge claim.
Compare the badge ID, holder name, status, evidence scope, and last checked date.
Treat screenshots, copied images, and cropped social posts as signals to verify, not as proof.
Pause if the badge is under review, suspended, revoked, expired, or shown on an unapproved domain.
Misuse signals
When to pause and verify
The badge is only shown as a screenshot.
The badge link opens a non-Qubicbox domain.
The holder name does not match the page, listing, invoice, or profile.
The badge appears on a domain that the live embed marks as unapproved.