PAY4ALL FOR MYPOS
Pay4All for myPOS – For WooCommerce & Pay4All Shop compatibility with REEID Translate
Pay4All for myPOS – For WooCommerce & Pay4All Shop compatibility with REEID Translate is being reviewed using official plugin documentation. Adds “myPOS Virtual” as a payment gateway to WooCommerce and the free “Pay4All Shop” plugin. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Pay4All for myPOS – For WooCommerce & Pay4All Shop does
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Pay4All for myPOS – For WooCommerce & Pay4All Shop is documented in the WooCommerce category with 8 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Pay4All for myPOS – For WooCommerce & Pay4All Shop compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Adds “myPOS Virtual” as a payment gateway to WooCommerce and the free “Pay4All Shop” plugin.
- Connects to myPOS by pasting a “Configuration Pack” (base64 blob) from the myPOS merchant portal.
- Displays enabled myPOS payment methods at checkout, including “cards”, “iDEAL”, “TWINT”, “IRIS”, “Satispay”, and more.
- Supports WooCommerce checkout experiences including “classic checkout”, “Checkout Blocks” and “HPOS”.
- Triggers refunds directly from the WooCommerce order screen using the “native WC refund flow”.
- Provides a “Test / Live mode toggle” with “locked Test mode when no production Pack is saved”.
- Localizes the plugin in “French, German, Italian and English”.
- Sends transaction data to https://mypos.com/vmp/checkout (production) or https://mypos.com/vmp/checkout-test (test mode) when a customer places an order and selects myPOS at checkout.
TRANSLATION BOUNDARY
Pay4All for myPOS – For WooCommerce & Pay4All Shop capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- No visitor-facing translation surface was established for this integration.
FREQUENTLY ASKED QUESTIONS
Pay4All for myPOS – For WooCommerce & Pay4All Shop and REEID Translate FAQ.
What does Pay4All for myPOS – For WooCommerce & Pay4All Shop do?
Pay4All for myPOS – For WooCommerce & Pay4All Shop has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does Pay4All for myPOS – For WooCommerce & Pay4All Shop have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Pay4All for myPOS – For WooCommerce & Pay4All Shop?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Pay4All for myPOS – For WooCommerce & Pay4All Shop in a multilingual WordPress workflow.
REEID documents Pay4All for myPOS – For WooCommerce & Pay4All Shop functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.