DIDIT VERIFY
Didit Verify compatibility with REEID Translate
Didit Verify compatibility with REEID Translate is being evaluated from available plugin evidence. Provides membership-style access control via a `[didit_gate]` shortcode that restricts wrapped content to verified users and shows an unverified message plus a verification button. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Didit Verify.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Didit Verify is documented in the Membership category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Didit Verify compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Provides membership-style access control via a `[didit_gate]` shortcode that restricts wrapped content to verified users and shows an unverified message plus a verification button.
- Exposes verification state to users and templates via a `[didit_status]` shortcode (e.g., “Identity Verified” vs “Not Verified”) with configurable label text.
- Persists verification results in WordPress user meta (e.g., `_didit_verified` and `_didit_status`) and makes the status visible in the WordPress admin Users list.
- Supports WooCommerce checkout gating for identity verification, including configurable checkout placement (4 position options) and product-scope rules (all products, only selected products, or all except selected).
- Sends verification session/billing data to the Didit service for pre-filling and cross-validation, and stores the verification session ID in WooCommerce order meta for audit.
- Supports multiple frontend display modes for the verification UI (Modal overlay or Embedded inline rendering) and allows per-shortcode overrides for display mode and button text/success text.
- Implements developer extensibility for membership/verification workflows via WordPress actions (`didit_session_created`, `didit_verification_completed`, `didit_verification_cancelled`) and a frontend `didit:complete` DOM CustomEvent.
CONTENT BOUNDARY
Didit Verify capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Didit Verify and REEID Translate FAQ.
What does Didit Verify do according to the available plugin evidence?
Didit Verify has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Didit Verify?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Didit Verify?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Didit Verify in a multilingual WordPress workflow.
REEID documents Didit Verify functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.