WebHosting4U Secure Card Gateway for ePay Paycenter (Piraeus Bank)

By webhosting4ugr

50+ active installationsVersion 1.0.41

Independent WooCommerce gateway by WebHosting4U for the ePay Paycenter (Piraeus Bank / Euronet Merchant Services) Redirection service.

Description

What sets this plugin apart

  • HPOS-native from day one. Built against WooCommerce’s High-Performance Order Storage from the very first release. All order metadata uses the HPOS-aware $order->update_meta_data() / get_meta() API — never the legacy update_post_meta() / get_post_meta() calls that silently fail on HPOS-enabled stores (the WooCommerce default for new installs since 8.x). Your transaction IDs, support reference IDs, and approval codes are preserved whichever storage mode you run.

  • Cloudflare-aware. Automatically detects when your store is served through Cloudflare (via the CF-Ray / CF-Connecting-IP request headers) and surfaces the current Cloudflare IPv4 CIDR ranges right in the gateway settings page, ready to copy. You hand them to Euronet Merchant Services so the bank’s callbacks are not blocked at their firewall when they arrive via Cloudflare edge IPs. Live list fetched from cloudflare.com/ips-v4 and cached for 12 hours.

  • Built-in WAF / callback self-test. A diagnostic button in the gateway settings sends a realistic, declined-transaction-shaped POST to your own callback URL via loopback and reports whether your host’s web-application firewall (cPFence, ModSecurity / OWASP CRS, Imunify360, BitNinja, LiteSpeed WAF) silently blocks it before PHP runs. No real order is created or modified — the synthetic payload carries a WAFTEST- merchant reference that cannot match any order in the database. Catches the class of “callbacks never arrive” problems before they cost you a sale.

  • Modern admin UI. Card-based layout, dashicons throughout, one-click Copy-to-clipboard for all callback URLs grouped in a single block, environment badge (Test / Live / Production) on the credentials section, collapsible Cloudflare details. Audited against the “Modern” admin theme introduced in WordPress 7.0.

  • Audited for WordPress 7.1 on release day. Reviewed against the full breaking-changes list in the WordPress 7.0 Field Guide on 2026-05-20 and again in the WordPress 7.1 Field Guide on 2026-08-28. “Tested up to” has tracked the current WordPress release since the very first stable version. The plugin requires PHP 7.4 (the WordPress 7.1 minimum) and uses no API deprecated in 7.0 or 7.1.

  • Fully bilingual (EN + EL). All 179 admin and customer-facing strings translated to Greek and shipped as both classic .mo and WordPress 6.5+ performant .l10n.php payloads. The wp.org page itself ships with an English readme.txt that opens with a Greek summary, plus a parallel full Greek readme-el.txt companion file inside the plugin folder for Greek-speaking merchants.

Ελληνικά:

Ανεξάρτητο πρόσθετο πύλης πληρωμής WooCommerce από τη WebHosting4U για
την υπηρεσία ePay Paycenter Redirection της Τράπεζας Πειραιώς /
Euronet Merchant Services. Υλοποιεί πλήρως την επίσημη προδιαγραφή
Redirection v3.1:

  • Έκδοση μοναδικού εισιτηρίου (TranTicket) μέσω SOAP Ticketing Web
    Service με κωδικοποίηση UTF-8.
  • Αυτόματη ανακατεύθυνση POST στην ασφαλή σελίδα πληρωμής της τράπεζας
    (pay.aspx) — τα δεδομένα κάρτας δεν περνούν ποτέ από τον διακομιστή
    του καταστήματος.
  • Πλήρης επαλήθευση HashKey HMAC-SHA256 σε κάθε επιτυχημένη απάντηση
    πριν χαρακτηριστεί η παραγγελία ως εξοφλημένη.
  • Συναλλαγές Sale (άμεση εκκαθάριση στην επόμενη παρτίδα).
  • Υποστήριξη IRIS Payments (άμεσες πληρωμές μέσω ΔΙΑΣ). Όταν η
    Euronet Merchant Services ενεργοποιήσει το IRIS στη σύμβασή σας, η
    σελίδα πληρωμής της τράπεζας εμφανίζει στον πελάτη και τις δύο
    επιλογές (κάρτα ή IRIS). Το πρόσθετο αναγνωρίζει τις απαντήσεις IRIS,
    αποθηκεύει το κανάλι πληρωμής στην παραγγελία, και εμφανίζει
    μηνύματα προσαρμοσμένα στα IRIS σενάρια (ακύρωση από την εφαρμογή
    τράπεζας, λήξη QR 5 λεπτών, σφάλμα υπηρεσίας IRIS κ.λπ.).
  • Πληρωμές Google Pay™ (Redirection v3.1) — γίνονται δεκτές
    αυτόματα, χωρίς καμία ρύθμιση. Η σελίδα της τράπεζας εμφανίζει το
    Google Pay σε συμβατές συσκευές για συναλλαγές αγοράς και προέγκρισης.
    Επειδή το Google Pay επιστρέφει την τυπική απάντηση κάρτας,
    επαληθεύεται με το ίδιο HashKey HMAC-SHA256· το πρόσθετο καταγράφει
    επιπλέον το πεδίο PanCardType (FPAN πραγματικός αριθμός κάρτας /
    DPAN token συσκευής) στην παραγγελία.
  • Συμπλήρωση πεδίων 3-D Secure από τη διεύθυνση χρέωσης / αποστολής
    του WooCommerce.
  • Συμβατότητα με HPOS (Custom Order Tables) και WooCommerce Blocks
    checkout.

Προϋπόθεση: πρέπει να έχετε υπογεγραμμένο συμβόλαιο αποδοχής με την
Euronet Merchant Services / Τράπεζα Πειραιώς και να διαθέτετε τα
διαπιστευτήρια AcquirerId, MerchantId, PosId, Username,
Password. Το πρόσθετο δεν παρέχει δικούς του δοκιμαστικούς
λογαριασμούς.

Η πλήρης ελληνική μετάφραση της σελίδας του προσθέτου στο WordPress.org
θα είναι διαθέσιμη μέσω του translate.wordpress.org
μόλις εγκριθεί από την κοινότητα. Δείτε επίσης το συνοδευτικό
readme-el.txt για την ολοκληρωμένη ελληνική τεκμηρίωση.

English:

This plugin integrates WooCommerce with the ePay Paycenter Redirection
service operated by Piraeus Bank / Euronet Merchant Services. It implements
the official Redirection v3.1 specification end to end:

  • SOAP Ticketing Web Service (IssueNewTicket) with UTF-8 payload.
  • Auto-submitted HTML form POST redirection to the Paycenter secure
    payment page (pay.aspx) so card data never touches your server.
  • Full HMAC-SHA256 HashKey verification for every successful callback
    before marking an order as paid.
  • Sale transactions, settled in the next batch with no further merchant
    action required.
  • IRIS payments (Greek instant payment / DIAS) accepted transparently
    when enabled by Euronet Merchant Services on the merchant agreement.
    The bank’s hosted page presents card and IRIS as the two payment
    options; the plugin recognises the IRIS-specific response payload
    (CardType=15, PaymentMethod=IRIS), surfaces IRIS-tailored decline
    messages for the IRIS-only ResponseCodes (05 user-cancelled-in-bank-app,
    06 service error, 09 pending, 68 5-minute QR timeout, 70 IRIS service
    error) and records the channel on the order so card vs IRIS settlements
    are distinguishable in your reports.
  • Google Pay™ (Redirection v3.1) accepted automatically — no
    configuration needed. The bank’s hosted page shows Google Pay on
    eligible devices/browsers for purchase and pre-authorization
    transactions (with or without installments). Because Google Pay
    returns the standard card success payload, it is verified against the
    same HMAC-SHA256 HashKey as any card; the plugin additionally records
    the PanCardType (FPAN real card number / DPAN device token) on the
    order and notes “Paid via Google Pay” so wallet settlements are
    distinguishable in your reports.
  • 3-D Secure auxiliary fields populated from the WooCommerce billing /
    shipping address.
  • HPOS (Custom Order Tables) and WooCommerce Blocks checkout support.

You must have signed an acquiring contract with Euronet Merchant
Services / Piraeus Bank and obtained AcquirerId, MerchantId, PosId,
Username and Password credentials before using this plugin.
The
plugin does not provide test or sandbox accounts on its own; please
contact Euronet Merchant Services to request one.

Affiliation and trademark notice

This plugin is independent software published by WebHosting4U and is
not affiliated with, endorsed by, sponsored by, or otherwise officially
connected to
Piraeus Bank S.A., Euronet Merchant Services, or
Automattic Inc. The third-party names “ePay”, “Paycenter”, “Piraeus Bank”
and “WooCommerce” are trademarks of their respective owners and are
used here in good faith, after the unaffiliation marker “for”, solely
to describe the third-party service this plugin integrates with, in
line with the WordPress.org Detailed Plugin Guidelines on third-party
trademarks. The bundled accepted card brands image
(assets/img/wp-cards.png) is included with the rights-holder’s
authorization for the merchant distribution scope of this plugin.

User tracking and consent

This plugin does not load any analytics, telemetry, advertising,
fingerprinting, profiling or behavioural tracking code, neither on the
storefront nor in the WordPress admin. It does not set cookies on
visitor browsers, does not contact any first-party or third-party
analytics endpoint, and does not collect aggregated or individual
usage statistics from the merchant’s installation. The only outbound
network traffic the plugin generates is the strictly transactional
traffic documented in the External services section below, which
is required to complete a payment the merchant has explicitly
configured the plugin to perform. No user-tracking consent prompt is
therefore required by this plugin (Plugin Review Team Guidelines 7
and 9).

External services

This plugin reaches out to three external services. Two are operated
by Euronet Merchant Services on behalf of Piraeus Bank S.A. for the
“ePay Paycenter” payment redirection product (mandatory for the
plugin’s core function). The third is a publicly available Cloudflare
endpoint used only in the admin panel to help store owners configure
firewall rules for payment callbacks.

1. ePay Paycenter Ticketing Web Service

  • What it is: a SOAP / ASMX endpoint published by Euronet Merchant
    Services that issues a single-use TranTicket for each card
    payment attempt. The ticket is kept server-side only (never exposed
    to the browser) and used solely to verify the HMAC-SHA256 HashKey on
    the bank’s callback; the customer’s browser is redirected to the
    secure payment page by a form carrying only non-secret fields, so
    cardholder data never touches the merchant server.
  • Endpoint: https://paycenter.piraeusbank.gr/services/tickets/issuer.asmx
  • What is sent: the merchant credentials provided by Euronet Merchant
    Services (AcquirerId, MerchantId, PosId, Username and an MD5 hash
    of the Password), the order’s MerchantReference (numeric WooCommerce
    order id with a short random suffix), the transaction amount and
    ISO 4217 numeric currency code, the request type (always Sale),
    and the 3-D Secure auxiliary fields populated
    from the WooCommerce order: billing email, cardholder name,
    billing address (city / lines / post code / state / ISO 3166
    numeric country code), shipping address when present, and the
    customer’s mobile phone number formatted as CC-Number. No
    cardholder data, no PAN, no CVV, no expiry, and no analytics
    identifier is ever transmitted; cardholder data is collected
    exclusively on the bank’s secure payment page.
  • When it is sent: once per successful checkout submission, at the
    moment WooCommerce hands control to the gateway’s
    Pay for order page, immediately before the customer is
    auto-redirected to the bank.

2. ePay Paycenter Redirection page

  • What it is: the bank-hosted secure payment page where the customer
    enters card details and completes the 3-D Secure challenge. The
    plugin renders an auto-submitted HTML form whose action attribute
    is the URL below.
  • Endpoint: https://paycenter.piraeusbank.gr/redirection/pay.aspx
  • What is sent: the merchant identifiers (AcquirerId, MerchantId,
    PosId, User), the language code, the MerchantReference issued
    during ticketing, and a per-order ParamBackLink so the bank’s
    Cancel button returns the customer to the correct WordPress
    endpoint. The TranTicket itself is read by the customer’s
    browser from the hidden form field; the merchant server is not
    the originator of the redirect POST.
  • When it is sent: once per checkout, immediately after the
    Ticketing call above succeeds.
  • Inbound counterpart: Paycenter posts a signed transaction
    response (HMAC-SHA256 HashKey) back to the plugin’s WC-API
    callback URL on the merchant site
    (https://<merchant-site>/?wc-api=epay_paycenter). This is the
    same service – the merchant site is the Notification / Success /
    Failure / Backlink target the merchant configures in the
    Euronet portal. No data leaves the merchant server on this
    inbound leg; the plugin only reads, verifies, and acts on the
    response.

Service operator and legal links

Both endpoints above are operated by Euronet Merchant Services
(epay) for Piraeus Bank S.A.. Before activating the gateway,
merchants must review and agree to the operator’s terms and
privacy policy:

If any of the above URLs change after publication, please consult
the live operator websites for the current version of the relevant
document. The plugin’s behaviour is not affected by such updates
because the operator’s terms apply to the merchant’s relationship
with Euronet Merchant Services / Piraeus Bank, not to the plugin
itself. Merchants remain responsible for keeping their own
privacy policy and terms aligned with the data flows documented
above (notably the transmission of billing / shipping address
fields and customer email / phone to the bank for 3-D Secure
authentication).

3. Cloudflare IPv4 list

  • What it is: a publicly available plain-text file published by
    Cloudflare, Inc. that lists the current IPv4 CIDR ranges used by
    Cloudflare’s edge network. The plugin fetches this file once every
    12 hours (or 15 minutes on failure) via wp_safe_remote_get() and
    caches the result in a WordPress transient.
  • Endpoint: https://www.cloudflare.com/ips-v4/
  • What is sent: a standard HTTP GET request with no personal data,
    no order information, no credentials, and no cookies. The only
    identifying information in the request is the plugin’s User-Agent
    string (secure-card-gateway-for-epay-paycenter-piraeus-bank/VERSION).
  • Why: when the plugin’s admin settings page detects that the
    WordPress site is served through Cloudflare (via the CF-Ray /
    CF-Connecting-IP / CDN-Loop request headers), it displays the
    current Cloudflare IPv4 ranges so the store owner can copy them
    into an email to Euronet Merchant Services to whitelist them for
    payment callbacks. Without this list, callbacks routed through
    Cloudflare edge IPs may be rejected by the bank’s firewall.
  • When: only when an administrator views the gateway’s WooCommerce
    settings page and Cloudflare is detected on the incoming request.
    It is never triggered on the storefront or by guest/customer visits.
  • Cloudflare service homepage: https://www.cloudflare.com/
  • Cloudflare Privacy Policy: https://www.cloudflare.com/privacypolicy/
  • Cloudflare Terms of Service: https://www.cloudflare.com/terms/

No data is sent to any third party other than the three endpoints
listed above.

Installation

  1. Upload the plugin ZIP through Plugins → Add New → Upload Plugin,
    or extract it into wp-content/plugins/wh4u-secure-card-gateway-for-epay-paycenter-piraeus-bank/.
  2. Activate the plugin.
  3. Go to WooCommerce → Settings → Payments and enable
    ePay Paycenter (Piraeus Bank).
  4. Enter your AcquirerId, MerchantId, PosId, Username and Password
    exactly as provided by Euronet Merchant Services.
  5. Set the environment (Test / Live), language, and transaction type.
  6. Provide Euronet Merchant Services with the following URLs for your
    merchant record:
    • Referrer URL: your shop checkout page.
    • Success URL: https://your-site.tld/wc-api/epay_paycenter/
    • Failure URL: https://your-site.tld/wc-api/epay_paycenter/
    • Backlink URL: https://your-site.tld/wc-api/epay_paycenter/
    • IP address: the outbound IP of your web server.
    • Response method: POST (recommended).
  7. Execute the mandatory test cases documented in Section 7 of the
    Redirection v2.9 manual before requesting live credentials.

FAQ

Which cards are supported?

Visa, Mastercard, Maestro, and (subject to agreement with Euronet
Merchant Services) Diners / Discover and American Express.

Does the plugin support IRIS payments?

Yes. When IRIS is enabled on your merchant agreement by Euronet Merchant
Services, customers can choose between card and IRIS directly on the
bank’s hosted payment page — the plugin does not need a separate setting
to “turn IRIS on” because the choice is made server-side at the bank,
not in your checkout. The plugin recognises IRIS responses (CardType=15
or PaymentMethod=IRIS in the bank’s HMAC-verified callback), shows
IRIS-tailored messages for the IRIS-only decline scenarios (user
cancelled in their banking app, 5-minute QR timeout, IRIS service error,
etc.) and records the payment channel on the order so card and IRIS
transactions are distinguishable in your reports.

Per Piraeus Bank policy, IRIS payments do not support installments
(the full amount is charged) and refunds are not supported for IRIS
transactions
(ResponseCode 9167). These restrictions are enforced by
the bank, not by the plugin.

Does the plugin store any card data?

No. Cardholder data is entered exclusively on the Paycenter secure
payment page and never transits your server. The plugin stores only
non-sensitive metadata such as approval code, response code and
SupportReferenceID for reconciliation.

What happens if the HashKey cannot be verified?

The order is set to On hold and a notice is logged. Verification is
mandatory before an order is marked paid; a mismatching HashKey is
treated as a potentially forged callback.

Is this plugin GDPR-compatible?

The plugin transmits only the minimum data required for the transaction
(order total, currency, merchant reference, and 3-D Secure auxiliary
fields such as billing email and address). No analytics or telemetry is
collected.

My host’s WAF (cPFence, ModSecurity, Imunify360, BitNinja, LiteSpeed) is blocking the bank callback. What do I do?

Shared-hosting firewalls sometimes flag Paycenter’s decline-callback
payload because it contains patterns (dash-only TransactionDateTime,
empty HashKey on declined transactions, Greek ResponseDescription
text) that overlap with default attack signatures. Symptoms: callbacks
for failed transactions never arrive and orders get stuck in pending
payment
.

The plugin’s settings page includes a Test callback URL diagnostic
that POSTs a realistic declined-transaction payload to your own callback
URL via loopback and reports whether a host WAF intercepts it. Run it
once before going live. If a WAF is intercepting, ask your hosting
provider to whitelist the URL /?wc-api=epay_paycenter (callback-URL
scope only — never disable rules server-wide). CDN-level WAFs
(Cloudflare, Sucuri, Akamai) must be configured separately at the CDN —
the in-admin diagnostic only exercises the origin server’s WAF.

My customer sees only “-1” after the bank return. What happened?

The literal -1 comes from WooCommerce core’s WC_API handler. For
this plugin it usually means one of three things:

  1. The callback URL in the Euronet portal does not match the plugin’s
    URL. Use exactly https://<your-site>/?wc-api=epay_paycenter (no
    trailing slash, no extra path). Copy it from the gateway settings
    page where the plugin displays the canonical form.
  2. A host WAF intercepted the callback before it reached PHP (see the
    WAF FAQ above).
  3. The plugin handled the callback but a downstream redirect target
    suppressed the notice. Since 1.0.14 decline messages survive
    cross-origin redirect cookie stripping, so this is rare on current
    versions.

Check WooCommerce → Status → Logs for epay-paycenter-* entries
around the transaction timestamp. The Callback envelope INFO line is
written on every callback that reaches PHP, so its presence or absence
distinguishes WAF-level blocks from plugin-level rejects.

Where do I report security bugs found in this plugin?

Please report security bugs found in the source code of the Secure Card
Gateway for ePay Paycenter (Piraeus Bank) plugin through the Patchstack
Vulnerability Disclosure Program
.
The Patchstack team will assist you with verification, CVE assignment, and
notify the developers of this plugin.

Screenshots

Changelog

1.0.41

Two corrections that follow from answers Euronet Merchant Services gave on 16 November 2026 about the follow-up call added in 1.0.40. The order note written for a payment the bank refused no longer claims the payment never happened, and the question is now put to the bank with the right Acquirer ID on the first attempt. Also declares compatibility with current WooCommerce. No configuration change required, and nothing about when or whether an order is marked paid has changed.
* Fix: an order note about a refused card no longer says the payment was never completed. When the hourly check asks the bank about a payment it cannot account for, the answer comes back in one of two forms that 1.0.40 treated as the same thing: either the bank holds no completed transaction for that attempt, which is the customer who closed the tab, or it holds one and refused it, which is the card that was declined. Euronet has now confirmed which is which, namely that a transaction that completed returns its result either way and the “no transaction” code means specifically that the attempt was never finished. The note left on the order read “this payment was never completed” in both cases, which about a declined card is untrue, and that note is what anyone reading the order a year later will go by. A refused payment now reads that the bank processed it and did not approve it, with the suggestion that the customer try again, and with another card if the same one is refused. Nothing the plugin does changes: both answers still mean no money was taken, both still leave the order unpaid, and neither has ever been able to mark an order paid. Only the sentence was wrong. In practice this is reached for an order that was flagged for checking, whose payment then completed and was refused, and whose result was lost on the way back, so most stores will never see either note; it is fixed because it is the one place where the plugin stated something false about a payment in a permanent record.
* Improved: the follow-up question now reaches the bank on the first attempt on every store. 1.0.40 did not know whether the Acquirer ID this particular call takes is the same for every merchant or derived from each merchant’s own account, so it sent a value derived from the account first, fell back to the one Euronet had supplied, and remembered whichever was accepted. Euronet has now confirmed it is the same value for every epay eCommerce merchant, so the derivation and the fallback are gone and the first request is the correct one. A store whose Acquirer ID is 14 never saw a difference, because both values were identical there. A store on any other Acquirer ID made one request that was always going to be rejected, once, on its first lookup, and that request is no longer made. The ability to override the value is kept, because a change at the bank would still announce itself as a rejected Acquirer ID.
* Compatibility: declared against WooCommerce 11.2, up from 9.5. The declaration had been left behind while WooCommerce released several major versions, so recent stores were shown an “untested with your version of WooCommerce” warning about a plugin that in fact runs on them. To be exact about what the new figure rests on: 1.0.40 has been running since 13 November 2026 on a live store on WooCommerce 11.2 and WordPress 7.1 where card payments through the bank are in daily use, so the checkout, the redirect to the bank and the return are exercised there constantly. The hourly reconciliation check has had no unresolved payment to look at on that store, so that path is covered by the test suite here and not yet by production traffic.

1.0.40

The hourly check for payments that were started but never confirmed can now ask the bank what actually happened to them, instead of only reporting that it does not know. Payments the bank confirms are reported with their approval code and transaction id, and can optionally be marked paid for you. Abandoned checkouts stop being reported as something to investigate. The new question is read-only and changes nothing at the bank; the one setting that can change an order is off until you turn it on.
* New: the check now asks the bank about a payment it cannot account for. Redirection returns the payment result through the customer’s browser, so a closed tab or a dropped connection loses it, and until now the plugin genuinely could not tell that apart from a checkout nobody completed. It now puts the question to the bank’s follow-up Web Service, using the credentials you have already entered, and acts on the answer. The call only reads the result of a transaction that already happened: it creates nothing, changes nothing at the bank, and is made only for attempts already past the grace period with no known outcome, so a busy store makes very few of them. Controlled by “Confirm unresolved payments with the bank”, which is on by default because on its own it cannot alter an order. If the bank rejects the credentials, the server’s IP address or the Acquirer ID, the “Integration health” panel says so in words you can act on instead of failing quietly.
* New, and off by default: “Complete orders the bank confirms”. With it off, a payment the bank confirms as approved is flagged on the order with the bank’s approval code, transaction id and support reference, and you mark the order paid yourself. With it on, the check does that for you, which is what finally closes a lost payment, an IRIS transfer especially, with nobody watching. It is off deliberately: the recommendation is to leave it off for a few days, compare the flagged orders against the epay eCommerce AdminTool, and turn it on once you have seen the plugin and the bank agree on real orders of yours. An order is only ever completed when the bank returns an approval for a MerchantReference belonging to that order, and the order is re-read immediately beforehand so a payment that arrived in the meantime cannot be processed twice.
* Safeguard: an order is not completed automatically if its total has changed since the payment was attempted. The bank’s answer tells you a specific attempt was approved, and that attempt was issued for whatever the order totalled at the time. If the order was edited afterwards, a line added over the phone for instance, the approved amount and the current total are different sums and completing the order would assert that the new one was paid. Those orders are flagged instead, with both figures and the bank’s approval code in the order note, so you can decide what to do about the difference. The same applies if the order’s currency no longer matches. An attempt made under different credentials than the ones now saved, which is what a brief switch to the test account or a migration to a new Merchant ID looks like, is not asked about at all rather than being written off on an answer from the wrong account.
* Improved: an abandoned checkout is no longer reported as needing attention. This is the change most stores will actually notice. Every payment attempt past the grace period with no response used to be flagged, annotated and listed for you to check in the AdminTool, and on a normal store the large majority of those are simply customers who changed their mind. When the bank confirms it never approved the attempt, it is now filed as accounted for with no flag, no order note and no admin notice, so the ones that remain are the ones worth your time.
* Improved: the answer is per payment attempt, not per order. An order a customer tried three times carries three MerchantReferences and the bank approved at most one of them. The check now asks about each open attempt separately, so a payment that succeeded on the second try is found behind the abandoned first one rather than the order being written off on the strength of the earliest attempt.
* Improved: the “Integration health” panel reports what the check concluded, not just that it ran. It shows how many attempts were put to the bank on the last run, how many were confirmed as paid, how many were confirmed never approved, and how many orders were completed automatically. An order the bank says it charged that is not marked paid in your store is reported in its own notice, which cannot be hidden for a week the way the ordinary one can, because that is a customer who is out of pocket.
* Fix: two scheduled runs can no longer overlap. WordPress does not serialise its own scheduled jobs, so a busy moment, or a server cron firing alongside a page view, could start the check twice at once. That was harmless while it only annotated orders and is not harmless now that it can complete one, so a run that finds another already in progress now steps aside.
* Correction to a note in the 1.0.39 changelog: that note said implementing the follow-up call would need separate bank credentials and the store’s outbound IP registered with the bank. Both were wrong. The call takes the same credentials you have already entered, with only an internal identifier differing, and the outbound IP is already registered at any store where card payments work at all, because the existing ticket request needs it from the same server. The genuine open question was whether the call reaches a payment made through Redirection at all; it was tested against a live account before this release was written, for a card payment and for IRIS, and it does.

1.0.39

Tells you within hours, instead of two days, that the scheduled check for unconfirmed payments has stopped running, and corrects the screens that still called that check daily after 1.0.38 made it hourly. No configuration change required.
* Fix: a stalled reconciliation check is now reported after 6 hours instead of 48. The check has run hourly since 1.0.38, but the threshold at which the “Integration health” panel and Site Health call it overdue was left at the figure chosen when it ran once a day. A store whose scheduled jobs had quietly stopped firing could therefore go two full days with both screens reporting nothing wrong, which defeats the point of reporting on a safety net at all: the panel exists to prove the check is running, and a proof that takes two days to fail is not worth much. Six hours still tolerates five missed hourly runs in a row, far more slack than a healthy site ever needs, so a low-traffic store is not warned about a schedule that is in fact working. The figure appears in the message itself, so it reads “more than 6 hours ago” and stays correct if it is ever tuned again.
* Fix: the gateway settings screen and Site Health no longer describe the check for unconfirmed payments as daily. It has run hourly since 1.0.38 and the wording had not caught up, so a merchant was told to expect one run a day while the same panel showed the next run an hour away, which made a correct schedule look wrong.
* Note on a known limitation: the check still never changes an order’s status and never marks anything paid, because it cannot ask the bank whether a payment actually settled. Earlier releases noted that the Web Service which would answer that question has a specification available only on request from Euronet Merchant Services. Euronet has now supplied it, and it does provide a follow-up call returning the result of a past payment. Implementing it is deliberately left to a later release: it needs separate bank credentials, the store’s outbound IP registered with the bank, and testing against the bank’s test account before any part of it is allowed to influence an order.

1.0.38

Fixes a regression that removed the card option from the block checkout entirely on recent WooCommerce versions, and a second fault that left the scheduled check unable to see most of the payments it was built to find. Also adds two checks that tell you when card payments have stopped working, before a customer has to, and fixes a case where a payment whose result could not be verified returned the customer to the payment page with no message at all. No configuration change required.
* Fix (important): the card option is back in the block checkout. On recent WooCommerce versions it had disappeared from the payment options altogether, while the gateway still showed as enabled under WooCommerce, Payments, still passed every availability check, and was still listed by the Store API as a method the store accepts. Nothing on any screen indicated a problem and nothing was written to any log; customers were simply left with no way to pay by card, and a merchant checking the settings would find them correct. The cause was the hook used to register the block checkout integration. WooCommerce fires woocommerce_blocks_loaded from inside its own loading sequence on plugins_loaded priority 10, and this plugin bootstraps on priority 11, so the listener was added after the action had already fired and was never invoked. Registration now happens directly on woocommerce_blocks_payment_method_type_registration, which fires later, on init priority 5, and is therefore reached in time. Should registration ever fail again for any reason, it is now recorded in the log rather than passing in silence. Stores on the older shortcode checkout were never affected.
* New: an alert when the bank stops answering. A gateway whose callback path breaks does not look broken. Checkout still works, the customer is still sent to the bank, and the card is still charged; only the response is lost, so orders sit in “pending” and the first person to notice is a customer. That has happened, caused by a callback URL left pointing at an old address in the Euronet portal. The plugin now watches for it: when several separate orders start a payment and not one of them produces a response, an alert appears on every admin screen naming what was observed. It distinguishes a store that has never received a response, which points at the callback URL registered with Euronet Merchant Services, from one where responses were arriving and then stopped, which points at something that changed. The alert clears itself the moment a response arrives. It is deliberately dismissible, unlike the credentials warning: that one is the bank telling you the credentials are wrong, while this one is inferred from an absence and can be innocent, because a customer who closes the payment page without paying also produces no response. The thresholds are filterable for stores whose volume makes the default judgement wrong.
* New: the daily check now proves it is running. The reconciliation added in 1.0.37 depends on WordPress scheduled jobs, which do not fire on a site with little traffic, or on one where WP-Cron has been disabled without a server cron put in its place. A safety net that has quietly never run is worse than no safety net, because you believe you are covered. Every run is now recorded, and a new “Integration health” panel on the gateway settings screen states plainly whether the bank’s responses are arriving and whether the daily check is actually running, with the dates to back both answers. The same two answers also appear under Tools, Site Health, where a host or developer looks first.
* Fix: when a failure response from the bank arrives carrying a signature that does not match, the plugin still refuses to change the order in any way, but the customer is no longer returned to the payment page in silence. That silence was the same unhelpful outcome this plugin avoids everywhere else: a page that looks like nothing happened, with an order left pending and nothing to explain it. A mismatched signature has two very different causes and the plugin cannot tell them apart from the response alone. It may be a genuine decline that could not be verified, for example because the POS ID or Acquirer ID was changed while a payment was in progress, in which case no money moved and paying again is harmless. Or it may be a forged failure sent over a payment that actually succeeded, in which case paying again charges the customer twice, and for an IRIS payment that second charge cannot be refunded because the bank does not accept refunds on IRIS transactions. The customer is therefore told that the outcome could not be confirmed and asked to contact the store before trying again, rather than being invited to retry. The order is left exactly as it was and the event continues to be recorded in the log for the merchant.
* Fix (important): the scheduled check could not see most of the orders it was built to find. The check added in 1.0.37 looks for payments that were started but never confirmed, so that a payment whose response was lost does not sit unnoticed. It treated a cancelled order as needing no attention. WooCommerce cancels unpaid orders by itself, after one hour by default, while the check waited two hours before examining anything, so by the time it looked almost every unconfirmed payment had already been cancelled and was dismissed as finished business. Measured on one live store: 33 payments had been started with no response ever received from the bank, and every one had been passed over without a flag, a note or a notice, while only 5 were reported. Two of those 5 were wrong in the other direction, orders that had in fact been paid and were cancelled afterwards, because the check asked whether an order is paid now instead of whether it was ever paid. The check no longer considers the order’s status at all. It now asks only what is actually known: the order was paid at some point, or the bank sent a response stating the payment was not approved. Everything else is reported, whatever status the order currently carries, and the note left on the order says plainly that a cancelled order is not evidence the payment failed, so it still needs checking in the epay eCommerce AdminTool. A payment the bank reported as approved on an order that was never marked paid is now reported separately and more urgently, because that combination should not occur. The check also runs hourly rather than once a day, and its waiting period is derived from your own “Hold stock (minutes)” setting instead of a fixed two hours, so that a flag reaches you while the order still looks live. Payments the old check already dismissed are not revisited automatically; anything still open is picked up on the next run.

1.0.37

Adds daily reconciliation for payments that never reported back and improves the 3-D Secure data sent to the card issuer, corrects the order status for pending IRIS payments, plus two fixes and a settings-screen clarification. No configuration change required.
* Improvement (3-D Secure): the customer’s phone number is now sent in the field that matches the kind of line it is. The Ticketing service accepts MobilePhone, HomePhone and WorkPhone as separate 3-D Secure inputs and the card issuer’s risk engine reads them as separate facts, but WooCommerce collects a single phone with no indication of its type, and every number was previously sent as a mobile. Greek numbers are now routed correctly (69x to MobilePhone, 2xx to HomePhone), which the national numbering plan makes unambiguous. Numbers from other countries are unchanged, because no equivalent guarantee exists there and a wrong guess would be worse than the current behaviour. Better 3-D Secure data means more payments approved without a challenge screen.
* New filter for stores that collect more than WooCommerce does: epay_paycenter_3ds_fields supplies BillAddrLine3, ShipAddrLine3, HomePhone, MobilePhone and WorkPhone for the 3-D Secure request. WooCommerce core has two address lines and one billing phone, so these fields have no standard source and the plugin will not invent values for data a fraud engine scores. A store whose checkout genuinely collects a third address line or a second phone number can now supply them. Everything the filter returns is re-validated against the specification’s character set and length limits before it is sent, and only those five field names are accepted, so the filter cannot alter the amount, the credentials or the transaction type.
* New: a prominent admin warning when the bank rejects the store’s credentials. ResultCode 100 (Authentication Error) means the Username or Password for the Ticketing Web Service is wrong, and because that is the one call carrying the credentials, it fails every single checkout: no customer can pay by card until it is corrected. Until now it appeared only as an individual customer decline and an order note, so a store could lose a day of card revenue with nothing on any admin screen explaining why. A warning now appears on every admin page, records when the failures began, quotes the bank’s response, and links straight to the credentials. It is not dismissible, because dismissing it would hide a complete outage, and it removes itself automatically the moment a payment is successfully started.
* New: a daily reconciliation check for payments that were started but never confirmed. If a customer is sent to the bank and the response never comes back, for example because a firewall or a stale callback URL in the Euronet portal swallows it, the order previously sat in “pending” forever with nothing to indicate anything had gone wrong. Such orders are now flagged after a grace period, given an order note listing their MerchantReference, and summarised in a dismissible admin notice. The check deliberately never changes an order’s status and never marks anything paid: without the bank’s follow-up Web Service, whose specification Euronet Merchant Services supplies on request, the plugin genuinely cannot distinguish an abandoned checkout from a completed payment whose response was lost, and guessing either way would be worse than reporting it. The affected orders are listed so they can be verified in the epay eCommerce AdminTool. The grace period (2 hours), retention (90 days) and batch size are filterable.
* Housekeeping: the internal ticket log finally has a lifecycle. Rows were written for every payment attempt and never read or removed, so the table grew indefinitely. Reconciliation now resolves each row to settled, closed or unresolved, and prunes resolved rows after 90 days. Unresolved rows are kept, because they are the audit trail for a payment nobody has accounted for yet.
* Fix (important, IRIS only): an IRIS payment that the bank reports as started but not yet completed (ResponseCode 09) is now placed ON HOLD instead of being marked failed. Per the Redirection Manual this code means the transfer was initiated and may still settle through DIAS, so marking it failed produced orders that were paid but recorded as failures, with nothing to reconcile the two. The customer is now told the payment is pending and asked NOT to pay again, and is sent to the order-received page rather than the pay-again page: an IRIS transfer still in flight can otherwise be paid a second time, and the bank does not accept refunds on IRIS transactions. Genuine IRIS declines (customer cancelled in the bank app, QR code timed out) are unaffected and still fail as before, as are all card declines, including a card response code 09, which does not carry the same meaning.
* Fix: pressing “Cancel” on the bank’s payment page now reliably cancels the order even when the payment page was opened from an earlier attempt. Every reload of the pay-for-order page issues a fresh cancel token, and only the most recent one was accepted, so a customer who reached the bank page, went Back and Forward, or used a second browser tab, could press Cancel and have nothing happen: the order stayed pending and they were returned to the generic checkout page with no explanation. The token is now matched against every still-open payment attempt on the order, using the same timing-safe comparison already applied to the bank’s callbacks. Forged, empty and expired tokens are still rejected.
* Fix: the “Logging” setting now enables debug logging on its own. Previously the debug-level lines also required the site-wide WP_DEBUG constant, which is off on virtually every production site, so ticking the box produced an empty log. The lines that were being suppressed are the ones needed to diagnose a callback that never arrives (“callback received before ticket issuance”, “endpoint hit without payload”, “callback from IP not in allowlist”), which is precisely the situation in which a merchant enables logging. Credentials, transaction tickets and HashKeys remain redacted as before.
* Improvement (merchant feedback): the “Bank integration data” panel now separates the two server addresses it was conflating. The row a merchant is meant to hand the bank is the server’s OUTBOUND IP, but the panel showed the address WordPress is served on, labelled simply “IP address”, with a one-click Copy button beside it. On a host that serves and egresses from different addresses (reverse proxy, load balancer, NAT, or simply more than one IP) that is the wrong value, and registering it with ePay makes every ticket request fail with nothing in the interface to explain why. The panel now shows “Outbound IP (the value ePay needs)” first and “Website IP (not the value for ePay)” below it, and the Copy button appears only next to a real outbound value. Because only a request to an outside host can reveal the outbound address, and this plugin makes no such call, the field explains how to obtain it (run curl -4 https://api.ipify.org over SSH, or ask your host) instead of displaying a confident wrong answer.
* New filter: epay_paycenter_outbound_ip lets a hosting provider, agency or site developer publish the server’s known outbound IP so it appears in the panel ready to copy. Returned values are validated as real IPv4 / IPv6 addresses and ignored otherwise. Thanks to the merchant who reported the IP mismatch in detail.
* Translations: the Greek catalogue is complete again. Two settings strings introduced in 1.0.36 (the password field description and its placeholder) had shipped untranslated and appeared in English on Greek installations; both are now translated, along with every string added in this release. The translation template shipped with the plugin was also regenerated from the current source, having been left at the 1.0.19 string set, so contributors on translate.wordpress.org now see the strings the plugin actually uses.
* Compatibility: tested against WordPress 7.1 and reviewed against its Field Guide. No API used by this plugin changed, was deprecated, or was removed. The PHP 7.4 minimum is unchanged and matches the WordPress 7.1 requirement.

1.0.36

Hardening release from an internal security review. No payment-flow change; no merchant action required.
* Hardening: the Ticketing Web Service password is now stored as the MD5 digest that the specification requires be transmitted, instead of in plain text. The plain password is never written to the database. Existing installations are converted automatically the next time the gateway settings are saved, and continue to work until then. The password field now always displays empty — leave it blank to keep the saved credential, or type a new password to replace it.
* Hardening: the callback endpoint is public and unauthenticated, so the diagnostic lines it writes are now drawn from an hourly budget. Previously a request flood could append unlimited attacker-supplied text to the WooCommerce log and fill the disk. Normal trade is far below the limit and is unaffected; when the budget is reached a single line records that suppression is active. Requests carrying no MerchantReference at all no longer produce a log line.
* Hardening: the per-order MerchantReference secret was lengthened from 6 to 12 characters (roughly 31 to 61 bits). This value is the only secret protecting the documented decline callback path, on which the bank sends no HashKey.
* Hardening: the optional epay_paycenter_allowed_callback_ips filter now only trusts the CF-Connecting-IP header when the request genuinely arrived through Cloudflare. On a site that is not behind Cloudflare that header is caller-supplied, so the allowlist could previously be bypassed with a spoofed header. Order state was never at risk — it remains gated on the HashKey and the MerchantReference secret.

1.0.35

  • Removed (important): the “Transaction type” and “Preauthorization expiry (days)” settings. All transactions are now sent as Sale (RequestType 02), which settles in the next batch with no further merchant action. Preauthorization only commits an amount — the Redirection Manual requires it to be completed separately (RequestType “SETTLE” via a Web Service whose specification Euronet Merchant Services supplies on request, or manually in the epay eCommerce AdminTool). That completion step was never implemented, so a store configured for Preauthorization marked orders as paid, reduced stock and shipped against funds that were only reserved and would silently expire. Removing the option resolves this. Stores previously set to Preauthorization now capture funds immediately, which is what their order statuses already indicated. If you deliberately relied on Preauthorization with manual completion in the AdminTool, please get in touch before updating.
  • Fix: the HMAC-SHA256 HashKey on a signed non-success callback is now verified against the transaction ticket belonging to that specific payment attempt. Two internal calls passed the ticket to functions that did not declare a parameter to receive it, so verification silently fell back to the most recent ticket stored on the order. On an order with several payment attempts (each reload of the pay-for-order page issues a fresh ticket) this could verify against …