Clover Payment

$39.00

Select Billing Option

1 Year

2 Years

Your POS Is Already Clover. Your Checkout Should Be Too.

You swipe Clover at the counter every day. Your online store is running through something completely different. Clover Payment for J2Commerce closes that gap — card fields on your page, saved cards, auto-renewing subscriptions, and admin controls for every post-sale action, all wired to the same Clover account you already have.

SAQ-A

PCI compliance tier — the lightest available

Checkout modes — iframe on-site or Hosted Checkout redirect

Admin order actions — Capture, Void, Refund, Charge Saved Card

Languages included

What Your Clover Account Can Actually Do — When It's Wired Into Your Store

Twenty-five code-verified features across the full payment lifecycle. One plugin. Two checkout modes. The complete Clover integration your Joomla ecommerce store should have had from day one.

SAQ-A Card Fields — On Your Page

Card number, expiry, CVV, and postal code render inside Clover-hosted fields on your Joomla checkout page. Your server receives a single-use token. The card data never touches your infrastructure. Lowest PCI compliance burden available to an ecommerce merchant.

Two Checkout Modes, One Plugin

Embedded iframe mode keeps the shopper on your page from start to finish. Hosted Checkout mode redirects to Clover's secured payment environment. One config toggle picks which. Same plugin, same admin panel, same order history either way.

Saved Cards — Card-on-File

Logged-in shoppers save their card at checkout and see it waiting on every return visit. Brand, last four digits, expiry. One tap. Returning customers — already sold on you — get the fastest possible path to purchase. No wallet hunting. No friction.

Subscription Auto-Renewal

Subscription products charge the stored card automatically when renewal comes due. Merchant-initiated, fully hands-off. No manual reconciliation. No failed-renewal support queue. Revenue that arrives without anyone lifting a finger.

Authorize Now, Capture When You Ship

Pre-authorize the card at order time and capture from the J2Commerce order screen when the goods go out. One-click capture for your team. Void option available until the transaction settles. Charge when you ship, not when they order.

Admin: Capture, Void, Refund, Charge Card

The order screen shows the right action for the current transaction state — and only that action. Auth pending: Capture and Void. Settled sale: Refund (full or partial with cumulative accounting). Need to run a card for a phone order? Charge a saved card directly from the admin. No portal hopping. No double-reversal accidents.

Signature-Verified Webhooks

When a shopper's browser crashes mid-checkout, the order still finalizes. Clover's payment notification hits your server, the signature is verified against your webhook secret, and the order updates — no browser required. What the gateway says happened matches what your store records.

Surcharge Support (% + Fixed)

Add a percentage and/or fixed surcharge to Clover card payments, shown as a labeled line item at checkout. Assign a tax class to the surcharge so it's taxed correctly — not lumped in as an untaxed adjustment. Margin recovered. No surprises on either end.

Debug Logging + Sandbox Toggle

One toggle writes every Clover API exchange to your Joomla log directory. A dedicated sandbox mode with completely separate credentials lets you test every flow without touching live payments. A dashboard warning keeps sandbox mode visible so you can't accidentally forget to go live.

Card Fields on Your Page. PCI Burden on Clover.

Clover's card fields render inside hosted iframes that look and feel like part of your Joomla checkout — but the card data flows directly to Clover's servers, never through yours. You receive a single-use payment token. That's SAQ-A: the lightest PCI compliance load available to an ecommerce merchant. No redirect. No "you are leaving our site" moment. No mobile checkout friction from a third-party page that's never met your customers. The shopper fills in their card and hits Pay without ever leaving your checkout flow. Your conversion funnel stays intact.

Clover-hosted card fields embedded in your J2Commerce checkout layout
Single-use token — raw card data never reaches your server
Lowest PCI compliance scope for card-present ecommerce

Saved Cards — One Checkout. Every Visit After That.

Logged-in customers save their card at checkout and see it waiting every time they come back — brand, last four digits, expiry. One tap. Done. Your returning customers — the ones with the highest lifetime value, the ones who already like you — get the fastest possible checkout experience. And when those customers subscribe to a recurring product, the same stored card handles every renewal automatically: merchant-initiated, no shopper interaction required, no manual billing cycle. Subscription orders force the card to be saved at first checkout, because a subscription that can't renew hands-free isn't a subscription. It's a recurring headache.

Save at checkout, reuse on every return visit with one tap
Subscription renewals charge the saved card automatically
Admin can charge any saved card directly from the order screen

Admin Controls That Know What State the Transaction Is In

The payment panel in every J2Commerce order shows exactly the actions available for that transaction's current state — and nothing else. Authorized but not captured: Capture and Void. Settled sale: Refund, full or partial, with cumulative accounting that tracks partial refund totals so you never accidentally exceed what was charged. Already voided or fully refunded: a status note, no action buttons. Need to charge a stored card for a phone order or a balance-due situation? A Charge Saved Card panel lets your team pick a card and run it — without anyone opening the Clover developer portal. One screen. The right controls. Always.

Capture authorized payments from the J2Commerce order screen
Full or partial refunds with cumulative accounting — no over-refund risk
Charge a saved card manually for phone orders and balance-due scenarios

Real-World Use Cases

A specialty outdoor gear shop had used Clover at their physical register for three years before they launched an online store. Their first online checkout plugin sent customers to a generic hosted payment page with a different brand name on it. Refunds went through a separate portal. Reconciliation required a spreadsheet every month. Switching to Clover Payment for J2Commerce put the card fields directly on their Joomla checkout page and routed every online transaction through the same Clover account as their in-person sales. One reconciliation. One gateway report. Their accountant stopped asking why the numbers didn't match. Their staff could process a refund from the J2Commerce order screen without logging into anything else. That's not a workflow improvement. That's the way it should have worked from day one.

A curated candle subscription service was manually billing each renewal cycle — pull the subscriber list, charge each one in the gateway portal, update the order. At 50 subscribers it was annoying. At 300 it was a part-time job and someone was doing it on Sunday afternoons. With the saved card subscription flow in Clover Payment for J2Commerce, each subscriber's card is stored at first checkout. Every renewal fires automatically as a scheduled merchant-initiated charge. The order marks paid. The next renewal date updates. The team reviews a weekly report. Nobody is running manual billing anymore. Nobody is working Sunday afternoons anymore. The subscription product became actual recurring revenue instead of recurring labor.

An industrial supply company sells to procurement departments who require internal approval before payment finalizes. Their old flow — charge on order placement, deal with disputes when the shipment was delayed — created friction with their biggest accounts. Auth + Capture fixed it. The card is authorized at order time and the procurement team sees the hold, which satisfies their internal approval workflow. No money moves until the goods actually ship. The J2Commerce order screen shows the Capture button. When the pallet leaves the warehouse, the team clicks Capture and the funds settle. Disputes dropped. Their largest accounts stopped calling about billing timing. The wholesaler's operations team stopped fielding payment complaints that had nothing to do with the product and everything to do with when the charge hit.

Your Clover Account Is Already Running. Put It to Work Online.

Card fields on your page. Saved cards your customers actually use. Subscriptions that renew themselves. Refunds in 60 seconds from the order screen. That's what it looks like when your online store and your Clover account are finally speaking the same language.

Translated In The Following Languages

Arabic Unitag (ar-AA), Chinese, Traditional (zh-TW), Danish (da-DK), Dutch (nl-NL), English (en-GB), English, USA (en-US), Finnish (fi-FI), French (fr-FR), German (de-DE), Greek (el-GR), Hebrew (he-IL), Italian (it-IT), Japanese (ja-JP), Norwegian Bokmål (nb-NO), Persian Farsi (fa-IR), Polish (pl-PL), Portuguese, Brazil (pt-BR), Portuguese, Portugal (pt-PT), Russian (ru-RU), Spanish (es-ES), Swedish (sv-SE), Turkish (tr-TR)

License Information

An active license entitles you to updates, downloads, and support for the duration of the license period. You may continue using this plugin indefinitely without an active license; however, support, updates, and downloads will not be available while your license is inactive.