WEBHOSTING4U SECURE CARD GATEWAY FOR EPAY PAYCENTER (PIRAEUS BANK)
WebHosting4U Secure Card Gateway for ePay Paycenter (Piraeus Bank) translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what WebHosting4U Secure Card Gateway for ePay Paycenter (Piraeus Bank) does, but does not yet establish specific visitor-facing content values that REEID should translate.
Visit WebHosting4U Secure Card Gateway for ePay Paycenter (Piraeus Bank) ↗
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- WooCommerce payment gateway integration that performs ePay Paycenter redirection using a SOAP ticketing call (IssueNewTicket) and an auto-submitted HTML form POST to the bank-hosted pay.aspx page so card data does not transit the merchant server.
- Callback handling includes full HMAC-SHA256 HashKey verification for successful responses before marking an order as paid; mismatching HashKey results in the order being set to “On hold” with a logged notice.
- Supports hosted payment callbacks via WooCommerce WC-API endpoint (wc-api=epay_paycenter) and uses merchant-configured success/failure/backlink URLs for the bank’s return flow.
- Includes an admin diagnostic (“Test callback URL”) that sends a synthetic declined-transaction-shaped POST to the plugin’s callback URL via loopback to detect whether a host web-application firewall blocks the callback before PHP runs.
- Cloudflare-aware admin behavior: detects Cloudflare via request headers and displays Cloudflare IPv4 CIDR ranges (fetched from cloudflare.com/ips-v4 and cached in a transient) for use in whitelisting payment callbacks.
- Claims HPOS-native operation by using WooCommerce HPOS-aware order metadata APIs ($order->update_meta_data()/get_meta()) rather than legacy post meta functions, preserving transaction/support identifiers across storage modes.
- States it does not load analytics/telemetry/fingerprinting code, does not set cookies on visitor browsers, and only performs strictly transactional outbound requests to the ePay Paycenter endpoints and Cloudflare IP list in the admin context.
Distinctive features
WooCommerce payment gateway integration that performs ePay Paycenter redirection using a SOAP ticketing call (IssueNewTicket) and an auto-submitted HTML form POST to the bank-hosted pay.aspx page so card data does not transit the merchant server. Callback handling includes full HMAC-SHA256 HashKey verification for successful responses before marking an order as paid; mismatching HashKey results in the order being set to “On hold” with a logged notice. Supports hosted payment callbacks via WooCommerce WC-API endpoint (wc-api=epay_paycenter) and uses merchant-configured success/failure/backlink URLs for the bank’s return flow. Includes an admin diagnostic (“Test callback URL”) that sends a synthetic declined-transaction-shaped POST to the plugin’s callback URL via loopback to detect whether a host web-application firewall blocks the callback before PHP runs. Cloudflare-aware admin behavior: detects Cloudflare via request headers and displays Cloudflare IPv4 CIDR ranges (fetched from cloudflare.com/ips-v4 and cached in a transient) for use in whitelisting payment callbacks. Claims HPOS-native operation by using WooCommerce HPOS-aware order metadata APIs ($order->update_meta_data()/get_meta()) rather than legacy post meta functions, preserving transaction/support identifiers across storage modes. States it does not load analytics/telemetry/fingerprinting code, does not set cookies on visitor browsers, and only performs strictly transactional outbound requests to the ePay Paycenter endpoints and Cloudflare IP list in the admin context.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what WebHosting4U Secure Card Gateway for ePay Paycenter (Piraeus Bank) does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
WebHosting4U Secure Card Gateway for ePay Paycenter (Piraeus Bank) and REEID Translate FAQ.
Does the current evidence establish translation scope for WebHosting4U Secure Card Gateway for ePay Paycenter (Piraeus Bank)?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.