Shadow Software Crypto for WooCommerce

Shadow Software Crypto for WooCommerce lets your store accept cryptocurrency straight to

your own wallets — no payment processor, no account, no fees, and no private keys

on your server. You enter your own receiving addresses; customers pay them

directly and the plugin watches the blockchain with free, public tools, only

marking an order paid once the payment is confirmed on-chain.

Supported payments:

• Ether (ETH) — native ETH on Ethereum, Base, Arbitrum One, and OP Mainnet.

• USDC and USDT — the leading dollar stablecoins, as ERC-20 tokens on those

same networks (whichever are deployed there).

• Bitcoin (BTC) — native BTC on the Bitcoin mainnet.

This plugin is completely free and open source. It is built and maintained by

Shadow Software.

Documentation and source code

The plugin is developed in the open on GitHub, and the project README is its full

documentation — the security model, every supported asset and network, the

external services it contacts, and how to build and test it yourself.

• Documentation: https://github.com/shadow-software/crypto-for-woocommerce#readme

• Source code and releases: https://github.com/shadow-software/crypto-for-woocommerce

• Report a bug or request a feature: https://github.com/shadow-software/crypto-for-woocommerce/issues

How it works

• The merchant enters their own receiving addresses (one EVM address for

ETH/USDC/USDT, and a Bitcoin address for BTC) and picks which assets to accept.

• The customer places the order and, on the pay page, chooses which crypto to pay

with. The order total is converted from your store currency to that crypto at

the live market rate and locked in.

• The pay page shows the exact amount, your address, and a scannable QR code. The

customer pays from their own wallet.

• The customer confirms by entering the wallet address they paid from (and,

optionally, the transaction ID — which is fastest).

• A background job checks the blockchain and completes the order once the payment

has enough confirmations. The customer’s page updates automatically.

Why merchants like it

• Self-custodial. Funds go straight to your wallets. The plugin never holds

money and never sees a private key.

• No fees, no middleman, no account. There is no gateway service to sign up

for and nothing takes a cut.

• Free tools only. Confirmation uses free public RPC nodes (EVM) and free

public block explorers (Bitcoin); the exchange rate uses a free public price

API. You can point any network at your own endpoint if you prefer.

• On-chain verified. An order is completed only after the exact payment is

found on-chain with the confirmations you require — never from the browser

alone. Each payment is bound to the buyer’s own wallet and to a unique amount,

so one payment can never settle two orders.

• Multi-asset, multi-network. ETH, USDC, USDT across Ethereum, Base, Arbitrum

One and OP Mainnet, plus native Bitcoin — each individually toggleable.

• Address safety. Your receiving address is checked (including its EIP-55

checksum) when you save it, so a typo can’t silently send funds nowhere.

• HPOS compatible and works with both the classic checkout shortcode and the

WooCommerce Checkout block.

• Translation-ready.

What this plugin is not

It does not custody funds, provide refunds on-chain, or swap/convert between

currencies. It confirms native ETH, USDC, USDT and BTC payments to your own

addresses and marks the order paid. Because payments are on-chain and

irreversible, treat confirmed orders like cash.

External services

This plugin connects to a small number of free, third-party services to price

orders and to confirm payments on the blockchain. No account or API key is

required for any of them. Here is exactly what is contacted, when, and what data

is sent.

1. com)

• What it is for: converting your store-currency order total into the amount

of the chosen crypto (ETH, USDC, USDT or BTC) using the live market rate.

• When it is called: when a customer chooses which crypto to pay with (results

are cached briefly to minimise requests).

• What is sent: only the request itself — the coin id ( ethereum, usd-coin,

tether or bitcoin ) and your store currency code (for example usd ). No

personal data, no order details, and no customer information are sent.

• CoinGecko API Terms of Service: https://www.coingecko.com/en/api_terms

• CoinGecko Privacy Policy: https://www.coingecko.com/en/privacy

2. Public Ethereum RPC nodes (by default the free PublicNode endpoints:

com,

com)

• What it is for: reading the EVM blockchains to find and confirm a customer’s

ETH, USDC or USDT payment (the transaction, its receipt and event logs, block

data, the chain id, and the current block height).

• When it is called: after a customer submits an EVM payment, on a background

schedule, until the payment is confirmed or the payment window expires.

• What is sent: standard read-only JSON-RPC queries containing the customer’s

submitted transaction hash and/or wallet address and your store’s receiving

address — all of which are already public information on the blockchain. No

private keys are ever sent, and no data is ever written to the blockchain by

this plugin.

• You may replace these defaults with your own RPC endpoint for any network on

the settings screen.

• PublicNode Terms of Service: https://www.publicnode.com/terms

• PublicNode Privacy Policy: https://www.publicnode.com/privacy

3. space and, as a fallback,

info — used only when Bitcoin is enabled)

• What it is for: reading the Bitcoin blockchain to find and confirm a

customer’s BTC payment (a transaction, an address’s transactions, and the

current block height).

• When it is called: after a customer submits a Bitcoin payment, on a

background schedule, until the payment is confirmed or the payment window

expires.

• What is sent: standard read-only REST requests containing the customer’s

submitted transaction id and/or wallet address and your store’s Bitcoin

address — all already public information on the blockchain. No private keys are

ever sent, and nothing is written to the blockchain.

• You may replace these defaults with your own Esplora-compatible explorer URL on

the settings screen.

• mempool.space Terms of Service: https://mempool.space/terms-of-service

• mempool.space Privacy Policy: https://mempool.space/privacy-policy

• Blockstream Privacy Policy: https://blockstream.com/privacy/

If you configure a custom RPC or explorer endpoint, the same read-only queries are

sent to the provider you choose, subject to that provider’s own terms and privacy

policy.

Privacy

This plugin does not create user accounts, does not set cookies, and does not

send any personal data to Shadow Software or to any external service. To price

and confirm a payment it stores, on the order itself, the asset and network, the

amount owed, the wallet address the customer says they paid from, and the

confirmed transaction id. These are kept with the order as its payment audit

trail (and, being on-chain data, are already public). No order or customer data

is transmitted to the third-party services listed above beyond the read-only

blockchain queries described there.

Full policies for the plugin’s author, Shadow Software LLC:

• Terms: https://shadowsoftware.com/terms

• Privacy Policy: https://shadowsoftware.com/privacy