How to Accept Crypto Payments on Your WordPress Website
23/09/2026

To accept crypto payments on WordPress, you can add a WooCommerce payment plugin, place a hosted payment link or QR code on the site, or connect a crypto payment API for a custom checkout. The right method depends on whether you run a store, a service site or a custom WordPress project. A WordPress crypto payment gateway can also handle payment addresses, transaction monitoring, conversion and payment status updates for you.
TL;DR
WooCommerce stores can use a no-code crypto payment plugin for WordPress and add cryptocurrency as another checkout option.
Blogs, landing pages and service sites can use Payment Links & QR Codes without building a full shopping cart.
Custom projects can use a Payment API to generate payment addresses or invoice links and receive payment-status callbacks.
Merchants can accept assets such as BTC, ETH, USDT and USDC, then use stablecoin conversion to reduce exposure to price movements after payment.
Test the full payment flow before launch: checkout, network selection, payment detection, order status, refunds and accounting records.
Which Integration Method Fits Your WordPress Site?
Method | Best for | Code required? | Typical setup time | PassimPay product |
No-code plugin | WooCommerce stores; similar CMS setups | No | About 10–15 minutes after onboarding | E-commerce Plugins |
Payment button / link | Blogs, landing pages, services, donations, one-off invoices | No; a normal link or button is enough | About 5 minutes | Payment Links & QR Codes / Hosted Checkout |
Full API integration | Custom checkout, marketplaces, higher-volume sites, custom UX | Yes | From several hours | Payment API |
The setup times are practical estimates and do not include business verification, internal testing or custom development.
How We Prepared This Guide
This guide was manually cross-checked in September 2026 against the current PassimPay WooCommerce module page, PassimPay API documentation, PassimPay support materials and current WordPress and WooCommerce payment documentation.
Interface labels are used only where the current documentation shows them. The guide also separates on-chain confirmation from provider-side payment detection so that a “fast payment” claim is not treated as a universal blockchain settlement time.
Why Accept Crypto Payments on WordPress?
Accepting crypto can add a payment route for customers who prefer digital assets or cannot use the same card and bank rails as the merchant. For international e-commerce, a provider can also remove the need to manage wallet addresses, blockchain monitoring and payment reconciliation manually. PassimPay, for example, offers a crypto payment gateway for e-commerce with plugin and API options.
Reach Customers Who Prefer Crypto
A WordPress store can accept Bitcoin, stablecoins and other supported assets without asking the customer to use a specific bank or card issuer. PassimPay currently supports 74 cryptocurrencies and 18+ blockchains and is available to eligible businesses in 122 countries.
If the goal is simply to accept Bitcoin payments on WordPress, you can enable BTC together with the other assets and networks your customers actually use rather than making every available option part of checkout.
Reduce Payment Processing Costs
Crypto payments use blockchain networks rather than card interchange and acquiring rails. PassimPay publishes processing fees starting at 0.5%, which may reduce acceptance costs for merchants whose card processing is more expensive.
Avoid Card-Network Chargebacks
Confirmed blockchain transfers are generally irreversible. A customer cannot reverse an on-chain payment through the card-network chargeback process, although a merchant can still issue a refund under its own refund policy.
Receive Payment Status Quickly
PassimPay reports an average transaction-processing time of about five seconds. That figure should be read as provider-side processing or detection rather than guaranteed final blockchain settlement: confirmation time still depends on the asset, network and network conditions.
How to Accept Crypto Payments on WordPress: 3 Integration Methods
There are three practical ways to accept crypto payments on WordPress. The plugin route is the simplest for WooCommerce crypto payments, payment links fit sites without a cart, and the API route gives developers control over the checkout flow.
Method 1: Add a No-Code WooCommerce Crypto Payment Plugin
For a standard online store, a ready-made gateway plugin is usually the shortest route. WooCommerce supports payment gateways through plugins, and PassimPay provides a dedicated WooCommerce plugin.
PassimPay also provides ready-made modules for platforms such as Shopify, Magento, PrestaShop and OpenCart, which can be useful for companies maintaining more than one e-commerce site.
1. Create and Verify a Business Account
Register a PassimPay business account, complete the required verification, and add the WordPress store as a project in the Platforms section. Choose the cryptocurrencies and networks you want to make available to customers.
2. Configure the Project URLs
The Notification URL is also configured in the PassimPay project and is required for payment callbacks. Its exact value is generated by the WooCommerce plugin, so install and open the plugin settings first, then copy the Notification URL shown there into the corresponding field in your PassimPay project. It normally looks like:
https://your-shop.com/?wc-api=passimpay
Without a valid Notification URL, WooCommerce will not receive PassimPay payment notifications.
3. Install the WordPress Plugin
Download the PassimPay WooCommerce module and upload the plugin archive in WordPress, then activate it. This is a WordPress/WooCommerce extension, so WooCommerce must already be installed and configured on the site.
4. Connect the Payment Gateway
Go to WooCommerce → Settings → Payments and open Passimpay Payment Gateway. Enable the gateway, copy the exact Notification URL displayed in the plugin settings and paste it into the Notification URL field of your PassimPay project. Then enter the Platform Id and Secret Key from your merchant account.
The documented payment options let the merchant choose what appears on the PassimPay payment page, including cryptocurrency-only or other supported payment modes where enabled for the account.
5. Test a Real Checkout
PassimPay's current module instructions recommend creating a low-value product and making a test purchase. Check that the customer reaches the payment page, the transaction appears in the PassimPay account, the notification reaches WooCommerce and the order status updates as expected.
PassimPay does not publicly document a separate sandbox for this flow, so use a small real transaction and confirm the current testing procedure before launch.
Method 2: Use a Payment Link, QR Code or Payment Button
A full WooCommerce checkout is unnecessary for many WordPress sites. Consultants, agencies, creators, donation pages and B2B service providers may only need a way to request a specific payment.
1. Create a Payment Request
Create an invoice or payment link in the business account and set the requested amount and supported payment currency. The hosted payment page can display the wallet address, QR code and amount for the customer.
2. Place It on the WordPress Site
Add the link to a normal WordPress button, pricing page, client portal or service page. This creates a simple crypto payment button on WordPress without custom payment logic. The same link can also be sent by email or messenger for an invoice outside the site.
3. Track the Payment
After the customer pays, monitor the payment status in the merchant account. This method is useful for one-off invoices, deposits, donations and sites that do not need product-level WooCommerce order handling.
The main tradeoff is automation: a hosted link is quicker to deploy, while a plugin or API is better when every payment must update an internal order, subscription or customer record automatically.
Method 3: Build a Custom Crypto Payment API Integration
A crypto payment API for WordPress fits sites with custom checkout logic, marketplace flows, internal account balances or a front end that should remain fully branded.
PassimPay documents two API payment flows: Host-to-Host (H2H) and Invoice Link.
1. Create the Project and Save API Credentials
Create a platform in the PassimPay dashboard and save the API Key and Platform ID. API requests must be signed, so secret credentials should remain server-side and should never be exposed in WordPress page source or browser JavaScript.
2. Choose H2H or an Invoice Link
With H2H, the server requests a payment address from the API and displays the address, amount and required network details in the site's own checkout. The customer can send any amount to the generated address, and the callback reports the amount actually received. If your WordPress order requires a fixed amount, your backend should compare the callback amount with the expected order amount before marking the order as paid.
With the Invoice Link method, the server creates an invoice and redirects the customer to a hosted payment form. This reduces front-end development while still allowing the site's backend to track payment status.
Invoice Link works differently because the invoice is created for a specific amount and reaches Paid status only after the full amount has been received. If the customer pays only part of the invoice, PassimPay sends a callback with the actual amount received and a waiting status. The merchant can either ask the customer to pay the remaining amount or credit the amount already received. If the invoice expires before it is fully paid, its status changes to error; for a partial payment, the callback still contains the amount actually received.
3. Handle Network Details Correctly
The customer must send the selected asset on the correct blockchain. USDT, for example, may be available on networks such as ERC20, TRC20 or BEP20. A payment sent to the wrong network can be difficult or impossible to recover.
Some assets also require a tag or memo in addition to the wallet address. The PassimPay API documentation specifically notes this for XRP, TON and similar networks.
4. Process Callbacks Safely
PassimPay sends callbacks after successful deposits and supports invoice-status checks. Your backend should validate the callback signature, make callback handling idempotent, prevent duplicate order updates and return HTTP 200 after successful processing. If the server does not return 200, PassimPay makes two additional attempts to resend the notification.
For BTC, LTC, DASH, Dogecoin and Bitcoin Cash, the same transaction can generate up to two webhook notifications: one after the first blockchain confirmation and another after the second. If PassimPay first detects the transaction when it already has two confirmations, only the two-confirmation webhook is sent. Use the transaction identifier and confirmation count to prevent the same payment from being credited twice.
For a production WordPress crypto payment integration, log the order ID, asset, network, crypto amount, fiat value, transaction identifier and final internal order status so finance and support teams can reconcile payments later.
Crypto Fees, Security, Volatility and Taxes
Adding a cryptocurrency plugin to WordPress is only the technical part. A production payment flow also needs rules for network fees, treasury, wallet security, KYC/AML and accounting.
Network Fees vs Payment Provider Fees
A network fee, often called gas on networks such as Ethereum, pays for blockchain processing. It is separate from the payment provider's processing fee.
The total cost can therefore include the gateway fee, blockchain network fee and, where used, a conversion or fiat-settlement fee. PassimPay publishes processing fees starting at 0.5% and currently lists a 0.2% fee for automatic stablecoin conversion. Actual commercial terms can depend on the merchant.
Hot Wallets vs Cold Wallets
A hot wallet is connected to the internet and is convenient for active treasury movements. A cold wallet keeps private keys offline and is generally better suited to funds that do not need frequent access.
Merchants should decide how much crypto should remain available for day-to-day use and how much should move to cold storage. PassimPay also lists automatic withdrawals to a cold wallet among its merchant features.
Never place a private key, seed phrase or unrestricted secret credential inside WordPress content, theme files or client-side code.
How Stablecoin Conversion Reduces Volatility
A customer may want to pay in BTC or ETH while the merchant wants to keep the received value closer to a dollar-denominated asset. Automatic conversion can convert eligible incoming balances into USDT or USDC after payment according to the provider's configured rules.
This is different from the checkout exchange rate. The checkout rate determines how much crypto the customer sends; stablecoin conversion determines what the merchant holds afterward.
Companies that mainly want to accept USDT on WordPress can also review the dedicated PassimPay USDT payment gateway. Network selection still matters because TRC20, ERC20 and BEP20 have different fees and wallet requirements.
KYC and AML Responsibilities
A payment provider can handle part of the compliance infrastructure, but it does not remove the merchant's own legal obligations. PassimPay requires business verification and states that it monitors transactions under its AML program; its support materials also state that incoming transactions are checked for AML compliance.
Its Canadian entity, NILESPAY FINANCE INC., lists FINTRAC MSB registration C100000852. An MSB registration is not the same as a banking license or a license in every country where a merchant may sell, so businesses should confirm which entity provides the service and what local rules apply.
Accounting and Tax Treatment
Crypto payment tax treatment depends on the merchant's jurisdiction. At minimum, finance teams should retain the invoice or order ID, payment date, crypto amount, network, transaction hash, exchange rate or fiat value used for accounting, provider fees, conversion details and settlement record.
Receiving crypto, converting it and later disposing of it can have different accounting or tax consequences. Before launch, confirm the treatment with a qualified tax adviser in the countries relevant to the business.
FAQ
Can I accept crypto payments on WordPress without any coding?
A WooCommerce store can accept crypto without custom code by installing a compatible payment gateway plugin. Sites without a cart can use hosted payment links or QR codes and place a normal button on a WordPress page.
Which cryptocurrencies can I accept on my WordPress site?
The available cryptocurrencies depend on the payment provider and enabled networks. PassimPay currently lists 74 cryptocurrencies and 18+ blockchains, including BTC, ETH, USDT and USDC, subject to merchant eligibility and current asset support.
Are crypto payments on WordPress reversible — do I need to worry about chargebacks?
Confirmed blockchain payments do not use the card-network chargeback mechanism and generally cannot be reversed by the sender. Merchants should still maintain a refund and dispute policy because customer refunds can be sent as separate transactions.
How much does it cost to accept crypto payments on a WordPress site?
Costs can include the payment provider's processing fee, blockchain network fees and optional conversion or settlement charges. PassimPay publishes processing fees starting at 0.5% and a 0.2% fee for automatic stablecoin conversion.
Do I need to complete KYC/AML checks to accept crypto on WordPress?
Verification requirements depend on the provider and business model. PassimPay requires business verification for merchant accounts and applies transaction monitoring under its AML program, while merchants remain responsible for any compliance duties that apply in their jurisdiction.
Does WooCommerce support crypto payments natively?
WooCommerce provides a payment-gateway framework, but cryptocurrency acceptance normally requires an additional gateway extension or custom integration. A compatible plugin adds crypto as a checkout method and connects WooCommerce order handling to the external crypto payment provider.
How fast do crypto payments settle compared to card payments?
Crypto payment timing depends on the blockchain and required confirmations. PassimPay reports about five seconds for average transaction processing, but final on-chain settlement can take longer. Card authorization may be fast while merchant settlement follows a separate schedule.
Related Reading
How to Accept Crypto Payments in a Telegram Bot
Stablecoins vs Bitcoin: Which Is Better for Business Payments?
E-commerce Plugins — ready-made PassimPay modules for WooCommerce and other supported CMS platforms.
Do you like this article? Share it with your friends.


