Linux 软件免费装

Transactium WooCommerce AddOn

开发者 transactium
transactiumdev
更新时间 2026年11月18日 23:39
捐献地址: 去捐款
PHP版本: 8.2 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

woocommerce payments credit card 3d secure transactium

下载

1.0 1.1 1.2 1.4 1.5 1.6 1.7 1.8 1.17 1.9 1.13 1.14 1.10 1.11 1.12 1.15 1.16 1.18 1.3 2.0.0

详情介绍:

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 Requirements
Transactium WooCommerce AddOn integrates with WooCommerce to allow customers to check out with Transactium EZPay. Optionally, install WooCommerce Subscriptions to take subscription payments.

安装:

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
  1. Upload the plugin (Plugins > Add New, search for Transactium WooCommerce AddOn, or upload the zip) and activate it.
  2. Go to WooCommerce > Settings > Payments and open Transactium EZPay (older WooCommerce versions show it under the Checkout tab).
  3. Tick Enable this payment gateway and enter your EZPay - Public Key and EZPay - Private Key.
  4. 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).
  5. 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.
  6. 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.
  7. 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.

屏幕截图:

  • The classic checkout with the Transactium card fields.
  • The block checkout with the Transactium card fields.
  • The block checkout with a saved card: only the security code (CVV) is asked.
  • The order received page after an approved payment.
  • The order notes of an approved order: one approval note and one set of emails.
  • A declined payment: the message and a retry on the order's pay page.

升级注意事项:

2.0.0 Security update, recommended for everyone. Requires PHP 8.2+, WordPress 6.5+ and WooCommerce 8.3+. No settings changes are needed. A saved card now always asks for its security code on the checkout.

常见问题:

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.

更新日志:

2.0.0 1.18 1.17 1.16 1.15 1.14 1.0