WooCommerce Crypto Payment Plugin: The 10-Minute Finality Setup (Non-Custodial)

The short answer: install the Finality plugin, paste two credentials (an API key and a webhook secret), and your WooCommerce checkout gains a crypto option — USDC, USDT, and native coins across five chains. When a customer pays, the money settles directly into your own wallet (never a platform balance), and the order moves to Processing by itself once settlement lands on-chain. Ten minutes, no code, and a sandbox mode that lets you rehearse the whole thing with zero real money. Here's the exact walkthrough, including the two edge cases most tutorials skip.

Before the plugin: three things you set up once

Do this in the Finality dashboard first — it takes five minutes and you never touch it again:

1. 1Add your payout wallet address per chain (Settings). This is where every payment lands. Because Finality is non-custodial, that address is the only place your money ever goes — there's no platform balance in between, nothing for anyone to freeze, and also no undo for a wrong address. Check it twice.
2. 2Create an API key. It's shown once — copy it somewhere safe. Start with a key beginning sk_test_ so you can rehearse without real money.
3. 3Copy your webhook secret from the same page. The plugin uses it to verify that "payment received" notifications really came from Finality and not from someone pretending to be Finality.

The WooCommerce setup, step by step

1. 1Upload the plugin in your WordPress admin (Plugins → Add New → Upload), then activate it.
2. 2Open Settings → Payments and enable Finality as a payment method.
3. 3Paste the API key and webhook secret you copied above. Save.
4. 4That's the integration. Crypto now appears as a payment option at checkout, next to your existing methods — it doesn't replace them.

Your customer picks crypto at checkout, chooses a coin and chain on the hosted payment page, and pays — from a browser wallet, a mobile wallet via QR code, or by withdrawing straight from an exchange like Binance or Coinbase, because every order gets its own dedicated payment address. That last path matters more than it sounds: a huge share of real customers keep their crypto on exchanges, and wallet-connect-only checkouts simply lose them.

Rehearse before you go live

With a sk_test_ key active, create a test order in your own store, open the payment page, and hit "simulate payment". You'll watch the full production sequence run with zero real money: payment detected, settlement executed, webhook delivered, order flipped to Processing on its own. When it looks right, swap in your sk_live_ key. That's the entire go-live.

This rehearsal is worth the five minutes: you're not testing whether Finality works, you're testing that your store reacts the way you expect — emails, stock updates, fulfillment triggers.

What happens on a real order

• Customer pays → Finality's own full nodes detect the payment the moment it enters a block (sub-second on Solana, a few seconds on EVM chains) — the checkout flips to "paid" while your customer is still looking at it.
• Settlement executes on-chain, in the same flow: the platform's flat 1% splits off and the rest lands in your wallet. There is no payout schedule, because there is no payout — the customer's payment is your settlement.
• The signed webhook arrives, and WooCommerce moves the order to Processing automatically. You ship. Reconciliation is 1:1 by construction — every order has its own address.

Two edge cases worth knowing about (both are surfaced in your dashboard, neither loses money):

• Partial payment. A customer sends less than the total — the order stays open as "partially paid" and shows the remaining amount; they top up the same address and it completes. You're never asked to ship against half a payment.
• Late payment. Money arrives after the payment window expired — it shows up as a late payment, the funds sit safely in that order's dedicated address, and you can recover them from the dashboard. Annoying, visible, and recoverable — which is more than most gateways can say about an expired invoice.

Why non-custodial matters for a store owner, in one paragraph

Every custodial plugin (Coinbase Commerce, BitPay, NOWPayments) routes your revenue through a platform account: money accumulates there, you withdraw on their schedule, and their risk team can pause the whole thing. The Finality plugin has no account to pause — settlement rules are welded into each payment address at creation, so the money physically cannot go anywhere but your wallet. Flat 1%, no chargebacks, no payout queue. If you're comparing plugins right now, that's the dividing line to compare on — here's the full custodial-vs-non-custodial breakdown.

Not running a full store?

• WordPress without WooCommerce — the plugin gives you a shortcode: put [finality_pay amount="49"] on any page and it renders a payment button. Tips, donations, memberships, a single product page — no cart needed.
• Shopify — Shopify only allows certified partners inside its native checkout, so the Finality app works honestly around that: after the customer orders, it sends them a payment link, then tags the order once settlement lands. Slightly different flow, same non-custodial rails.
• No website at all — create a payment link in the dashboard and send it by email or chat; it works as a QR code too.

Selling subscriptions from your store?

If your store sells memberships or anything recurring, this is where Finality stops being "another plugin" entirely: it runs the industry's first real crypto subscriptions — automatic recurring charges from a vault only the customer controls, not renewal-reminder emails. And if you grow through affiliates, the built-in affiliate system splits commissions inside the customer's own payment transaction, straight to each affiliate's wallet — no monthly payout spreadsheet. The subscription architecture is here; the USDC guide covers choosing chains and coins.

FAQ

Does the plugin replace my card checkout?

No — crypto appears as an additional payment method. Customers who want cards keep using cards.

Which coins and chains will my customers see?

The ones you enable: USDC/USDT and native coins across Solana, Ethereum, Base, BNB Chain, and Robinhood Chain. Stablecoins-first is the sensible default — your prices stay in dollars.

Do I need to handle exchange rates?

No. The customer's quote locks when they choose a coin at checkout; you receive the settled amount in your wallet.

What does it cost?

A flat 1% per successful payment, carved out on-chain during settlement. No monthly fee, no setup fee, nothing on payments that never complete — and no withdrawal fees, because there are no withdrawals.

How do I add crypto payments to WooCommerce?

The three steps this article walks through: upload the plugin, paste the two credentials (API key + webhook secret) under Settings → Payments, enable your chains — rehearse in sandbox first and your first order moves itself to Processing.

What's the best WooCommerce crypto payment plugin?

Judge by the five production criteria — underpayment handling, order-status automation, custody of settlement — not the coin-count banner. The break-it-on-purpose sandbox test beats every review page.

Do my customers need a crypto wallet to check out?

No — an exchange withdrawal to the order's dedicated address completes the purchase. Wallet users scan; exchange users withdraw; the plugin treats both as the same payment.

What happens when a customer underpays an order?

The order shows partially paid with the shortfall visible — usually an exchange fee shaved the send — and the customer tops up to the same address. Nothing cancels; nobody emails support.

Does the plugin work with WordPress outside the shop pages?

That's the shortcode's job — [finality_pay amount="49"] renders a payment button in any post or page, the non-store patterns are their own guide.

Can I run subscriptions through WooCommerce with this?

Checkout and vault subscriptions share one account — recurring products charge automatically from customer-controlled vaults, which no reminder-email "subscription" plugin actually does.

Is the plugin PCI-compliant?

Nothing card-shaped ever touches your server — the payment page is hosted, the settlement is on-chain, the compliance surface shrinks structurally.

What if a customer pays after the order's quote expires?

Late payments are detected and flagged against the order rather than lost — honor or refund at your call; the dashboard shows exactly what arrived when.

Do refunds work from inside WooCommerce?

The refund is a send from your own wallet; the order record is what you update in Woo. Never refund to an exchange deposit address — ask the customer for a wallet address.

Will the plugin slow down my store?

The checkout hand-off is a redirect to a hosted page; your theme carries no payment JavaScript. Detection speed is server-side — sub-second on fast chains — and your pages stay yours.

Ten minutes from now, crypto can be just another payment method in your store — one that happens to pay you instantly, in your own wallet: set up the sandbox, simulate a payment, and watch an order move itself to Processing. Every API detail is in the docs, live-testable in the API explorer.