How it is triggered
You control when the popup appears from the Configuration page in the portal. There are three independent settings — automated trigger, manual trigger, and location targeting: Automated trigger — when the popup fires on its own:- Every page — any unverified visitor sees it immediately on every page load
- Specific pages — only on URLs matching patterns you define (e.g.
/shop/*,/checkout*) - Never — the popup never fires automatically; verification is triggered manually
- Optionally configure one or more CSS selectors (e.g.
#add-to-cart,.checkout-btn) - Clicking those elements will be intercepted and the popup shown, regardless of the automated trigger setting
- Once verified, the buttons work normally for the duration of the session
Location targeting
If you only need age verification in certain markets, you can scope the automated trigger to specific countries, based on the visitor’s network location.- All countries (default) — the automated trigger applies to every visitor, regardless of location
- Only these countries — the automated trigger fires only for visitors in the countries you list
- Everywhere except these countries — the automated trigger fires everywhere except the countries you list
Location targeting only affects the automated trigger. Manual trigger buttons and the JS API always show the popup when called, regardless of the visitor’s location.
Branding
The popup displays Veriox branding and a short explanation of the Concordium ID process. Custom branding (your logo and colours) is available on paid plans — contact support@veriox.io if you need this.Mobile
The popup works on mobile browsers. On mobile, the QR code is replaced with a direct link that opens the Concordium wallet app automatically.Restricting the popup to specific pages
If most of your site doesn’t need verification — your homepage, marketing pages, login page, and so on — use Specific pages for your automated trigger instead of Every page, and list only the URL patterns that should require verification (e.g./shop/*, /checkout*). Pages that don’t match any pattern are served without the verification check.
There isn’t currently a separate “exclude these pages, verify everywhere else” mode — for a mostly-open site with a few pages to protect, list those pages directly rather than trying to enumerate everything else.
