PrestaShop

The ProofAge Age Verification module puts the hosted verification in front of restricted products, categories and pages, and keeps shoppers who are not verified from buying them, without code. It supports PrestaShop 8.1 to 9.x on PHP 7.2.5+, and needs an HTTPS storefront.

​

What it protects

• The whole shop, or selected products, product categories (with or without their subcategories), CMS pages, front controllers and URL paths, with exclusions. The most specific rule wins: product, then category, then page, then the whole shop.
• Add-to-cart, product quick view, the cart and checkout: they are refused server-side while the cart holds a protected product and the shopper is not verified.
• Order creation: an order with a protected product is not created for a shopper who is not verified, whatever payment module or checkout creates it.

A protected page shows a full-page gate, which search engines do not index, or a blurred overlay that keeps the page content indexable. The verification opens in a modal on the page or on the ProofAge page, as you choose.

​

Install

1. Create a workspace in the ProofAge console, usually Facial age estimation or age verification by ID document, and copy its public and secret keys.
2. Download proofage.zip from the latest release and upload it under Modules → Module Manager → Upload a module, then click Configure. Use the release ZIP, not GitHub’s source archive.
3. On the Connection tab, enter the two keys and click Test connection: it shows the workspace’s name, mode, check type and minimum age.
4. Choose what to protect on the Rules tab, the gate texts and launch mode on Display, and how long a verification stays valid on Validity.
5. In the ProofAge console, set the workspace’s webhook URL to https://your-store.example/module/proofage/webhook. The Connection tab shows the exact URL with a copy button.

The module returns shoppers to https://your-store.example/module/proofage/return and from there to the page they started on.

​

What the shopper sees

A gate explaining that the content is age-restricted, with a button that opens the ProofAge verification. When the verification is approved, the shopper goes back to the page they were on. The module learns the outcome from the webhook, and also checks the status while the shopper waits and when they return, so a delayed webhook does not block them. A shopper who closes the verification before finishing can open it again from the same button. A guest stays verified in that browser for the hours you set; a signed-in customer for the days you set, or for good, on any device. A guest who verifies and then signs in keeps the verification on the account.

​

Orders and customers

The module stores a snapshot of the verification on each order and shows it on the order page: whether one was required, its status and the method (digital identity wallet, or face or document). If an approval is later revoked in ProofAge, the snapshot shows it. The customer page shows whether the customer is verified and has a button to reset it. The module’s page lists recent verifications and webhook deliveries.

​

Privacy

The module keeps verification IDs, statuses, the method and dates, never images or document data. It works with the PrestaShop GDPR module: a customer’s export includes their verifications, and deleting a customer anonymises them.

​

Languages

The module is translated into English, French, Spanish and Italian, and the gate texts can be edited per shop language. It passes the storefront’s language to ProofAge.

​

What it does not do

• Capture inside your own UI: it always uses the hosted verification.
• Hide protected products from listings, search and the home page: their cards stay visible, and adding them to the cart opens the gate.
• Detect third-party one-page checkouts on its own: add their controller to the protected controllers. Order creation is blocked either way.