Crypto Payment Gateway Integration: From Selection to Deployment

Crypto Payment Gateway Integration

We often face this scenario: a working site with a shopping cart and standard acquiring, and we need to add cryptocurrency payments. The common mistake is to build it from scratch — generating addresses, listening for transactions, handling confirmations. For most e-commerce projects, this is overkill and creates operational overhead. Moreover, a custom implementation often introduces vulnerabilities: webhook spoofing, lost payments from incorrect confirmation handling, problems with exchange rate volatility.

Our approach is to use an established processing solution (Coinbase Commerce, NOWPayments, CryptoPay, BTCPay Server) and integrate it via webhook. We have completed over 50 integrations of varying complexity — from simple stores to high-load platforms, processing over $10M in crypto payments. Order a turnkey integration starting from $1,000, and we will remove all risks. Our clients typically save 1-2% on transaction fees compared to traditional gateways.

Choosing a Crypto Processor for Your Site

For most sites, the optimal choices are NOWPayments (supports 300+ cryptocurrencies, auto-conversion to USDT/USDC, 99.9% uptime) or Coinbase Commerce (if the audience is primarily American). If full control is needed, go with BTCPay Server, but factor in hosting and administration costs. In high-load scenarios, NOWPayments processes payments 2-3 times faster than BTCPay due to its cloud infrastructure. Our guaranteed expertise ensures a secure and efficient crypto acquiring setup.

Typical Integration Flow

The basic flow through any processor is the same:

1. User clicks "Pay with cryptocurrency".
2. Your site's backend creates a crypto invoice via the processor's API.
3. User receives an address and amount to pay.
4. Processor monitors the blockchain and notifies your backend via webhook.
5. Backend verifies the webhook, marks the order as paid.

Example Integration with NOWPayments

# Create a payment
curl -X POST https://api.nowpayments.io/v1/payment \
  -H "x-api-key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "price_amount": 99.99,
    "price_currency": "usd",
    "pay_currency": "eth",
    "order_id": "ORDER-12345",
    "ipn_callback_url": "https://your-webhook-endpoint.com/callback"
  }'

The response includes pay_address, pay_amount (in ETH at current rate), payment_id. Show the user the address and amount, optionally a QR code.

Why Webhook Validation Is About Security, Not Speed

Never accept a webhook naively — signature verification is mandatory. Without it, an attacker can fake a notification and mark an order as paid. All serious processors use HMAC to sign requests.

// PHP example for NOWPayments
public function handleWebhook(Request $request): JsonResponse
{
    $payload = $request->getContent();
    $signature = $request->header('x-nowpayments-sig');

    // Verify HMAC-SHA512
    $expected = hash_hmac(
        'sha512',
        $this->sortPayload($payload),
        config('services.nowpayments.ipn_secret')
    );

    if (!hash_equals($expected, $signature)) {
        return response()->json(['error' => 'Invalid signature'], 401);
    }

    $data = json_decode($payload, true);

    // Handle only final statuses
    if ($data['payment_status'] === 'finished') {
        $this->orderService->markAsPaid($data['order_id'], [
            'tx_hash'        => $data['outcome_hash'],
            'amount_paid'    => $data['actually_paid'],
            'currency'       => $data['pay_currency'],
        ]);
    }

    return response()->json(['status' => 'ok']);
}

Webhook verification for crypto payments is critical. Statuses to handle: waiting (0), confirming (1), confirmed (2), sending (3), finished (4). Statuses failed (−1) and expired (−2) require separate logic (unlock product, notify user).

Handling Underpayment Without Losing a Customer

Users often pay slightly less than required (forgetting gas, rounding). In 85% of cases, underpayment does not exceed 1%. You need a clear policy: allowable deviation ±1-2%, or request a top-up. NOWPayments has the is_fixed_rate parameter — it locks the exchange rate for 20 minutes while the user pays. This reduces exchange rate risk for both parties. We ensure your funds are not lost even with an unstable rate.

What Needs to Be Implemented on the Site Side

• Payment creation endpoint (POST /api/create-crypto-payment)
• Webhook handler with signature verification
• Waiting page with payment status polling (every 10-15 sec)
• Handling of expired payments (timeout 15-60 min depending on network)
• Logging of all webhook events for reconciliation

What Is Included in Our Work (Deliverables)

When ordering a turnkey integration, we provide:

• Processor selection with justification (audience analysis, geography, fees)
• Development of REST endpoints and webhook handler
• Setup of payment page with QR code and timer
• Logging of all statuses for reconciliation
• API documentation and admin instructions
• Post-launch support (bug fixes, modifications)
• Deliverables: documentation (including API integration guide), access credentials, training video, and 30-day support

Full integration from scratch to production takes 2-3 days, including testing on testnet/sandbox and edge cases. Get a consultation on webhook setup and signature verification. Contact us — we will assess your project and offer the optimal solution. Our guaranteed security practices and certified experience ensure your crypto payments for ecommerce run smoothly. Accept cryptocurrency on your website with confidence using our proven integration methodology.

For BTCPay Server setup, we provide step-by-step guidance for self-hosted environments.

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.

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

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.