Pay4All Age Verification - For WooCommerce & Pay4All Shop
| 开发者 | pay4all |
|---|---|
| 更新时间 | 2026年8月25日 00:10 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
Pay4All Age Verification blocks any order containing age-restricted products until the customer has submitted a 5-second video selfie and/or valid proof of identity, including the front and back of the document. The video selfie and identity document photos are captured by scanning a QR code, allowing the customer to continue the verification process on their smartphone.
The plugin integrates with WooCommerce and Pay4All Shop (pay4all-form). Install it alongside either e-commerce solution, and it will only appear when a product is marked as requiring age verification. The same settings page (
Pay4All AGE > Settings) manages both integrations. A merchant using both Pay4All Shop and WooCommerce therefore only needs to configure the verification process once and will benefit from consistent behaviour across both platforms.
Identity document photos and/or video selfie
The merchant can choose to require either verification method or both, depending on the applicable legislation.
WooCommerce support
Simply select the Requires age verification option on the product page to trigger QR-code age verification during checkout. The customer's age verification status can be reviewed directly from the order.
Pay4All Pro provides the WooCommerce integration. Pay4All Age remains completely free when used with Pay4All Shop.
How it works
- The merchant selects the Requires age verification option on the product edit screen.
- When a customer adds the product to their order form, a panel containing a QR code appears.
- The customer scans the QR code with their smartphone. The mobile capture page opens and allows them to take the required identity document photos or record the video selfie using their phone's camera.
- The form displayed on the customer's computer automatically unlocks once all required photos and/or the video selfie have been submitted.
- When the order is submitted, the encrypted photos and videos are stored with the order. They are only decrypted on demand by an administrator from the order edit screen.
- Photos are encrypted with AES-256-GCM using a per-order (or per-user) subkey derived via HMAC-SHA256 from a master key.
- Ciphertexts live in a private folder guarded, so they are never web-servable.
- Admin decryption endpoint is nonce-protected and requires the
edit_userscapability. - Photos are auto-purged when the order (or user) is permanently deleted.
安装:
- Upload the plugin to
/wp-content/plugins/pay4all-age-verification/or install via Plugins > Add New. - Activate it from the Plugins menu.
- Open Pay4All AGE > Paramètres to tune what documents you require and to override the customer-facing texts if needed.
- On each product that requires an age check, tick the Requires age verification checkbox on the product edit screen (Pay4All Shop product).
屏幕截图:
常见问题:
Do I need Pay4All Shop or WooCommerce?
Yes. Pay4All Age Verification is a companion plugin — it plugs into either Pay4All Shop (free, ships the form-based checkout) or WooCommerce (via the paid Pay4All Pro add-on). On a bare WordPress install without either, the plugin stays dormant and shows an admin notice on the Plugins screen.
How are photos encrypted?
AES-256-GCM with a per-order (or per-user) subkey derived via HMAC-SHA256 from a master key. The master key is generated once and stored in wp-content/uploads/p4all-age-secure/age.key (mode 0600). Ciphertexts live in the same private folder, guarded by .htaccess, index.php and web.config so they are never web-servable — a direct URL always returns 403 / 404. See the Security section above for the full threat model.
Where is the master encryption key stored?
Outside the database, in wp-content/uploads/p4all-age-secure/age.key. This means a stolen SQL dump alone is not enough to decrypt the photos — the attacker would also need read access to that specific file. Please make sure your backup strategy either encrypts wp-content/uploads/p4all-age-secure/ or excludes it entirely from the backup archive.
What happens to the photos when an order is deleted?
They are auto-purged. Both the WooCommerce order lifecycle (woocommerce_delete_order hook) and Pay4All Shop order deletion trigger KycStorage::purge_order(), which removes every encrypted blob and the order-scoped directory. A daily cron also purges session-scoped buckets older than the configured TTL (default 24 h).
What happens if a user account is deleted?
The delete_user hook fires KycStorage::purge_user() — every stored user photo (recto / verso / selfie_1 / selfie_2) is removed together with the user record. GDPR-friendly by default.
Does the mobile capture page work on all phones?
The page uses the native <input type="file" accept="image/*" capture="…"> API — supported by Safari (iOS 6+), Chrome, Firefox, Edge on both Android and iOS. On the desktop side, the QR code is generated with a pure-JS library (no external service call) and the pairing is polled every 4 seconds via a REST endpoint scoped to the session token.
Does it work with WPML / Polylang?
Yes. When a product's Requires age verification flag is ticked on a source-language product, every translation is treated as age-restricted too — even if the flag hasn't been mirrored to the translation post. Same behaviour on WooCommerce products via Pay4All Pro.
Which languages ship out of the box?
French (fr_FR), German (de_DE), Italian (it_IT) and English (en_US). Every customer-facing string is also overridable per-language from the settings page — merchants can rewrite the KYC panel copy without touching a .po file.
Does the plugin contact any external service?
No. Photo capture, encryption, storage and admin decryption are all local — nothing leaves the site. The QR code is generated client-side ; the mobile page polls only your own WordPress REST API.
更新日志:
1.6.1
- Compat Pay4All Pro : un client déjà vérifié via son compte saute automatiquement l'étape de vérification d'âge sur ses commandes suivantes, sans rechargement de page.
- New « Add-ons » admin sub-page listing the other Pay4All plugins with install / learn-more links.
- Translations (FR / DE / IT) updated to cover the new Add-ons strings.
- i18n: new msgid for the WC product description "When ticked, this product triggers ID + selfie capture at checkout." (used by Pay4All Pro 2.3.3+).
- UX: "Pay4All Shop" link added on the host-plugin notice and on the WooCommerce teaser page.
- UX: WooCommerce teaser gains a "Download Pay4All Pro" primary button next to the "Discover" secondary button.
- Fix: Settings > Texts placeholders empty in FR / DE / IT after 1.5.0 refactor. Now routed through gettext per language.
- UX: text fields pre-filled with the shipped default when no merchant override is saved.
- i18n refactor - source strings converted to English. All user-facing strings in the plugin code are now in English, matching the WordPress i18n convention (
msgid= English source,msgstr= translation). Full translation packs are bundled and validated for French (fr_FR), German (de_DE) and Italian (it_IT) under/languages/. - Config.php cleanup. The historic per-locale
TEXT_DEFAULTS/ADMIN_STRINGSinline catalogs (~600 lines of hardcoded fr/de/it/en strings) are replaced by a single English source array feeding through gettext. The merchant per-language text override (Pay4All AGE > Settings > Texts) still wins over the shipped translation, so custom copy is preserved on upgrade. - No behaviour change, no configuration change, no manual action required.
- Readme rewrite: Description, WooCommerce support and How it works sections rewritten in clearer English to better reflect the current feature set (video selfie, QR-code capture, choice between ID document and/or video selfie). No behaviour change.
- Anti-fraude étendu aux photos : le code défi 4 chiffres est désormais aussi incrusté sur les photos de pièce d'identité (recto + verso), pas seulement sur la vidéo. Composé côté client via un canvas dans le coin haut-droit avant l'upload. Le code n'est jamais affiché au client (ni pendant la vidéo, ni avant la photo) - il apparaît uniquement dans les fichiers finaux, et l'admin le voit dans la lightbox au-dessus de chaque item pour cross-check visuel.
- UX desktop : sur les écrans ≥ 901 px, les boutons « Prendre la photo » / capture vidéo directe sont masqués - le client est forcé à scanner le QR code pour capturer depuis son smartphone. Garantit que chaque fichier passe bien par la caméra du téléphone (où le code défi est burned par le canvas). Mobile / tablette portrait garde les boutons.
- New liveness selfie video replaces the two static selfie photos. When the merchant asks for a selfie, the mobile capture page now records a single 5 s clip via
MediaRecorder, with a random 4-digit challenge code (minted by the server) burned into the top-right of the recorded pixels as a real-time proof. The head-motion prompt (« Tournez lentement la tête ») shows as an HTML overlay to guide the customer but doesn't pollute the recorded file. Video is compressed client-side (VP8 or H.264, ~500 kbps, ~325 KB for 5 s), encrypted AES-256-GCM before storage, and played back inline in the admin lightbox with the same shield button. Legacy orders that stored the two-photo variant remain readable and decryptable - no data migration needed. - No third-party service : the challenge code is minted by the plugin, the recording, overlay compositing and compression all run in the customer's browser, and the encrypted bytes never leave the merchant's server. Matches the plugin's « 100 % local » promise as before.
- UX customer : « Vous aurez 5 secondes pour tourner lentement la tête » notice shown before the recording starts ; the customer then previews the recorded clip and clicks « Valider et envoyer » (or « Refaire la vidéo ») BEFORE the upload begins. « Recommencer la vidéo » button only surfaces after a successful upload.
- UX admin : the lightbox displays the « Code attendu dans la vidéo : #XXXX » banner above the video player so the merchant can visually cross-check the digits burned into the video pixels against the reference code - proof the clip is a real-time recording, not a stale replay. The code is persisted on the order as
post_metaat upload time (checkout + resend flows). The video autoplays and loops muted for at-a-glance review. - UX admin resend : a single « Demander au client de renvoyer les photos et la vidéo » button now resends the whole KYC bundle at once ; no more per-photo checkboxes. The default OR-choice option at checkout now follows the merchant's drag-drop order (was always « pièce d'identité » before, even when moved to 2nd position).
- Réglages admin : new « Vidéo » text-override section under
Pay4All AGE > Paramètres > Textesexposing every customer-facing string of the video capture flow (pre-recording notice, single head-motion prompt, statuses, Démarrer / Valider / Refaire / Recommencer buttons, camera-denied / unsupported-browser errors), overridable per language. Default text is now shown as an input placeholder (empty field = « use built-in translation »). - Cleanup : dropped the now-obsolete admin fields « Libellé - Selfie 1 / 2 (historique) » and « Bouton - Prendre le selfie ». Renamed the drag-drop step « Selfies » to « Vidéo selfie » (FR / EN / IT) / « Selfie-Video » (DE) and the metabox hint on the order screen to mention the video alongside the photos.
- Plugin Check : sanitisation of
$_POST['slots']viaarray_map('sanitize_key', wp_unslash(...))in the admin resend handler ;mt_rand()replaced bywp_rand()in the challenge-code fallback.
- Fix : the resend « Documents received » screen didn't paint on the desktop copy of the mobile page after the customer uploaded from their phone. Root cause : the resend token was cleared the instant the last photo landed, so the desktop poll got 410 and never observed the « satisfied » state. The token now stays alive for a 15-minute grace window after completion and the admin notification is idempotent (no double e-mail on re-uploads).
- Fix : admin resend e-mail on Pay4All Shop orders was missing the order link because
get_edit_post_link()returns an empty string when called from the customer's public REST upload (noedit_postcap). URL is now built manually. - Fix : « Ask to resend » checkboxes now appear on WooCommerce orders even when the photos live in the customer's account bucket rather than the order bucket.
- UX : the resend mobile page now shows both a QR code AND the clickable URL below it so a customer who opened the e-mail on their desktop can either scan or copy-paste to their phone. Polls the status endpoint every 4 s so the desktop copy flips to « Documents received » once the phone finishes.
- New « Ask the customer to resend the photos » admin action. On any order screen (Pay4All Shop AND WooCommerce - via Pay4All Pro), the age-verification lightbox now shows a checkbox next to each photo. The admin ticks the ones to retake and clicks the new button - the customer receives an e-mail with a secure 30-day link that opens the same mobile capture page, this time restricted to the requested photos. New photos overwrite the old encrypted files (same order id, so admin decryption keeps working).
- Once every requested photo has been re-uploaded, the admin gets a single « new photos received » notification e-mail - never one per photo.
- Customer + admin e-mails have their own subject + body per locale in
Pay4All AGE > Paramètres > Textes > Renvoi, with placeholders{customer_firstname},{customer_lastname},{order_number},{slots_list},{link},{admin_order_url},{site_name},{shop_name}. Sensible FR / DE / IT / EN defaults ship out of the box.
- New drag-and-drop reorder of the ID card and selfies steps from
Pay4All AGE > Paramètres > Documents à demander > Ordre d'affichage. The chosen order applies to both Pay4All Shop and WooCommerce checkouts (single source of truth). Keyboard fallback (up/down arrows) included for accessibility. - Plugin renamed to « Pay4All Age Verification for WooCommerce & Pay4All Shop » to reflect the dual-storefront support already provided when paired with Pay4All Pro.
- Full FR / DE / IT / EN translations for the new « Ordre d'affichage » UI strings.
- Fix : the KYC text-override form is now correctly styled when embedded inside Pay4All Shop's « Réglages › Vérification d'âge » tab. The settings-page CSS was only enqueued on the plugin's own page, so labels overlapped with inputs and the language accordions rendered as bare
<details>markup.
- Renamed the settings page title from « Pay4All — Age verification » to « Pay4All Age verification » in the four bundled languages.
- Added FR/EN/DE/IT translations for the « Important reminder » box on the settings page (previously French-only).
- Fix bug security.
- Initial release.
- Product-level Requires age verification checkbox (Pay4All Shop).
- Cross-device QR flow (desktop QR -> mobile capture page).
- AES-256-GCM encryption at rest, per-order and per-user derived subkeys.
- Metabox on the Pay4All Shop order edit screen with nonce-protected decrypted-photo streaming and a lightbox to view every document side-by-side.
- Shield column on the WordPress users list — one click opens the customer's verified documents.
- Settings page with OR / AND mode, purge delay, per-locale text overrides.
- FR / DE / IT / EN built-in translations, with 4-language text override per string from the settings page.
- WPML / Polylang aware : translated products inherit the Requires age verification flag from their source.