THEMEPRIME MANUALPAY FOR WOOCOMMERCE
ThemePrime ManualPay for WooCommerce compatibility with REEID Translate
ThemePrime ManualPay for WooCommerce compatibility with REEID Translate is being evaluated from available plugin evidence. Create up to 20 fully independent custom manual payment gateways for WooCommerce. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for ThemePrime ManualPay for WooCommerce.
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
ThemePrime ManualPay for WooCommerce is documented in the WooCommerce 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 ThemePrime ManualPay for WooCommerce 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
- Create up to 20 fully independent custom manual payment gateways for WooCommerce.
- Add per-gateway payment instructions with account numbers/wallet IDs and one-click copy.
- Support per-gateway QR codes and custom checkout fields (including transaction IDs/reference numbers).
- Allow customers to upload a payment slip (receipt image or PDF) at checkout.
- Apply per-gateway transaction fees and conditional logic (cart total range and customer user role).
- Automatically cancel unpaid orders via order auto-expiry and restore stock.
- Provide an admin workflow to verify or reject payments and notify the customer by email.
CONTENT BOUNDARY
ThemePrime ManualPay for WooCommerce 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
- No visitor-facing translation surface was established for this integration.
COMMON QUESTIONS
ThemePrime ManualPay for WooCommerce and REEID Translate FAQ.
What does ThemePrime ManualPay for WooCommerce do according to the available plugin evidence?
ThemePrime ManualPay for WooCommerce 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 ThemePrime ManualPay for WooCommerce?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for ThemePrime ManualPay for WooCommerce?
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 ThemePrime ManualPay for WooCommerce in a multilingual WordPress workflow.
REEID documents ThemePrime ManualPay for WooCommerce 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.