NP AgeVerify
Build a branded, self-hosted PrestaShop age gate with four declaration methods, country and catalogue age rules, five layouts, six themes, checkout enforcement and an auditable first-party decision trail.
→ €49 one-time for a first-party gate with no per-check charge or external age-verification SaaS dependency.
Inspect the exact age-gate release before trusting it with a live policy.
Match the delivered ZIP, inspect the native PS8/PS9 lifecycle and upgrade path, then decide whether self-declaration fits the risk and operating model of your store.
One public version, one private artifact identity.
The catalog current-version pointer and private download path resolve to the same deterministic ZIP exercised by every lifecycle and browser gate.
b4404d94b490aaf2dbdbfcf005a9b6c3d51fc1687aa8a501d3c4d60d51437435The package has no PrestaShop Product Key and no authenticated official Validator run is claimed. Marketplace submission remains gated even though direct delivery is live.
Reproduce the gate without submitting personal data.
Use an invented date. Change the base policy, detected-country override and catalogue tiers to see the effective age, cookie, checkout and audit decision.
- Calculated example age
- 24
- Effective required age
- 21+
- Gate on this surface
- Visible
- Decision cookie
- Would be set for 30 days
- Checkout
- No checkout redirect in this state
Browser record
Signed first-party HttpOnly np_age_verified token; SameSite=Lax; Secure on HTTPS; session fallback when persistent cookies are unavailable.
Server record
Event for this simulated state: verify / passed / birth_year 2002
Columns in the delivered log table
id_shop · id_customer · id_cart · event_type · result · rule_context · minimum_age · birth_year · ip_hash · user_agent_hash · date_add
Release 1.2.10 has no automatic audit-log expiry or purge. Cookie days do not delete audit rows; seven-day cleanup applies only to rate-limit and alert guard rows.
Product simulator only. It does not determine the applicable age, evidence level, lawful basis, retention period or delivery control for any product or country.
Inputs stay in this browser and are never submitted to Neuroplugin. Use invented examples only.
Experience NP AgeVerify
Follow real shopper and merchant paths, inspect the interface at full size, then open the live demo when one is available.
Make the interruption feel native to the brand
The blocking gate keeps every action reachable, traps focus outside inline mode and displays the effective threshold for this exact context.
- Full DOB is one of four selectable methods.
- Future dates are rejected again on the server.
- Confirm and leave actions remain explicit.
This tour uses real product captures and documented behavior. It is not a performance benchmark or a promise of storewide uplift.
Check your store before you buy
Answer four release-specific questions. The result identifies what to validate next; it is not an automatic compatibility guarantee.
NP AgeVerify 1.2.10 gives PrestaShop 8 and 9 merchants one operational workspace for age-gating the whole store or only selected categories and products. Choose full date of birth, an 18+ acknowledgement, Yes/No, or a birth-year dropdown. A country rule can replace the base threshold when GeoIP is available; product, category and cart tiers can raise it. The final requirement is always the highest applicable age.
The storefront is deliberately configurable instead of looking like a generic system popup: six visual themes, five layouts, logo and industry icons, brand colours, background effects, consent text and custom CSS. The module can exclude controllers or custom URLs, bypass recognised search and social-preview crawlers, and fall back to a secure session when persistent cookies are blocked.
Verification stays on the shop server. DOB and birth-year paths have strict server validation, rate limiting and optional email alerts. The back office includes filtered audit history, CSV export and aggregate analytics; PrestaShop GDPR export/delete hooks cover linked customer rows. Guard rows used for throttling are opportunistically pruned after seven days.
This remains self-declaration—not identity, document, biometric, payment or delivery verification. The audit table has no automatic retention scheduler, so the merchant must define and operate an appropriate deletion period. Installation alone does not establish legal compliance in any country.
What it does
- Four shopper methods: full DOB, 18+ checkbox, Yes/No, or birth-year dropdown—with strict server-side rejection of malformed and future dates.
- Effective age = highest applicable base/country, category, product or cart tier; the pending decision is signed before verification.
- Six themes and five layouts, with logo, icon presets, colour palette, background effects, consent copy and custom CSS.
- Storewide or restricted catalogue scope, checkout enforcement, excluded controllers/URLs and recognised crawler/social-preview bypass.
- First-party HttpOnly SameSite=Lax decision cookie, signed age binding and secure session fallback when cookies are unavailable.
- Filtered audit log, CSV export, analytics, customer-data export/delete hooks, rate limiting and optional failure alerts.
In the wild
Who this is for
Best for a merchant-controlled declaration gate
Use it when independent review accepts self-declaration, you want the decision on your own server, and country/catalogue thresholds plus a polished branded experience matter.
Not for verified-identity or delivery evidence
Choose a specialist process when the applicable risk requires documents, biometrics, trusted age tokens, payment identity, carrier checks or proof at delivery.
vs identity-verification SaaS
These are different evidence models. NP AgeVerify optimises a first-party declaration gate; a specialist identity service may be required when the merchant must establish stronger evidence.
| Capability | NP AgeVerify | identity-verification SaaS |
|---|---|---|
| Evidence model | Visitor self-declaration | May verify identity/age evidence |
| Data path | Your PrestaShop server | External provider flow |
| Pricing | €49 one-time | Usually recurring / per check |
| Identity assurance | No | Provider-specific |
Why neuroplugin
- Why more than a basic 18+ popup?
- Real stores need route scope, country and catalogue precedence, checkout enforcement, blocked-cookie behavior, operational evidence and a gate that belongs to the brand.
- Why publish the exact limits?
- A merchant should choose the evidence model before buying. Self-declaration can be appropriate in some reviewed contexts and insufficient in others; hiding that distinction creates the wrong sale.
- Why no monthly platform fee?
- The package runs locally and performs no metered verification call. Optional six-month renewal covers continued updates and support, not permission to keep the installed release running.
By the numbers
Questions answered
- Is NP AgeVerify identity verification?
- No. It records a visitor declaration using DOB, birth year, checkbox or Yes/No. It does not inspect documents, biometrics, payment identity, government data or delivery evidence and cannot prove who made the declaration.
- How are country and product age rules combined?
- GeoIP can replace the base policy age for a detected ISO2 country. Category, product and cart tiers can then raise it. Version 1.2.10 uses the highest applicable value and signs that pending age before the verification request.
- Does the server reject future or malformed dates?
- Yes in 1.2.10. The controller rejects arrays, decimals, negatives, zero and partially numeric fields; the DOB service rejects invalid calendar dates, years before 1900 and dates after today. Both PS8 and PS9 paths passed direct-request regression tests.
- What data is stored?
- The audit table stores shop/customer/cart IDs when present, event, result, rule context, effective minimum age, birth year when the chosen method supplies one, hashed IP, hashed user agent and timestamp. It does not have day or month columns. The full DOB is processed by the same-origin endpoint but not stored in that table.
- Does the audit log delete itself automatically?
- No. Seven-day cleanup applies to rate-limit and alert guard rows, not the audit history. The merchant must choose, document and operate an audit-retention process. GDPR export/delete hooks cover rows linked to a customer account.
- Will it work with every checkout and theme?
- No universal guarantee is possible. The package is runtime-verified on PrestaShop 8 and 9, including Classic and Hummingbird-aware styling, but custom checkout controllers, theme overrides, consent layers and cache/CDN rules must be tested on a production-like staging clone.
Protect more of the revenue journey
A conversion-focused one-page checkout for PrestaShop 8 and 9 with three familiar presentation presets, deep brand controls, optional Spanish retailer-tax adapter support and a built-in observe-only Sentinel.
Turn local PrestaShop SEO evidence into a prioritized, reviewable action queue—without ranking guarantees or obsolete indexing promises.
Native loyalty for PrestaShop 8 and 9: tiers, wallet, referrals, Reward Shop, payouts and 11 localized transactional emails — no external SaaS.
Ready to add NP AgeVerify?
Build a branded, self-hosted PrestaShop age gate with four declaration methods, country and catalogue age rules, five layouts, six themes, checkout enforcement and an auditable first-party decision trail.