Table of Contents
Magento 2 Veratad Age Verification Extension User Guide for Magento 2
Related overview
For a shopper-friendly overview of features and setup, see the Magento 2 Veratad Age Verification User Guide on the storefront. This wiki page remains the full technical documentation.
Extension context
This is a Toweringmedia Magento 2 extension guide generated from the Magento Admin virtual product catalog.
Product page
Overview
The ToweringMedia Veratad Age Verification Extension for Magento 2.4 provides automated age verification for age-restricted products. This extension integrates with Veratad's age verification service to ensure compliance with age-restriction regulations for products like alcohol, tobacco, vaping products, and other restricted items. Perfect for merchants selling age-restricted products, this extension automatically verifies customer age at checkout using Veratad's database and verification services. The extension helps ensure legal compliance while providing a seamless checkout experience for verified customers. Features Veratad Integration – Direct integration with Veratad age verification services. Automatic.
What this extension does
- Magento 2 Veratad Age Verification Extension - Automated age verification for age-restricted products
- Integrates with Veratad for compliance
- Perfect for alcohol, tobacco, and vaping products
- Compatible with Magento 2.4.x
Delivery
This is custom work, not a self-install package. There is no Composer package, no download, and no license key for Veratad Age Verification.
Towering Media scopes, builds, and deploys it for your store as part of an engagement. Pricing and timeline are confirmed with you before any work starts.
To get this built, or to ask whether it fits your store:
Configuration
Configure extension options in Magento Admin, then validate key storefront/admin flows tied to this extension.
Validation checklist
- Configuration saves without errors in Admin.
- Expected storefront/admin behavior is present.
- No critical PHP/JS errors occur during test flow.
- Caches and static assets are refreshed after changes.
Troubleshooting
- Feature missing: verify module status, cache flush, and static-content deploy.
- Unexpected behavior: retest with only required related modules enabled.
- Admin setting not applying: verify config scope and clear cache.
