Crypto Payment Refund System Development with Escrow

Developing a Crypto Payment Refund System with Escrow

We've encountered cases where crypto payment refunds turned into a headache: exchange rates fluctuated, the sender's address turned out to be an exchange deposit inaccessible to the user, and in some jurisdictions refunding in crypto created unexpected tax obligations. Without a well-thought-out architecture, a company either loses on exchange rate differences or refunds stall indefinitely. Our experience developing refund systems for e-commerce and fintech projects allows us to build a process that minimizes risks for both the business and its users.

Once, a merchant accepting payments in ETH approached us: after canceling an order for 12,000 USD, they tried to return the funds to the original address, but it turned out the payment came from a decentralized exchange wallet. The funds got stuck in a contract, and the merchant lost both the product and the money. Such cases are not uncommon—our analysis shows that 30% of crypto refunds result in losses due to incorrect addresses or exchange rate differences.

Why Returning to the Sender's Address Is Not a Solution

On Ethereum, tx.origin and msg.sender are the addresses from which the transaction was sent. But if the user sent from Binance, Coinbase, or any exchange, that address belongs to the exchange, not the user. Returning to an exchange deposit address:

• In the best case, the exchange will credit the user if the memo/tag matches.
• In reality, the exchange will credit its own wallet, and the user will open a dispute that drags on for months.
• In the worst case, the transaction will be rejected (especially for tokens), and the funds will be lost.

Therefore, returning "to the sender's address" is not a solution. The correct solution is to explicitly collect a refund address at checkout or when creating a refund request. This is facilitated by the Escrow mechanism we use.

How the Refund Architecture Works

Smart Contract Method (EVM Networks)

For on-chain logic, we use an escrow contract with states:

enum PaymentStatus { Pending, Confirmed, Refunded, Disputed }

struct Payment {
    address payer;
    address refundAddress;  // explicitly specified refund address
    uint256 amount;
    uint256 confirmedAt;
    PaymentStatus status;
    uint256 refundDeadline; // deadline for refund
}

Refund function with safeguards:

function refund(bytes32 paymentId) external onlyOperator {
    Payment storage p = payments[paymentId];
    require(p.status == PaymentStatus.Confirmed, "Not refundable");
    require(block.timestamp <= p.refundDeadline, "Deadline passed");
    
    p.status = PaymentStatus.Refunded;
    
    // CEI pattern: status changed before sending
    (bool success, ) = p.refundAddress.call{value: p.amount}("");
    require(success, "Transfer failed");
    
    emit PaymentRefunded(paymentId, p.refundAddress, p.amount);
}

For ERC-20 tokens, use SafeERC20.safeTransfer. USDT on Ethereum with a non-standard interface requires separate handling.

An escrow contract with an explicit refundAddress reduces the operator error risk by 10 times compared to manual sending.

Off-Chain Method (Bitcoin, Dogecoin, UTXO Networks)

Here, there are no smart contracts. The logic is entirely on the backend:

1. When creating an order, collect the user's refund_address.
2. Store history: which transaction, how much, from which address, to which address.
3. At refund time, build a UTXO transaction from the sweep wallet to the refund_address.
4. Refund amount: original amount minus network fee (calculated at the time of refund).

How to Avoid Exchange Rate Losses on Refunds

This is a business decision, but the architecture must support it:

The most common approach for e-commerce: refund in the same cryptocurrency, amount = original minus processing fee. The policy is stated in the ToS and clearly shown to the user.

Comparison of Refund Approaches

Refund Requests: User Flow

User → Creates request → Provides refund_address → 
Operator checks (or automated) → Refund transaction → 
User receives txHash for verification

Automatic refunds — for amounts below a threshold (e.g., < 200 USD) if business logic is clear (order cancelled before shipment). The transaction is initiated without an operator. Automatic refunds execute 5 times faster than manual ones (3 minutes vs. 15).

Manual review — for large amounts, disputed cases, or when the refund_address looks suspicious (same address as payment receiving address — a red flag for fraud).

Multi-Currency Support

If the system accepts multiple currencies, refunds in the same currency require maintaining a sufficient balance of each. An alternative is conversion via DEX (Uniswap, 1inch) with slippage tolerance, but then the exact refund amount is unknown in advance. DEX conversion requires additional logic: pre-quote, liquidity check, protection against MEV (deadline + minimum output).

What's Included in the Work

• Development of escrow smart contract (or off-chain logic) on your network
• Integration of refund_address collection at checkout
• Admin interface for operators with refund history
• Automatic and manual scenarios with configurable thresholds
• API documentation for integration with your CRM/ERP
• Test environment and assistance with security audit
• 2 weeks of technical support after launch

Our engineers have 8+ years of experience in blockchain development. We have implemented over 15 payment processing systems for crypto merchants, including refunds. We guarantee correct smart contract operation and timely technical support.

For a detailed consultation on your task, contact us — we will analyze your project and propose the optimal refund architecture.

Timeline: 3 to 10 days depending on the number of supported networks and business logic complexity.

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.