Get in touch
WooCommerce

Clover Payments for WooCommerce — cards in Clover fields, refunds, Apple Pay and Google Pay

Cards at WooCommerce checkout through Clover fields: card data never reaches the store. A safe payment retry, full and partial refunds. Pro adds Apple Pay, Google Pay, authorize and capture, Hosted Checkout and a journal. Run a sandbox payment first.

Download Free
Pro · one-year licence Staging copies are included. The more sites, the cheaper each one
Compatibility
WordPress 6.2+ · WooCommerce 7.0+ · PHP 7.4+ · block and classic checkout · languages: English, Canadian French
Licence
a site + a staging copy, annual
Trial
7 days, no card, one per site
Updated
November 2026
Or all 394 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
Clover card fields on the classic and block checkout and the pay page ✔ ✔
The store gets a one-time token, not card data ✔ ✔
A retry with the same key after a lost answer, so nothing is charged twice ✔ ✔
A payment check button on the order: it only reads and never charges ✔ ✔
Full and partial refunds ✔ ✔
Clear bank decline messages ✔ ✔
Amount check: a mismatch puts the order on hold ✔ ✔
Attempt limit against card testing ✔ ✔
Connection check: a wrong key, a sandbox key in Live, a private key in the public field ✔ ✔
Apple Pay and Google Pay — ✔
Authorize and capture — ✔
Clover Hosted Checkout with webhook signature check — ✔
Payment watchdog every 15 minutes — ✔
Payment journal — ✔

What it looks like

Card fields at checkout
Classic checkout with the real Clover script: the fields opened. No payment was made on this screen.
Decline message
A bank decline: the buyer sees a clear text.
Settings
Free version settings. Test keys.

Key points

What the buyer sees

The buyer picks card payment and sees the Clover fields on the classic or block checkout.

What the admin gets

In the settings you enter the Merchant ID, public and private keys, and the check button says what is wrong: a bad key, a sandbox key in Live mode or a private key in the wrong field.

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 7.0+, PHP 7.4+.
  • A Clover merchant account and Ecommerce API tokens.
  • HTTPS on the site.

Version history

v1.0.0 Current November 2026

Clover fields, refunds, a payment check.

Frequently bought with Clover Payments

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

Full module description

Clover Payments takes cards in WooCommerce through the fields of Clover itself. The buyer types the card right at checkout, and the store gets only a one-time token. The module is for merchants who already have a Clover account.

We have not run a single payment through real Clover. Before you take money, run a test payment in the sandbox.

What the buyer sees

The buyer picks card payment and sees the Clover fields on the classic or block checkout. If the bank declines, the buyer sees a clear message, the cart stays, and the order can be paid with another card.

What the admin gets

In the settings you enter the Merchant ID, public and private keys, and the check button says what is wrong: a bad key, a sandbox key in Live mode or a private key in the wrong field. The private key is stored encrypted.

A payment attempt is written to the order before the request goes to Clover. If the answer is lost, the retry uses the same key, and the check button looks for the payment in Clover without charging again.

How it works, step by step

  1. The buyer enters the card in the Clover fields.
  2. Clover returns a one-time token.
  3. The store server sends the charge with a stable attempt key.
  4. The plugin reads the result, checks the amount and updates the order.
  5. If the answer is lost, the attempt is checked in Clover without a second charge.

Under the hood

  • Card fields live in a Clover iframe, so the card number never reaches your server.
  • tax_amount is not sent: the Clover documentation says it blocks partial refunds.
  • The limit per order is more reliable than the limit per address, because an IP can be faked.
  • If the amount changes after a lost answer and the payment is not visible yet, a new attempt could in theory create a second payment. This goes into the order notes.

How to install

  1. Plugins → Add New → Upload Plugin: pick the zip and activate.
  2. WooCommerce → Settings → Payments → Clover.
  3. Keep Sandbox mode, enter the Merchant ID and keys, press the check button.
  4. Run a test payment and only then switch to Live.
  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
Is this the official Clover plugin?

No, it is an independent integration. Clover has its own plugin.

Does the store see the card number?

No. The fields belong to Clover, and the store gets only a token.

Can I refund part of an amount?

Yes, from the order screen.

Is there one for OpenCart?

Yes, it is a separate module.

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