Get in touch
TapPay Payments for WooCommerce — card payments in Taiwan with secure fields and 3D Secure
TapPay card fields at checkout Bank decline at checkout TapPay settings TapPay settings (2)
WooCommerce

TapPay Payments for WooCommerce — card payments in Taiwan with secure fields and 3D Secure

Card payments through TapPay: card fields at checkout, 3D Secure, confirmation by the Record API, classic and block checkout, TWD only. Pro adds refunds and a payment re-check.

Download Free
Pro · one-year licence Staging copies are included. The more sites, the cheaper each one
Compatibility
WordPress 6.2+ · WooCommerce 8.0+ · PHP 7.4+ · HPOS · classic and block checkout · TWD only · HTTPS · plugin languages: English, Traditional Chinese
Licence
a site + a staging copy, annual
Trial
7 days, no card, one per site
Updated
November 2026
Or all 395 Pro modules with All Access — 4 990 ₴ / year ≈ €98

What Free has,
and what Pro adds

The free version works with no time limit. Pro adds the rest of the features in the table.

Feature Free Pro
TapPay card fields at checkout: the number never reaches your server ✔ ✔
Classic and block checkout ✔ ✔
3D Secure through the TapPay page ✔ ✔
Payment confirmed by a Record API request, not by text in a link ✔ ✔
Amount and order number checked before Paid ✔ ✔
Buyer return and TapPay notification: whichever comes first works ✔ ✔
With no bank answer the order waits and the buyer is told not to pay again ✔ ✔
Later checks of an abandoned 3D Secure page ✔ ✔
Test mode and separate keys ✔ ✔
Partner Key stored encrypted ✔ ✔
E.164 phone format for Taiwan numbers ✔ ✔
Full and partial refunds from the order — ✔
A "Check the payment at TapPay" action — ✔

What it looks like

TapPay card fields at checkout
Real TapPay fields at checkout. TapPay sandbox.
Bank decline at checkout
The buyer sees text and the cart stays.
TapPay settings

Key points

What the buyer sees

The buyer picks the card, types the number, expiry and code into TapPay fields and presses pay.

What the admin gets

In the WooCommerce settings you enter the App ID, App Key, Partner Key and Merchant ID separately for sandbox and production.

How much it costs

The base version is free. Pro costs 990 UAH for a one-year licence. A year of updates, technical support and all Pro features.

The trial starts when you ask

A fresh install is the free version, nothing switches on by itself. The “Try Pro for 7 days” button → e-mail → the key right in the window and by e-mail.

One key — a site and a staging copy

Moving the site? Unlink the licence on the old domain and activate it on the new one yourself. A staging copy (staging., dev.) works with the same key and does not take a site slot. For studios — keys for 5 or 25 sites, or unlimited.

Technical requirements

  • WordPress 6.2+, WooCommerce 8.0+, PHP 7.4+.
  • A TapPay account and sandbox keys, and for production the keys after TapPay approval.
  • The site on HTTPS and port 443: otherwise TapPay sends no notification.
  • Shop currency TWD.

Version history

v1.0.0 Current November 2026

TapPay card payments, 3D Secure, confirmation by the Record API.

Frequently bought with TapPay Payments

All Access Need more? All modules (395) under one licence, new ones are added automatically. 4 990 ₴≈ €98 Learn more →

Full module description

TapPay Payments adds TapPay card payments to WooCommerce for shops in Taiwan. The card number is typed into TapPay secure fields and never reaches your server. The plugin gets a one-time prime, runs the payment and trusts only the Record API answer.

The TapPay Portal sign-up did not open from our network, and we have no Partner Key of our own. Real TapPay fields and a real prime from their sandbox work in block and classic checkout, and the real TapPay server refused that prime for a wrong Partner Key.

What the buyer sees

The buyer picks the card, types the number, expiry and code into TapPay fields and presses pay. The bank shows a 3D Secure page, then the buyer returns to the thank-you page.

If the bank declines, the buyer sees plain text and stays at checkout with the cart in place. If the bank does not answer, the thank-you page asks not to pay again: the plugin checks the payment by itself and updates the order.

What the admin gets

In the WooCommerce settings you enter the App ID, App Key, Partner Key and Merchant ID separately for sandbox and production. The plugin warns if keys are missing, the currency is not TWD or the site is not on HTTPS.

Each attempt leaves a note with the TapPay status. Pro adds full and partial refunds and a payment re-check action.

How it works, step by step

  1. In the TapPay Portal you take the App ID, App Key, Partner Key and Merchant ID.
  2. You enter them in the settings and enable the method.
  3. The buyer types the card into TapPay fields.
  4. The plugin runs the payment with a one-time prime.
  5. The bank shows 3D Secure.
  6. The plugin asks the Record API and only then marks the order paid.

Under the hood

  • The return link and the TapPay notification prove nothing by themselves: they only start a Record API request.
  • Each attempt has its own bank_transaction_id, so a payment can be found even with no answer.
  • After 421, 915 and similar codes the plugin offers no second payment until the result is known.
  • A one-time prime is never sent twice.
  • The Partner Key is stored encrypted with the site keys.
  • Card data and keys never reach the log.

How to install

  1. Plugins → Add New → Upload Plugin: pick the zip and activate.
  2. WooCommerce → Settings → Payments → TapPay: enter the sandbox keys.
  3. Make a test payment with card 4242 4242 4242 4242, a future expiry and code 123.
  4. After TapPay approves you, enter production keys and turn test mode off.
  5. For Pro: paste the key or start the 7-day trial.

The module is not on wordpress.org yet: the free version and Pro are one archive from this page. Without a key it works as the free version.

Questions
about the module

Didn't find the answer? Message us on Telegram and we'll reply within a business day.

@catcode_support Setup, compatibility, activation
Why TWD only?

Version 1.0 is tested with whole TWD amounts only, and we did not enable other currencies.

What if the buyer closes the bank page?

The order waits, the plugin checks it after 15, 60 and 240 minutes and leaves you a note.

Can a buyer pay twice because of a failure?

With no bank answer the plugin asks not to pay again and looks the payment up by the attempt number.

What happens after the trial?

Pro switches off, and taking cards keeps working.

Not quite what you are looking for?

We build custom modules for WordPress, WooCommerce, OpenCart and Shopify. Tell us about the task and we'll prepare an estimate.

Order a custom module