Active installs
8K+
Subscription includes
Support
Clover for WooCommerce is a WooCommerce payment gateway that connects your store to your Clover merchant account, so customers pay by card on your own checkout. They enter their card in Clover’s hosted form, and you capture, refund and look up payments from the WooCommerce order screen. It supports saved cards, WooCommerce Subscriptions and Pre-Orders, the cart and checkout blocks and High-Performance Order Storage.
Before you buy: Clover for WooCommerce supports Clover merchant accounts in the US and Canada. It takes card payments only, and it doesn’t sync products, inventory, customers or orders with Clover.
Customers enter their card in Clover’s hosted form on your classic or block checkout, so card entry happens in Clover’s form rather than in a field of your own. Turn on Address Verification Service to add a street address field, and AVS Card Holder Name Present to add a card holder name field, then switch on the matching fraud rules in your Clover account. Turn on detailed decline messages, and customers see the reason Clover gives when a payment is declined.

Turn on Tokenization and customers can tick Securely Save to Account at checkout, or add a card under My account » Payment methods. Cards are stored in Clover, not in your store. Clover allows one saved card per customer, so a shopper who wants a different card deletes the saved one first. The saved card also pays WooCommerce Subscriptions renewals and charges Pre-Orders when they are released, so repeat buyers check out faster and subscribers never re-enter payment details. Cards are kept separately for the sandbox and production environments.
Set Transaction Type to Authorization and Clover holds the amount on the card while the order waits On hold. When you ship, click Capture Charge on the order, or select several orders and capture them in bulk. Turn on Enable Partial Capture to take less than you authorized, for example after removing an out-of-stock item. You can never capture more than the authorization, and the order screen stops offering capture 30 days after it. Authorizing first suits made-to-order and backordered items, because the customer is charged only when you ship.

Open an order, click Refund, enter an amount and click the button that names your Clover payment method. Full and partial refunds both work, and you can refund the same order more than once up to its total, so your team never needs the Clover dashboard for a refund. Clover receives the amount only, not line items, and each charge carries the WooCommerce order number so you can match it in Clover. There is no separate void: refund the full total of an uncaptured authorization and the hold is released.

Charge takes the payment as soon as the customer places the order. Authorization only holds it. With Authorization, Charge Virtual-Only Orders still charges orders that contain only virtual products, so downloads and access arrive right away, and Capture Paid Orders captures when an order moves to Processing or Completed. Pick the type that fits how you fulfill orders: Charge for goods that ship fast, Authorization for made-to-order or backordered items. Test every setting first in Clover’s sandbox, which shows test card numbers at checkout.

The older Payeezy, Payeezy Gateway and Global Gateway connections are being retired and will stop processing payments. Enter your Clover Merchant ID, Public Token and Private Token, then click Use Clover. Once Clover is connected in Production, click Migrate saved cards. It runs in the background, 25 cards at a time, and moves matching subscriptions to Clover. eCheck payment methods can’t migrate, and Global Gateway stores need customers to enter their cards again. Keep the old gateway switched off once Clover is live, because only one gateway family is active at a time.
Clover works on its own. With Tokenization on, it pairs with WooCommerce Subscriptions for renewals on a saved card and with WooCommerce Pre-Orders for payment when an order is released. It also works with the cart and checkout blocks and High-Performance Order Storage. To keep card-testing bots out, add the AVS fields here and set up CVV and velocity rules in your Clover account.
Built and supported by Kestrel, a long-time WooCommerce extension developer. Read the Clover documentation, or contact Kestrel support if you want a hand getting started.

Clover merchant accounts in the United States and Canada. Other countries, including the UK, aren't supported, so check where your Clover account is registered before you buy. You can test the whole setup first with Clover's sandbox.
No. Clover for WooCommerce takes card payments only. It doesn't sync products, inventory, customers or orders between Clover and WooCommerce, and it doesn't send order line items to Clover. If you need inventory sync with Clover POS, this isn't the extension for it.
Yes, with Tokenization turned on. Renewals and Pre-Orders charge the customer's saved card, and customers can change the payment method on inactive subscriptions. Clover allows one saved card per customer.
You can capture authorized payments, in full or in part, and refund in full or in part from the order screen. There is no separate void. Refund the full total of an uncaptured authorization to release it.
No. Clover for WooCommerce takes card payments in Clover's hosted card form, and it has no Apple Pay, Google Pay or 3D Secure option. For fraud protection, turn on the AVS fields in the plugin and set up CVV and velocity rules in your Clover account.
Connect Clover in Production and click Migrate saved cards. Cards from Payeezy and Payeezy Gateway convert in batches and their subscriptions move with them. Global Gateway cards and eCheck payment methods can't migrate, so customers add them again.
Categories
Extension information
Quality Checks
Countries
Languages
Requirements