PAY4ALL AGE VERIFICATION
Pay4All Age Verification – For WooCommerce & Pay4All Shop translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Pay4All Age Verification – For WooCommerce & Pay4All Shop does, but does not yet establish specific visitor-facing content values that REEID should translate.
Visit Pay4All Age Verification – For WooCommerce & Pay4All Shop ↗
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- WooCommerce age-gating trigger: adds a QR-code-based age verification panel during checkout when a product is marked with a “Requires age verification” option; customer verification status is viewable on the order.
- Identity capture workflow: requires a 5-second video selfie and/or valid proof of identity (front/back document photos) captured via a smartphone flow initiated by scanning a QR code.
- Local-only processing and storage: photo/video capture, encryption, storage, and admin decryption are performed on the site; the plugin states it does not connect to any external service.
- Encryption at rest for captured media: encrypts photos/videos using AES-256-GCM with a per-order (or per-user) subkey derived via HMAC-SHA256 from a master key; ciphertexts are stored in a private folder guarded to prevent web serving.
- Admin-only decryption access control: the admin decryption endpoint is nonce-protected and requires the `edit_users` capability.
- Data lifecycle controls: encrypted media are auto-purged when an order or user is permanently deleted; a daily cron purges session-scoped buckets older than a configured TTL (default 24h).
- WPML/Polylang compatibility behavior for age restriction: when the age-restricted flag is set on a source product, translations are treated as age-restricted as well (even if the flag is not mirrored).
Distinctive features
WooCommerce age-gating trigger: adds a QR-code-based age verification panel during checkout when a product is marked with a “Requires age verification” option; customer verification status is viewable on the order. Identity capture workflow: requires a 5-second video selfie and/or valid proof of identity (front/back document photos) captured via a smartphone flow initiated by scanning a QR code. Local-only processing and storage: photo/video capture, encryption, storage, and admin decryption are performed on the site; the plugin states it does not connect to any external service. Encryption at rest for captured media: encrypts photos/videos using AES-256-GCM with a per-order (or per-user) subkey derived via HMAC-SHA256 from a master key; ciphertexts are stored in a private folder guarded to prevent web serving. Admin-only decryption access control: the admin decryption endpoint is nonce-protected and requires the `edit_users` capability. Data lifecycle controls: encrypted media are auto-purged when an order or user is permanently deleted; a daily cron purges session-scoped buckets older than a configured TTL (default 24h). WPML/Polylang compatibility behavior for age restriction: when the age-restricted flag is set on a source product, translations are treated as age-restricted as well (even if the flag is not mirrored).
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Pay4All Age Verification – For WooCommerce & Pay4All Shop does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Pay4All Age Verification – For WooCommerce & Pay4All Shop and REEID Translate FAQ.
Does the current evidence establish translation scope for Pay4All Age Verification – For WooCommerce & Pay4All Shop?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.