SIMPLYPAYE MOBILE MONEY GATEWAY
SimplyPaye Mobile Money Gateway compatibility with REEID Translate
SimplyPaye Mobile Money Gateway compatibility with REEID Translate is being evaluated from available plugin evidence. Adds Orange Money, Airtel Money, M-Pesa and Visa card payments for online stores in the Democratic Republic of the Congo. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for SimplyPaye Mobile Money Gateway.
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
SimplyPaye Mobile Money Gateway is documented in the WooCommerce category with 6 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 SimplyPaye Mobile Money Gateway 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
- Adds Orange Money, Airtel Money, M-Pesa and Visa card payments for online stores in the Democratic Republic of the Congo.
- Provides a checkout choice between “Mobile Money” (USSD push on their phone) and “Visa card” (secure redirect).
- Integrates with SimplyPaye by sending payment-related data to SimplyPaye when a store owner configures the gateway and when a customer initiates or checks a payment.
- Requires the e-commerce plugin dependency listed in the “Requires Plugins” header (WooCommerce).
- Provides a setup flow via “Settings → Payments → SimplyPaye” where a merchant code is entered (and an optional API key is recommended for new accounts).
- Connects to the SimplyPaye Payment API endpoint “https://api-simply-pay.net” (configurable in gateway settings; default shown above).
CONTENT BOUNDARY
SimplyPaye Mobile Money Gateway 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
SimplyPaye Mobile Money Gateway and REEID Translate FAQ.
What does SimplyPaye Mobile Money Gateway do according to the available plugin evidence?
SimplyPaye Mobile Money Gateway has 6 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 SimplyPaye Mobile Money Gateway?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for SimplyPaye Mobile Money Gateway?
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 SimplyPaye Mobile Money Gateway in a multilingual WordPress workflow.
REEID documents SimplyPaye Mobile Money Gateway 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.