WordPress Crypto Plugin Without the Store: One Shortcode, Paid in Your Own Wallet
Most WordPress sites aren't shops — they're blogs, portfolios, communities, and course pages that still want to get paid. One shortcode puts a non-custodial crypto payment button on any page: tips, donations, memberships, single products. No WooCommerce required.
The short answer: you don't need WooCommerce, a cart, or a "store" to get paid on WordPress. The Finality plugin gives you a shortcode — [finality_pay amount="49"] — that renders a payment button on any page or post. A visitor clicks it, pays in USDC/USDT or native coins from any wallet or a plain exchange withdrawal, and the money settles into your own wallet, minus a flat 1%, on-chain. Tips, donations, memberships, a single product, a course, a consulting deposit — if it lives on a WordPress page, it can now take payment there. Running an actual WooCommerce shop? That's its own ten-minute guide; this one is for everyone else.
Most WordPress sites aren't stores — and most guides pretend otherwise
WordPress runs a huge share of the web, and the overwhelming majority of it isn't e-commerce: blogs, newsletters, portfolios, documentation, communities, course sites, local businesses with a contact page. Every "accept crypto on WordPress" guide immediately assumes you want a shop plugin, cart flows, and product catalogs — machinery that's pure overhead if what you actually want is "a reader pays me $49 on this page."
The shortcode model matches how non-store sites actually work: payment as content. You place it where the paying happens — end of a post, a /support page, a course landing page — the way you'd place an image or an embed.
The two-minute setup
- 1In the Finality dashboard: add your wallet address per chain (the only place money will go — check it twice), create an API key, copy your webhook secret. Once, five minutes, never again.
- 2Upload the plugin in WordPress admin, activate, paste the two credentials.
- 3Put the shortcode wherever payment should happen:
[finality_pay amount="49"]That's the integration. The button opens a hosted checkout with a dedicated address for that payment — coin and chain picker, QR code, live paid status — and your dashboard records every payment with reconciliation built in by construction.
What people actually use this for
- Tips and donations. A /support page with one button beats a wallet address pasted in a footer in every way that matters: amounts are encoded (no hand-typing errors), every payment gets its own address (you know what arrived and why), and payers can come straight from an exchange — the wallet-less majority included.
- Single products. An ebook, a preset pack, a template — one landing page, one shortcode, no cart pretending three items might exist.
- Course and community access. Take the payment on the sales page; grant access on the
payment.settledwebhook — the signal that fires only after money reached your wallet (the full flow). - Deposits and invoices for services. A consulting page with a deposit button, or a payment link pasted into your proposal — same machine, different packaging.
- Global audiences, structurally. A reader in a USDT-first economy pays in what they hold (why that widens your reach) — no card network deciding which countries your supporters can be from.
Why non-custodial matters double for small sites
Big merchants negotiate with processors; a blogger with a donations button doesn't. If your support revenue flows through a custodial platform, you have the same freeze exposure as an enterprise — with none of the leverage. The non-custodial model deletes that asymmetry: money lands in a wallet only you control, there's no account to review, and the platform structurally cannot hold your funds. A flat 1% on-chain — auditable per payment — and no chargebacks means a $5 tip can't turn into a $20 dispute fee.
Memberships: where this gets genuinely interesting
One-off payments cover most pages. But if your site runs on recurring support — memberships, premium newsletters, communities — reminder-based renewal is where crypto has always fallen apart, and where Finality's real subscriptions change the sentence entirely: automatic recurring charges from a vault only the member controls, no renewal nagging, cancel refunds the remaining balance and the rent deposit. For a WordPress membership site, that's card-subscription UX with crypto's custody model — an industry first, and a topic worth its own read.
FAQ
Do I need WooCommerce installed?
No — the shortcode works on plain WordPress, any theme, pages or posts. WooCommerce is only for actual catalog stores, covered separately.
Can I have different amounts on different pages?
Yes — each shortcode carries its own amount, and each rendered payment gets its own dedicated address, so your dashboard cleanly separates the $5 tips from the $200 course.
What do my readers need in order to pay?
Any wallet — or none: the checkout's dedicated address means an exchange withdrawal from Binance or Coinbase is a complete payment.
What does it cost me?
A flat 1% on successful payments, split on-chain during settlement. No monthly fee, no setup fee, and a $0 month costs $0.
How do I accept crypto payments on WordPress?
One shortcode on any page — [finality_pay amount="49"] — after a two-minute setup: sandbox key, paste credentials, publish. No store, no cart, no checkout rebuild.
What's the best WordPress bitcoin plugin?
Reframe slightly: your readers mostly hold stablecoins and exchange balances, not wallet BTC — so the best "bitcoin plugin" is the one whose checkout takes exchange withdrawals of anything, BTC-holders included via a two-tap conversion.
Can I take donations on a WordPress blog?
The shortcode is the donation button — set an amount or let supporters pick, the nonprofit playbook applies to blogs unchanged: link in posts, QR in the sidebar.
Can I sell digital downloads without WooCommerce?
Pattern from the article: shortcode on the sales page, webhook flips access on payment.settled — for a handful of products, that's the whole store.
Do WordPress crypto payments work with any theme?
The shortcode renders inside your content area like any embed — no theme hooks, no template edits. If your theme shows posts, it shows the button.
What about recurring supporter payments — memberships?
The membership upgrade is vault subscriptions: supporters fund a vault they control, the membership charges itself, cancellation returns unspent funds — kinder than any card-on-file.
Is a crypto plugin safer for a small site than card processing?
Structurally lighter: no card data means no PCI surface, and non-custodial settlement means the freeze-your-account risk — the one small sites can least absorb — doesn't exist.
Where does the money actually go?
Straight to your wallet, inside the payer's transaction — nobody holds it in between. The plugin renders buttons; the rail settles; your dashboard reconciles.
Can I track which page generated which payment?
Each shortcode's payments carry their own dedicated addresses — reconciliation separates them by construction: the tip jar, the course page, the consulting deposit, each its own clean line.
What happens if a reader underpays or pays late?
Same machinery as full checkouts — shortfalls prompt a top-up, late payments are flagged and matched. The shortcode inherits the whole payment engine, not a lite version.
If your WordPress site has ever had a "support me" ambition, the distance to done is one shortcode: grab a sandbox key, drop the button on a draft page, simulate a payment, and watch it land — your page, your button, your wallet.