WPXPERT PAYMENT GATEWAY FOR SIMPLEPAY
WPXpert Payment Gateway for SimplePay compatibility with REEID Translate
WPXpert Payment Gateway for SimplePay compatibility with REEID Translate is being evaluated from available plugin evidence. Provides a SimplePay (OTP Mobil) card payment gateway for WooCommerce stores. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for WPXpert Payment Gateway for SimplePay.
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
WPXpert Payment Gateway for SimplePay is documented in the WooCommerce category with 8 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 WPXpert Payment Gateway for SimplePay 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 a SimplePay (OTP Mobil) card payment gateway for WooCommerce stores.
- Sends customers to the SimplePay hosted payment page; card details never reach the shop and are never stored there.
- Supports sandbox and live systems, with test mode on activation.
- Uses separate merchant accounts per currency (HUF, EUR, USD) and selects the merchant account based on the order currency.
- Marks orders as paid via IPN after receiving, authenticating, and properly acknowledging the IPN.
- Supports full and partial refunds from the WooCommerce refund flow.
- Provides manual transaction status query from the order screen.
- Displays the mandatory data transfer statement at checkout, with the configured company details.
CONTENT BOUNDARY
WPXpert Payment Gateway for SimplePay 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
WPXpert Payment Gateway for SimplePay and REEID Translate FAQ.
What does WPXpert Payment Gateway for SimplePay do according to the available plugin evidence?
WPXpert Payment Gateway for SimplePay has 8 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 WPXpert Payment Gateway for SimplePay?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for WPXpert Payment Gateway for SimplePay?
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 WPXpert Payment Gateway for SimplePay in a multilingual WordPress workflow.
REEID documents WPXpert Payment Gateway for SimplePay 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.