URBO PAYMENT INITIATION SERVICE (PIS) FOR WOOCOMMERCE
URBO Payment Initiation Service (PIS) for WooCommerce compatibility with REEID Translate
URBO Payment Initiation Service (PIS) for WooCommerce compatibility with REEID Translate is being reviewed using official plugin documentation. Accept direct bank payments in a WooCommerce store using URBO Payment Initiation Service (PIS). No specific text shown to visitors is currently confirmed for translation.
Visit URBO Payment Initiation Service (PIS) for WooCommerce ↗
AWAITING VERIFICATION
What URBO Payment Initiation Service (PIS) for WooCommerce 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
URBO Payment Initiation Service (PIS) for WooCommerce is documented in the WooCommerce category with 6 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 URBO Payment Initiation Service (PIS) for WooCommerce 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
- Accept direct bank payments in a WooCommerce store using URBO Payment Initiation Service (PIS).
- Connects to the URBO Payment Initiation Service (PIS) API at mip.urbo.lt to initiate and track bank payments.
- Sends order data (including order reference, order total, currency, country, locale, return URL, optional webhook URL, and billing email) to the API to create a payment.
- Uses webhooks to receive payment status notifications and automatically update order status.
- Provides sandbox and production environments for payment processing.
- Supports WooCommerce Blocks checkout and is HPOS (High-Performance Order Storage) compatible.
TRANSLATION BOUNDARY
URBO Payment Initiation Service (PIS) for WooCommerce 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
URBO Payment Initiation Service (PIS) for WooCommerce and REEID Translate FAQ.
What does URBO Payment Initiation Service (PIS) for WooCommerce do?
URBO Payment Initiation Service (PIS) for WooCommerce has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does URBO Payment Initiation Service (PIS) for WooCommerce 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 URBO Payment Initiation Service (PIS) for WooCommerce?
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 URBO Payment Initiation Service (PIS) for WooCommerce in a multilingual WordPress workflow.
REEID documents URBO Payment Initiation Service (PIS) for WooCommerce 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.