Description
Transact securely from your WordPress site with Transactium, no coding required.
The plugin adds the Transactium EZPay payment method to WooCommerce. The customer types the card details into fields that Transactium’s script (ezpay.js) turns into a token in the browser, so card numbers never reach your server. Your server then asks Transactium to take the payment with that token.
Features
- One-time card payments in the classic (shortcode) checkout and in the WooCommerce block checkout
- 3-D Secure: the customer is sent to the issuer’s page when it is needed and returns to the order
- Refunds from the WooCommerce order screen (full or partial)
- Optional saved cards (tokenization) for repeat purchases; a saved card always asks for its security code (CVV)
- Subscription payments through WooCommerce Subscriptions (a separate plugin, not included)
- High-Performance Order Storage (HPOS) compatible
- Optional debug log under WooCommerce > Status > Logs
Requirements
- WordPress 6.5 or newer, PHP 8.2 or newer, WooCommerce 8.3 or newer (tested up to WordPress 7.1 and WooCommerce 11.3)
- A Transactium EZPay account (public and private key)
Transactium WooCommerce AddOn integrates with WooCommerce to allow customers to check out with Transactium EZPay.
Optionally, install WooCommerce Subscriptions to take subscription payments.
External services
This plugin connects to the Transactium EZPay payment service (psp.transactium.com, or psp.stg.transactium.com in staging mode) to take payments. Your site’s server sends the order total, currency, order reference and the billing/shipping details of the order, and a payment token produced in the customer’s browser. At checkout the customer’s browser also loads Transactium’s ezpay.js and stylesheet from the same host to tokenise the card. Service terms and privacy policy: Transactium.
Support
Problems? Require special customisations? Contact Us
Current Limitations
- The “add payment method” page of My Account is not offered: a card is saved while paying for an order.
- A saved card always needs its security code (CVV, 3 or 4 digits) when the customer pays. Automatic subscription renewals are exempt, because nobody is there to ask.
- If Transactium asks for 3-D Secure on an automatic subscription renewal, the renewal cannot be completed without the customer: it fails with an order note and the customer pays the renewal order from their account.
- The translations of 1.x do not carry over: the text domain changed to
transactium-woocommerce-addon(see the changelog).
Installation
Before you start
You need your own copy of WooCommerce (8.3 or newer) and a Transactium EZPay account. The plugin needs PHP 8.2 or newer; WordPress will not offer the 2.0 update to a site on an older PHP version, which simply stays on 1.18.
Steps
- Upload the plugin (Plugins > Add New, search for
Transactium WooCommerce AddOn, or upload the zip) and activate it. - Go to WooCommerce > Settings > Payments and open Transactium EZPay (older WooCommerce versions show it under the Checkout tab).
- Tick Enable this payment gateway and enter your EZPay – Public Key and EZPay – Private Key.
- Choose staging or live: Staging/Live Mode ticked means live; unticked talks to Transactium’s staging service (use it with your development keys and test cards).
- EZPay – 3DSecure: Off sends a plain sale; Async asks for 3-D Secure and sends the customer to the issuer’s page. Transactium can require 3-D Secure even when this is Off (see the FAQ); the customer is then sent to the issuer’s page anyway.
- Optional: Tokenization lets logged-in customers save a card; Subscriptions is for WooCommerce Subscriptions; Debug log writes gateway events to WooCommerce > Status > Logs (source
transactium-woocommerce-addon). Card data, tokens and keys are never logged. - In WooCommerce > Settings > General set your currency, save, and place a test order on the checkout.
Updating from 1.x
Nothing to do. Settings, saved cards, subscriptions, the callback address and earlier orders keep working as they are.
FAQ
Do I need to have my own copy of WooCommerce for this plugin to work?
Yes, you need to install the WooCommerce plugin for this plugin to work.
Does it work with the block checkout?
Yes, from 2.0. The classic shortcode checkout keeps working unchanged; you do not have to switch.
Is it compatible with HPOS (custom order tables)?
Yes, from 2.0. Orders created before the upgrade keep working, including refunds and subscription renewals.
Does it work with the latest WooCommerce?
2.0 requires WordPress 6.5, WooCommerce 8.3 and PHP 8.2 or newer. It has been tested on WordPress 7.1 with WooCommerce 8.3 and 11.3, and its code on PHP 8.2, 8.3 and 8.4. Newer releases may need a newer version of this plugin.
Do I have to do anything after updating from 1.x?
No. Settings, saved cards, subscriptions, the callback URL and previous orders are all used as they are. There is nothing to re-enter or re-save.
What happens to a payment that was in progress while I updated?
For 2 hours after the update, a customer who was sent to the issuer’s 3-D Secure page before the update and comes back in the same browser session is still completed. Payments of 1.x are never matched by the notification alone: if the customer does not come back, the order stays pending and you can check it in your Transactium portal.
Why does a payment show 3-D Secure even though 3DSecure is Off?
The Transactium service decides when authentication is needed. When it asks for it, the customer is always sent to the issuer’s page, whatever the setting says.
A payment failed. Where do I look?
Open the order: the order notes say what happened (declined, could not be verified, a second payment, and so on). For more detail, turn on Debug log and open WooCommerce > Status > Logs, source transactium-woocommerce-addon: every entry names the order number, and each line says whether it came from the customer’s browser (return) or from Transactium’s notification (ipn).
Does a saved card need its security code (CVV)?
Yes, every time the customer is paying: on the checkout, on the pay page (also when a renewal order is paid by hand) and for the first payment of a subscription. A missing or invalid code is refused before anything is sent to Transactium. Automatic subscription renewals are made without a customer and do not need it.
A subscription renewal failed with a note about 3-D Secure.
Transactium asked for customer authentication, which cannot be done for an automatic renewal. The renewal order stays unpaid; the customer can pay it from their account (the saved card needs its security code there).
How do I turn on logging?
Tick “Enable logging” in the Transactium EZPay settings. Entries appear under WooCommerce > Status > Logs (source transactium-woocommerce-addon). Card data, tokens and keys are never logged.
Your plugin just does not work
Please contact support.
Screenshots







Changelog
2.0.0
- New: WooCommerce block checkout support (the classic checkout keeps working unchanged).
- New: High-Performance Order Storage (HPOS) compatibility.
- New: optional debug log (WooCommerce > Status > Logs, source transactium-woocommerce-addon); every entry names its order.
- Security: removed an unauthenticated legacy callback branch that trusted posted values. Payment callbacks now need the merchant reference stored on the order, are re-verified with Transactium before anything changes, and saved cards can only be used by their owner.
- Fix: double finalisation. When the customer’s browser return and Transactium’s notification arrived together, the order notes and the customer/admin emails could be produced twice. The order is now re-read from the database after the lock is taken, and a lock can no longer be released by a request that lost it.
- Fix: subscription renewals (WooCommerce Subscriptions) use the current API and the transaction stored on the subscription; a renewal that Transactium sends to 3-D Secure now fails with a clear order note instead of the raw status.
- Fix: the card form no longer asks Transactium for a new session on every checkout refresh; the add-payment-method page no longer shows an error; guests are no longer sent with a client reference of 0; a customer returning after the notification was already processed is sent to the order page instead of a blank page; PHP 8.2+ deprecations and several logic errors.
- Change: a saved card now ALWAYS needs its security code (CVV, 3 or 4 digits) when the customer pays. Automatic subscription renewals are not affected. 1.x did not enforce a code.
- Change: the customer is always sent to the 3-D Secure page when Transactium asks for it, whatever the 3DSecure setting says.
- Change: after a declined payment the customer returns to the order’s pay page with the message and a retry, instead of the cart; the failure order note is written once per attempt; log lines say whether they came from the browser (return) or the notification (ipn).
- Change: merchant references are 25 characters (what Transactium keeps) and the payment is tied to its order by the reference stored on the order.
- Change: a late approved payment completes an order that WooCommerce cancelled or marked failed in the meantime; an approved payment for an order that cannot be completed (on hold, refunded…) leaves an order note and an error log entry for a manual review. Notifications that could not be processed (lock busy, Transactium not reachable) are answered 503 so that Transactium sends them again.
- Change: payments that were in flight during the upgrade from 1.x are accepted for 2 hours, only while the customer’s own checkout session returns, only for a reference that started between the creation of the order and the upgrade, and never with a transaction that already belongs to another order.
- Change: log lines remove card numbers only when they really are card numbers (checksum-validated, also with spaces or dashes), so numeric transaction ids stay readable. The session-key rate limit uses the connection’s address (filter transactium_ezpay_client_ip for sites behind a reverse proxy).
- Change: requires PHP 8.2, WordPress 6.5 and WooCommerce 8.3. Support code for WooCommerce 2.x/3.0 was removed and the plugin code split into smaller files.
- Change: the text domain is now transactium-woocommerce-addon (it was transactium-wc-addon), so translations made for 1.x need to be exported again.
- New: uninstall.php removes only the plugin’s own markers, locks and rate-limit transients; settings, orders, saved cards and subscriptions are never touched.
1.18
- Update : Add locking and further checks to prevent double order registration
1.17
- Update : Make tokenization and subscriptions optional and disabled by default
1.16
- Update : Fix BUG introduced in 1.15
1.15
- Update : Added IPN support for notifications
1.14
- Update : Removed obsolete methods (3ds v1)
- Update : Added proper client reference to all transactions
1.0
- Initial release.