Age verification without turning checkout into an obstacle.
PrestaHeroes AgeChecked Integration provides a complete post-order age-verification workflow for restricted products—from internal testing, official sandbox scenarios, and stealth production rollout to approvals, exceptions, customer messaging, and detailed compliance records.
Build confidence before every customer sees it
Move from configuration to live operation through a practical, low-risk rollout path. Test the customer journey, verify provider response handling, validate privately on production, and then open the workflow to all matching orders.
Configure
Keep sandbox and production credentials separate, choose the verification method, define country scope, and select restricted products.
Prove it in sandbox
Run official AgeChecked AC0120 scenarios for approved, partially found, not found, and underage outcomes against the real sandbox endpoint.
Test production privately
Enable stealth mode so storefront notices, DOB collection, prompts, and provider calls run only for approved tester IP addresses.
Go live with control
Disable stealth mode when testing is accepted. The same proven order workflow then applies to every matching customer and product.
Apply age checks exactly where they belong
Broad category rules make setup fast. Product-specific overrides handle the exceptions. Country scope prevents irrelevant age-verification messaging or processing outside the markets you configure.
Category-based rules
Select complete categories and subcategories to apply age verification across a product range.
Product-level overrides
Require age checking, exclude a specific product, or let the product inherit its category rule.
Country-aware scope
Apply the workflow only to listed countries—or to all countries except your exclusions.
Relevant storefront messaging
Show the 18+ AgeChecked assurance only for restricted products and only when the visitor’s active country is in scope.
Previous approval option
Trust a customer’s earlier AgeChecked approval to avoid unnecessary repeat checks while recording the new order’s compliance decision.
Custom customer content
Control success, review, denial, technical-error, order-confirmation, and hosted-return-page messaging from the module.
Post-order verification designed to protect conversion
The customer completes checkout first. The module then evaluates the saved order, its delivery country, and its restricted products before starting the configured AgeChecked process.
- Order is created normallyThe module does not replace or rewrite the payment status.
- Eligibility is resolvedCountry, category, product overrides, and previous approval are evaluated from the persisted order.
- Verification runsAC0120 can return an immediate result; AC0130 sends the customer through AgeChecked’s hosted evidence flow.
- Compliance is recordedThe order receives a separate Pending, Approved, or Needs approval state.
- Exceptions reach the merchantOrders that cannot be cleared automatically appear in the review queue and on the order itself.
Collect only what the selected method requires
- AC0120: collects DOB after purchase for an in-scope restricted order and sends it to AgeChecked.
- Transient DOB: the module does not store the customer’s DOB locally.
- AC0130: evidence is handled through the hosted AgeChecked journey rather than collected by PrestaShop.
- Sanitized diagnostics: sensitive credential fields are masked in stored request traces.
- Server callback: the AC0130 callback remains the authoritative processor for the final verification result.
Choose the right path—or use the intelligent fallback
| Method | Best for | Customer experience | Module handling |
|---|---|---|---|
| AC0120 / cceroll | Fast automated dataset verification | Transient post-purchase DOB entry | Immediate result mapping and order compliance update |
| AC0130 hosted ID check | Document-based verification when stronger evidence is needed | Hosted ID, selfie, and liveness process | Customer redirect, branded return page, callback processing, and pending-state tracking |
| AC0120 → AC0130 fallback | Maximum automation with a second route for customers not approved by AC0120 | Fast check first; hosted evidence flow only when required | Automatic transition from the initial check into AC0130 with linked diagnostics |
Every result is connected to the order that matters
Your team does not need to hunt through disconnected systems to understand what happened. The module brings the decision, provider context, and merchant actions into the PrestaShop back office.
Dashboard and alerts
See counts for orders needing approval, approved restricted orders, product-level rules, and verification events.
Dedicated review queues
Open separate Needs approval and Approved queues with order, customer, delivery, payment, provider, AgeCheckID, and total context.
Order-level compliance panel
Review the AgeChecked state directly on the PrestaShop order page without confusing it with payment status.
Manual approval with reason
Approve an exception with a required audit note. The action is recorded in the module log and the order’s private messages.
Cancel when no longer required
Close the age-verification requirement when a restricted item is removed or another documented fulfilment decision makes it unnecessary.
Correct and rerun AC0120
Enter corrected customer details, provide an audit reason, send a real AC0120 request, and retain the new provider result.
A compliance record built for investigation—not guesswork
- Chronological verification event history
- Order, customer, delivery, payment, and order-total context
- Provider status, normalized result, method, code, and AgeCheckID
- Sanitized raw provider request visibility
- Raw provider response visibility for diagnostics
- Manual approval, cancellation, and recheck notes
- Private order messages that preserve staff actions
Built specifically for modern PrestaShop
- Compatible with PrestaShop 8.x and 9.x
- Resilient order-confirmation hook fallbacks for varied themes and payment modules
- Product-page rule integration and country-scoped 18+ assurance messaging
- Separate module compliance status that does not overwrite native payment state
- Upgrade-safe module architecture with retained compliance history by default
Requirements and important notes
- A working PrestaShop 8 or PrestaShop 9 shop.
- An AgeChecked merchant account and the appropriate sandbox and/or production API credentials.
- AgeChecked registration of the module’s generated AC0130 callback and redirect URLs when using hosted verification.
- HTTPS and a production environment capable of receiving provider callbacks.
- Merchant configuration of the products and countries that legally or operationally require age verification.
AgeChecked account charges, provider approval, legal advice, and custom installation services are not included unless stated separately. The merchant remains responsible for confirming that its age-verification policy and fulfilment procedures satisfy the laws and rules that apply to its products and markets.
Frequently asked questions
Does the module block checkout?
No. The module follows a post-order workflow. PrestaShop creates the order first, and the module records a separate age-compliance state for fulfilment handling.
Does AgeChecked change the payment status?
No. Payment and age compliance remain separate. Your normal PrestaShop payment status stays intact while the module records Pending, Approved, or Needs approval.
Can I test safely on a live shop?
Yes. Stealth mode limits storefront AgeChecked behaviour to specified tester IP addresses, allowing controlled production validation before general release.
Can I require verification for a whole category but exclude one product?
Yes. Product-specific rules take precedence, so an individual product can be required, excluded, or set to inherit its category rule.
What happens when AC0120 does not approve the customer?
You can send the order to merchant review or configure the AC0120 → AC0130 workflow so the customer continues to the hosted ID-verification journey.
Is the customer’s date of birth stored in PrestaShop?
No. For AC0120, DOB is collected transiently after purchase and sent to AgeChecked without being stored locally by the module.
One module. One controlled workflow. No missing pieces.
Configure the rules, prove the outcomes, test privately in production, launch confidently, and give your team the order-level tools and evidence needed to operate age-restricted sales responsibly.
Comments (0)
Your review appreciation cannot be sent
Report comment
Report sent
Your report cannot be sent