Pay4All Age Verification for WooCommerce & Pay4All Shop
| 开发者 | pay4all |
|---|---|
| 更新时间 | 2026年7月23日 00:56 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
Pay4All AGE > Paramètres) drives both integrations — a merchant running Pay4All Shop AND WooCommerce configures the verification once, gets consistent behaviour everywhere.
Drag-drop step order
The two capture steps (ID card front/back and selfies) can be reordered by drag-and-drop from Pay4All AGE > Paramètres > Documents à demander > Ordre d'affichage. The chosen order applies to both Pay4All Shop and WooCommerce checkouts.
WooCommerce support
The WooCommerce integration (product-level "Requires age verification" checkbox, QR-code checkout panel, order-screen photo viewer) is provided by the paid Pay4All Pro add-on, distributed through pay4all.ch. Pay4All Age itself remains free ; Pay4All Pro simply wires it into WooCommerce.
How it works
- Merchant ticks Requires age verification on any product edit screen (Pay4All Shop product).
- When a customer adds such a product to their form, a panel appears in the KYC step showing a QR code.
- Customer scans the QR with their phone -> the mobile capture page opens -> they take the required photos with their phone camera.
- The desktop form polls the server every 4 seconds and unlocks automatically when every required slot is filled — no page refresh needed.
- On order submit, the encrypted photos are moved from the session bucket to the order-scoped bucket, and are only decrypted on demand by an admin 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.
更新日志:
- 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.