Why WooCommerce Doesn't Natively Accept Cryptocurrency and How to Fix It

We design and develop full-cycle blockchain solutions: from smart contract architecture to launching DeFi protocols, NFT marketplaces and crypto exchanges. Security audits, tokenomics, integration with existing infrastructure.
Showing 1 of 1All 1305 services
Why WooCommerce Doesn't Natively Accept Cryptocurrency and How to Fix It
Simple
~2-3 days
Frequently Asked Questions

Blockchain Development Services

Blockchain Development Stages

Latest works

  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1257
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1209
  • image_logo-advance_0.webp
    B2B Advance company logo design
    668
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    957
  • image_logo-aider_0.webp
    AIDER company logo development
    882
  • image_crm_chasseurs_493_0.webp
    CRM development for Chasseurs
    996

Why WooCommerce Doesn't Natively Accept Cryptocurrency and How to Fix It

In the WooCommerce core, there are no handlers for blockchain transactions, so accepting crypto requires integration. Two paths: a ready-made plugin from a processor (CoinGate, NOWPayments, Coinbase Commerce) or a custom WooCommerce payment gateway with your own wallet. The difference is in custody, fees, and control level. We use both approaches, and below we break down when each is more profitable.

Common Problems When Integrating Crypto Payments into WooCommerce and How We Solve Them

Exchange Rate Volatility and Amount Fixation

Between order creation and payment, 10–20 minutes pass—the rate can change by 2–5%. If you don't fix the crypto amount, the store risks receiving less money. Our solution: at checkout, we fetch the rate via Chainlink Oracle (or exchange API) and store the equivalent in satoshi/wei. We set an order lifetime of 15–20 minutes; after expiry, the user moves to a new one with the current rate. This reduces slippage risk to 0.1%.

Underpayment and Overpayment

Due to user errors or network delays, part of the funds may not arrive. Our handling:

Status Action
paid Full amount—order completes
underpaid Status on-hold, email to manager
overpaid Accept all, excess as bonus or refund
expired Order cancelled, funds not accepted

We also check a unique _crypto_payment_id to avoid duplicate webhook processing. Duplicate calls don't change order status if already completed. Log via WC_Logger.

How to Choose Between a Ready-Made Plugin and a Custom Gateway

Ready-made plugins (CoinGate, NOWPayments) are good for a quick start: setup takes 1–2 hours, processor fee 1–3%. However, you lose control over funds and can't change processing logic. A custom gateway gives full control: you manage the wallet, fees are only network gas ($0.01–$0.50 per transaction). With volumes over 500 orders per month, a custom solution pays off in 3–4 months and saves up to 40% on fees—2-3 times more profitable compared to ready-made plugins.

How We Do It: A Custom Gateway Case on Polygon

A client once wanted to accept USDT on Polygon with minimal fees. Ready-made plugins didn't fit—they needed their own node and custom refund logic. We developed a WooCommerce Payment Gateway that:

  • Uses ethers.js to sign transactions on the server (Node.js microservice);
  • Fixes the rate via Chainlink USDT/USD feed;
  • Generates a unique deposit address for each order;
  • Processes webhook from the node with signature verification (EIP-712).

Below is the structure of the WC_Crypto_Gateway class. Setup took 5 days; the client got 0% fees (only gas ~$0.01 per transfer) and full control.

class WC_Crypto_Gateway extends WC_Payment_Gateway {
    
    public function __construct() {
        $this->id                 = 'crypto_gateway';
        $this->method_title       = 'Crypto Payment';
        $this->method_description = 'Accept cryptocurrency payments';
        $this->has_fields         = false;
        $this->supports           = ['products'];
        
        $this->init_form_fields();
        $this->init_settings();
        
        $this->title       = $this->get_option('title');
        $this->description = $this->get_option('description');
        $this->api_key     = $this->get_option('api_key');
        
        add_action('woocommerce_update_options_payment_gateways_' . $this->id,
            [$this, 'process_admin_options']
        );
        add_action('woocommerce_api_' . $this->id, [$this, 'handle_webhook']);
    }
    
    public function process_payment($order_id) {
        $order = wc_get_order($order_id);
        
        // Create payment request via our API
        $payment = $this->create_crypto_payment([
            'amount'       => $order->get_total(),
            'currency'     => get_woocommerce_currency(),
            'order_id'     => $order_id,
            'callback_url' => WC()->api_request_url($this->id),
            'success_url'  => $this->get_return_url($order),
        ]);
        
        if (is_wp_error($payment)) {
            wc_add_notice('Payment error: ' . $payment->get_error_message(), 'error');
            return ['result' => 'fail'];
        }
        
        // Save external ID for reconciliation
        $order->update_meta_data('_crypto_payment_id', $payment['id']);
        $order->update_status('pending', 'Awaiting crypto payment');
        $order->save();
        
        return [
            'result'   => 'success',
            'redirect' => $payment['payment_url'],
        ];
    }
    
    public function handle_webhook() {
        $payload = file_get_contents('php://input');
        $data    = json_decode($payload, true);
        
        if (!$this->verify_webhook_signature($payload, $_SERVER['HTTP_X_SIGNATURE'] ?? '')) {
            status_header(400);
            exit('Invalid signature');
        }
        
        $order = wc_get_order($data['order_id']);
        if (!$order) {
            status_header(404);
            exit('Order not found');
        }
        
        switch ($data['status']) {
            case 'paid':
                $order->payment_complete($data['payment_id']);
                $order->add_order_note(sprintf(
                    'Crypto payment confirmed. Received %s %s',
                    $data['amount_received'],
                    $data['currency']
                ));
                break;
                
            case 'expired':
                $order->update_status('cancelled', 'Crypto payment expired');
                break;
                
            case 'underpaid':
                $order->update_status('on-hold', sprintf(
                    'Underpayment: expected %s, received %s',
                    $data['amount_expected'],
                    $data['amount_received']
                ));
                break;
        }
        
        status_header(200);
        exit('OK');
    }
}

Plugin Registration

// crypto-payment-gateway.php (in wp-content/plugins/)
/**
 * Plugin Name: Crypto Payment Gateway
 * Description: Custom cryptocurrency payment gateway
 * Version: 1.0.0
 * Requires Plugins: woocommerce
 */

if (!defined('ABSPATH')) exit;

add_action('plugins_loaded', function() {
    if (!class_exists('WC_Payment_Gateway')) return;
    require_once plugin_dir_path(__FILE__) . 'includes/class-wc-crypto-gateway.php';
});

How to Set Up Crypto Payments on WooCommerce

  1. Choose integration method—ready-made plugin or custom gateway. If you need non-custodial acceptance without intermediaries, go custom.
  2. Install and activate the plugin (if ready-made) or deploy your own microservice for signing transactions.
  3. Configure gateway parameters—wallet address, limits, order lifetime (we recommend 15–20 minutes).
  4. Add webhook URL in provider settings or your node. URL format: https://example.com/wc-api/crypto_gateway.
  5. Test in sandbox—pay a test order, check underpayment, expiry, duplicate webhooks.
  6. Go live—after successful testing, enable active mode. Monitor via WC_Logger.

How We Test and Guarantee Reliability

We always go through scenarios in sandbox: successful payment, expiry, underpayment, duplicate webhook, rate reset. We use WC_Logger for all events.

Stage What We Do Duration
Analysis Gather requirements, choose provider or write spec for custom 1–2 days
Implementation Code gateway, webhook, handlers 3–7 days
Testing Cover all cases in sandbox 1–2 days
Deployment Deploy to production, set up monitoring 1 day

What's Included

  • Selection and setup of payment provider (CoinGate, BTCPay Server, own node) or custom gateway development from scratch.
  • Full WooCommerce Payment Gateway class with all status support.
  • Webhook handler with HMAC verification.
  • Edge case handling: rate difference, underpayment, expiry, duplicates.
  • Gas optimization for smart contracts (using unchecked blocks, Packed structs)—cost reduction by 15–20%.
  • Integration with WC_Logger for debugging.
  • Installation and operation documentation.

Our team has 6+ years of blockchain development experience and over 40 successful payment system integrations in WooCommerce. Have a difficult case? Get a consultation—we'll find the optimal solution for your budget and timeline. Contact us for a cost estimate. Order crypto payment integration for WooCommerce, and we'll configure everything for your business.

Blockchain Infrastructure Deployment: Nodes, RPC, Indexing

Subgraph fell at 3:47 AM. By morning users saw outdated balances, transactions "hung" in the UI, support received 47 tickets in an hour. Cause: the handler in the subgraph failed on a transaction with a non-standard event log — and the entire index stopped. We have encountered such situations dozens of times. Our experience shows: blockchain infrastructure does not forgive gaps in observability. Guaranteeing uptime without multi-layered monitoring and fault-tolerant architecture is impossible. Over 8 years working with Ethereum, Polygon, and Solana, we have developed an approach that allows predictable deployment of infrastructure of any scale — from a single node to a multichain grid with dozens of subgraphs.

RPC Layer Architecture

Every dApp interaction with the blockchain goes through RPC — the JSON-RPC API provided by a node. Three options:

Managed providers — Alchemy, QuickNode, Infura, Ankr. Minimal operational costs, SLA, built-in monitoring. Limits: rate limits (Alchemy Free: 300 RU/sec), vendor lock, potential downtime during provider incidents. For most projects — the right choice at the start.

Self-owned nodes — full control, no rate limits, no third-party dependence. Cost: archive Ethereum node requires 2.5–3TB SSD, a strong server, and DevOps support. Sync from scratch on Ethereum via Geth/Nethermind — 3–7 days. Justified under high load or latency requirements.

Hybrid — self-owned node as primary, managed provider as fallback. Standard for protocols with high TVL. Proper load balancing can reduce costs by 20–30% compared to pure managed setup. Under high monthly request volume, hybrid saves significantly.

Provider Strength Limitation
Alchemy Supernode, Enhanced APIs, webhooks Expensive on high-volume
QuickNode Low latency, multi-chain More expensive than Alchemy on basic plan
Infura Historical reliability Rate limits on free, one major incident halted half of DeFi
Ankr Cheap, 40+ chains Less stable

How to Set Up an RPC Layer Without a Single Point of Failure?

At least two providers, DNS round-robin with health check every 5 seconds, automatic fallback when latency >500 ms. In practice, this gives 99.99% availability during any provider failure. For protocols with high TVL, we recommend a custom HA-proxy (nginx or Envoy) in front of two managed providers.

Why Is a Hybrid RPC Scheme More Cost-Effective Than Pure Managed?

At high request volumes, managed providers can be very expensive; a hybrid using a self-owned node as primary and a managed fallback cuts costs significantly without losing SLA.

Ethereum Node Clients

Execution clients: Geth (most used), Nethermind (C#, fast sync), Besu (Java, enterprise), Erigon (fastest sync, efficient archive mode ~2TB instead of 3TB).

Consensus clients (post-Merge): Lighthouse (Rust), Prysm (Go), Teku (Java), Nimbus (Nim). Each node after The Merge requires a pair of execution + consensus clients.

For DevOps: eth-docker — Docker Compose configurations for all client combinations. Setting up monitoring via Grafana + Prometheus is mandatory; a standard dashboard is available in each client's repository.

The Graph: Event Indexing

The Graph Protocol — decentralized indexing. A subgraph describes which events from which contracts to index and how to transform them into a GraphQL schema.

Subgraph structure:

  • subgraph.yaml — manifest: contract addresses, startBlock, events to handle
  • schema.graphql — GraphQL schema of entities
  • src/mapping.ts — AssemblyScript event handlers
dataSources:
  - kind: ethereum
    name: UniswapV3Pool
    network: mainnet
    source:
      address: "0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640"
      abi: UniswapV3Pool
      startBlock: 12370624
    mapping:
      eventHandlers:
        - event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
          handler: handleSwap

AssemblyScript handlers — not TypeScript. No nullable types, no closures, no many standard APIs. An error in the handler stops the subgraph indexing on that transaction. Important: add try-catch for operations that can fail (e.g., store.get() for an entity that may not exist).

How to Avoid Subgraph Indexing Stops?

Graph Node logs are monitored in real-time; on hasIndexingErrors = true an alert fires and an automatic node restart (via systemd or Kubernetes). Typical downtime on error — 150–300 seconds to recover. Additionally, for production we set up a watchdog that restarts Graph Node if subgraph lag exceeds 50 blocks.

Choosing Between Hosted Service and Decentralized Network

Graph Hosted Service (free, centralized) is deprecated in favor of Subgraph Studio + Graph Network. For production: deploy on Graph Network with GRT curation signal — the subgraph gets indexers proportional to curation.

Alternatives to The Graph: Ponder (TypeScript, self-hosted, easier to debug), Envio (ultra-fast indexer, supports EVM + non-EVM), Subsquid (TypeScript, own network), Moralis Streams (managed, webhook-based). Our experience shows: for high-load projects with unique logic, Ponder or Envio are more effective — they give full control over the process and do not require GRT tokenomics.

Webhooks and Real-Time Notifications

Alchemy Webhooks and QuickNode Streams allow receiving events in real-time via HTTP webhook or WebSocket. For monitoring addresses, new transactions, mints — this is faster than polling RPC.

Tenderly — platform for monitoring and alerts. You can set up an alert for a specific contract event, balance change, function call with certain parameters. Transaction simulation via Tenderly API is invaluable for debugging.

Monitoring and Observability

Minimum monitoring stack for a protocol:

On-chain: OpenZeppelin Defender Sentinel — watches contract events, triggers webhook or Autotask when conditions are met. Forta Network — community-maintained bots detect anomalies (large withdrawals, flash loans, governance attacks).

Infrastructure: Grafana + Prometheus for nodes, Datadog or Grafana Cloud for managed metrics. Alerts on: node is 10+ blocks behind, RPC latency >500ms, subgraph lag >100 blocks.

Uptime: Better Uptime or PagerDuty on RPC endpoint and subgraph health endpoint (The Graph provides _meta { hasIndexingErrors, block { number } }).

Why Is Monitoring Without Tenderly Insufficient?

Tenderly provides transaction simulation and detailed traces — critical for debugging subgraph and smart contract errors. Forta focuses on network anomalies, not your infrastructure. The combination of Tenderly plus a custom Grafana dashboard covers 90% of incident scenarios.

Multichain Infrastructure

A protocol on 5 chains = 5 separate RPC endpoints, 5 subgraphs, 5 monitoring configs. Manageable but requires deployment automation.

For subgraph multi-network deployment: graph deploy --network mainnet, graph deploy --network arbitrum-one etc. with a unified codebase and network-specific addresses in separate config files.

Chainlink CCIP and LayerZero for cross-chain messaging require monitoring of both chains and transactions on intermediate relayers. A reorg on the source chain after a confirmed mint on the target chain is a classic bridge problem. Solution: wait for finality (on Ethereum ~15 minutes after Merge for economic finality) before confirming on the target chain.

Infrastructure Setup Process

  1. Audit current stack — determine chains, request volume, latency and availability requirements.
  2. Architecture design — select providers, load balancing, redundancy.
  3. Subgraph development — manifest → schema → handlers → testing on local Graph Node → deploy to testnet → mainnet.
  4. Monitoring configuration — Tenderly alerts, Grafana dashboard, PagerDuty integration.
  5. Documentation and runbook — what to do when: subgraph falls behind, RPC downtime, node desync.
  6. Handover to operations — team training, access transfer, first month support.

What's Included

  • Deployment of managed or self-hosted Ethereum, Polygon, BNB Chain nodes
  • RPC layer setup with primary/fallback and load balancing
  • Subgraph development and deployment for your protocol
  • Monitoring connection (Tenderly, Grafana, alerts)
  • Runbook and operations documentation
  • Team training (up to 4 hours online)
  • 30-day support after delivery

Timeline

Task Duration
RPC and basic monitoring setup 1–2 weeks
Subgraph for one protocol 2–4 weeks
Self-hosted node with monitoring 2–3 weeks
Full infrastructure (multi-chain, monitoring, runbooks) 6–10 weeks

All projects are managed in a GitHub/GitLab repository with CI/CD; configuration code stays with you. Order infrastructure deployment — we'll show how to cut costs by 20–30% without losing reliability. Get a consultation — we'll demonstrate how we deployed infrastructure for a protocol with large TVL on Ethereum and Arbitrum. Contact us.