How you integrate age verification depends on your stack and who maintains it. Two common patterns are a direct API integration and a ready-made plugin for WordPress or WooCommerce.

API integration. You redirect the user to the age verification provider (e.g. via OAuth-style flow with client_id and redirect_uri). The user completes verification; the provider redirects back with an authorization code. Your backend exchanges the code for a JWT or signed token (and optionally an Audit ID). You then grant or deny access based on the token. This fits custom apps, headless front ends, and any platform where you control the backend. You get full control over when to trigger verification, how to cache or refresh tokens, and how to pass the result to your business logic.

WordPress / WooCommerce plugin. If your site runs on WordPress and you need to gate content or purchases (e.g. alcohol, age-restricted products), a plugin can handle the redirect, callback, and token validation. The plugin typically checks for a valid age verification result (and perhaps an Audit ID) and then allows access to the page, product, or checkout. Best for teams that prefer minimal code and quick deployment. Ensure the plugin is maintained and that it does not store more user data than necessary (e.g. only the verification outcome and audit ID, not raw tokens or PII beyond what you need).

Hybrid. Some providers offer both: an API for full control and a plugin for WordPress. You might start with the plugin for a marketing or e‑commerce site and add API integration later for a custom app or forum. In all cases, prefer a solution that returns only a verification outcome and audit trail, so your integration stays simple and compliant.