MoonPay Integration: Buy Crypto with Card in dApp & Wallet

MoonPay Integration: Buy Crypto with Card in dApp & Wallet

Imagine: you launch a dApp, users are ready to pay, but they can't buy ETH with a card. Building your own on-ramp requires licenses, KYC, banking partnerships — 6-12 months and tens of thousands of dollars. MoonPay solves this in days: 150+ fiat currencies, 100+ cryptocurrencies, coverage in 160+ countries. MoonPay official documentation We integrate MoonPay into your project so that buying crypto with a card becomes a standard feature. Development savings — up to 90% compared to a custom solution.

Problems Solved by MoonPay Integration

Need for Own Payment Infrastructure

Building a fiat gateway from scratch — obtaining licenses (MSB, EMI), integrating with acquiring banks, setting up KYC/AML. This requires 6+ months of work by compliance and development teams. MoonPay handles all regulation: you simply send a request with a wallet address and amount.

Security Risks in Fund Transfers

Every transaction must be protected from tampering and replay attacks. MoonPay uses signed URLs (HMAC-SHA256) and webhook verification. Without this, anyone could modify transaction parameters, substituting their own wallet. Your task is to correctly implement signature verification on the server.

Uncontrolled Fees and Delays

A custom on-ramp often loses profit due to high bank transfer and conversion costs. MoonPay provides a ready model: card fee — 3.99%, transfer fee — 1.99%. For partners with volumes over $1M/month, revenue share is available. As a result, you get stable income without hidden costs.

How Does MoonPay Integration Work?

MoonPay is a white-label on-ramp provider that handles payment infrastructure. You get a widget or API, the user buys crypto with a card or transfer, and the funds arrive at your smart contract or wallet. All this in hours, not months. Turnkey MoonPay integration includes setting up signed URLs and webhooks for full automation.

Why MoonPay Instead of a Custom Gateway?

MoonPay is a proven provider with experience in major projects (OpenSea, MetaMask, Trust Wallet) and 99.9% uptime. We have experience integrating MoonPay in 20+ projects, including DeFi platforms and NFT marketplaces. Compared to a custom gateway, MoonPay reduces implementation time by 10x and eliminates regulatory headaches. Development savings — up to 90%.

How We Do It?

We connect the widget or SDK, configure signed URLs and webhooks. Example React component:

import { MoonPayProvider, MoonPayBuyWidget } from '@moonpay/moonpay-react';

function CryptoPurchaseModal({ walletAddress, currency = 'eth' }) {
  return (
    <MoonPayProvider
      apiKey={process.env.MOONPAY_API_KEY}
      debug={process.env.NODE_ENV === 'development'}
    >
      <MoonPayBuyWidget
        variant="overlay"
        baseCurrencyCode="usd"
        baseCurrencyAmount="100"
        defaultCurrencyCode={currency}
        walletAddress={walletAddress}
        onLogin={() => console.log('user logged in')}
        onTransactionCompleted={(txData) => {
          // txData.status: "completed" | "failed" | "pending"
          handleTransactionComplete(txData);
        }}
        visible={true}
      />
    </MoonPayProvider>
  );
}

Signed URLs for Security

MoonPay requires URL signing to prevent parameter tampering (wallet address, amount). Signature generation in Python:

import hmac
import hashlib
import urllib.parse
import base64

def sign_moonpay_url(base_url: str, secret_key: str) -> str:
    """Signs a URL for MoonPay widget"""
    parsed = urllib.parse.urlparse(base_url)
    query = parsed.query
    signature = hmac.new(
        secret_key.encode(),
        query.encode(),
        hashlib.sha256
    ).digest()
    sig_b64 = base64.urlsafe_b64encode(signature).decode().rstrip('=')
    separator = '&' if query else '?'
    return f"{base_url}{separator}signature={sig_b64}"

# Usage
url = f"https://buy.moonpay.com?apiKey={API_KEY}&currencyCode=eth&walletAddress={wallet}"
signed_url = sign_moonpay_url(url, MOONPAY_SECRET_KEY)

Webhooks

MoonPay sends webhook notifications when transaction status changes. Signature verification is mandatory:

from fastapi import FastAPI, Request, HTTPException
import hmac, hashlib

@app.post("/webhooks/moonpay")
async def moonpay_webhook(request: Request):
    signature = request.headers.get("MoonPay-Signature-V2")
    body = await request.body()
    expected = hmac.new(
        MOONPAY_WEBHOOK_SECRET.encode(),
        body,
        hashlib.sha256
    ).hexdigest()
    if not hmac.compare_digest(f"sha256={expected}", signature):
        raise HTTPException(403, "Invalid signature")
    event = await request.json()
    if event["type"] == "transaction_updated":
        tx = event["data"]
        await process_transaction_update(
            external_id=tx["externalTransactionId"],
            status=tx["status"],
            crypto_amount=tx.get("cryptoTransactionId")
        )
    return {"received": True}

Typical Integration Mistakes

• Storing secretKey and webhookSecret in plaintext in client-side code. Use server environment variables.
• Missing webhook signature verification, leading to fake notifications.
• Incorrect handling of transaction statuses: not all statuses are final (e.g., "pending" may change).

We help avoid these risks at the design stage. Order turnkey MoonPay integration — we'll prepare everything in 1–2 weeks. We'll assess your project for free.

What's Included?

• Selection of the optimal integration method (widget/SDK/API)
• Setup of API keys, secrets, and webhook handlers
• Implementation of signed URLs and transaction verification
• UI customization to match your design
• Integration documentation and testing instructions
• Warranty and support after deployment

Estimated Timelines

Cost is calculated individually based on complexity and scope. For an accurate estimate, contact us — we'll propose a solution for your project.

MoonPay on Wikipedia

Why exchange development requires deep domain expertise

We develop exchanges — not 'chart sites,' but matching engines that process thousands of orders per second without delay, route liquidity between pools, and guarantee that no user gains access to others' funds. Teams that start with the UI and postpone the engine 'for later' end up rewriting everything in six months in 90% of cases.

Order Book vs AMM: where most projects break

Centralized exchanges (CEX) are built around an order book + matching engine. Decentralized exchanges (DEX) either also use an order book (dYdX on StarkEx, Serum/OpenBook on Solana) or an AMM with concentrated liquidity (Uniswap v3/v4, Curve, Balancer). A classic mistake when developing a CEX is implementing the matching engine on top of a relational database with transactions for each match. PostgreSQL handles ~500 RPS without special effort, but at peak loads of 5,000–10,000 orders per second, it turns into a deadlock nightmare. The correct architecture: in-memory order book (Redis Sorted Sets or custom C++/Rust structure), asynchronous writing of matches to PostgreSQL via a queue (Kafka/RabbitMQ), and a separate settlement service that finally updates balances.

For DEX, the most painful problem is sandwich attacks and MEV. A pool with a plain xy=k AMM without slippage protection becomes a target for MEV bots within hours of launch. Uniswap v2 lost hundreds of millions of dollars in user liquidity. Solutions: integration with Flashbots Protect, a commit-reveal scheme for orders, or switching to TWAMM (Time-Weighted AMM) for large trades.

Concentrated liquidity and impermanent loss

Uniswap v3 introduced concentrated liquidity – LPs choose a price range in which to provide liquidity. Capital efficiency increased 4,000x compared to v2 for stable pairs. But implementing this mechanism correctly is non-trivial. The Uniswap v3 liquidity contract uses tick-based accounting: the price space is divided into discrete ticks (tick = log₁.0001(price)), each tick stores accumulated fee growth and liquidity delta. When creating a position, the lower and upper ticks are computed, and the contract recalculates all active positions at each swap. Storage layout is critical here – incorrect variable packing in slots easily adds 40–60% to swap gas cost.

We implemented a Uniswap v3 fork for a client on Polygon with a custom fee tier system. The initial version consumed 180k gas for a swap across 2 ticks. After slot packing of variables in Tick.Info and inlining several internal calls, it dropped to 112k gas. This reduced gas costs by 38% and saved the client substantial costs on fees monthly. The techniques applied are described in the Uniswap v3 Whitepaper and confirmed by our audit experience.

How a matching engine delivers performance

A production-ready matching engine is built according to the following scheme:

• Order ingestion layer – WebSocket gateway (Go or Rust), accepts orders, validates signature, checks balance via Redis, queues them. Latency at this level must be <1ms.
• Matching core – single-threaded event loop (eliminates race conditions without mutexes). In memory, we hold two Sorted Sets for each trading instrument: bids and asks. FIFO matching for limit orders, immediate-or-cancel for market orders. Throughput with a proper Rust implementation – 500k–1M matches per second on a single core.
• Settlement service – reads matches from Kafka, atomically updates balances in PostgreSQL (UPDATE accounts SET balance = balance - $1 WHERE id = $2 AND balance >= $1). Optimistic locking via row versioning.
• Withdrawal pipeline – separate service with cold/hot wallet architecture. The hot wallet holds 5–10% of total deposits, the rest is cold storage with multi-sig (Gnosis Safe or custom HSM). Automatic withdrawals only from hot wallet, large amounts require manual authorization.

How our exchange development process ensures reliability

Smart contracts and gas optimization

For EVM-based DEX (Ethereum, Arbitrum, Optimism, Polygon), the entire critical path lives in Solidity. Main contracts: Pool, Factory, Router, PositionManager (for v3-like), and Quoter for off-chain calculations. Typical mistakes we see in audits:

Reentrancy via callback. Uniswap v3 uses flash swap with a callback (uniswapV3SwapCallback). If your router lacks a nonReentrant guard and you don't check msg.sender == pool, the contract gets drained via a nested call. This is not hypothetical – several v3 forks lost funds this way.

Oracle manipulation in AMM. If your contract uses the spot price from the pool for collateral calculation, it is front-runnable. Correct: TWAP over 30+ minutes (Uniswap v3 OracleLib) or an external oracle (Chainlink).

Unbounded loops in liquidity range. If a swap crosses many ticks in a row (price impact 80%+), gas may exceed the block limit. Need MAX_TICKS_CROSSED with partial fill and returning the remainder.

For Solana DEX (Anchor framework, Rust), the architecture is fundamentally different: account-based model, Program Derived Addresses (PDA) instead of storage, Cross-Program Invocations instead of internal calls. Solana's throughput (~3,000–4,000 TPS vs 15–30 on Ethereum mainnet) allows building on-chain order books – exactly what Phoenix DEX does.

Liquidity bootstrapping and aggregator integration

Launching a pool is not enough – you need to ensure liquidity at launch. Practical mechanisms:

• Liquidity Bootstrapping Pool (LBP) – initial price is high, asset weights dynamically shift, creating selling pressure and even token distribution. Implemented in Balancer v2.
• Initial Liquidity Offering via Uniswap v3 – adding liquidity in a narrow range around the initial price, then gradually expanding as volume grows. Requires active liquidity management or integration with Arrakis/Gamma.
• Integration with 1inch, Paraswap, Li.Fi – aggregators bring traffic but require standard compliance: the pool must have correct getAmountsOut, support ERC-20 approval/permit, and not have custom transfer hooks that break the aggregator's routing.

Development process and deliverables

Analytics and design begin with choosing the architectural model: CEX with custodial storage, non-custodial DEX, or hybrid (off-chain order book + on-chain settlement, like dYdX v3). This decision determines everything – regulatory load, tech stack, team.

Development proceeds in layers: first smart contracts with full Foundry coverage (fuzzing, invariant testing), then backend services, then integration layer, and finally frontend. Testing includes fork testing on mainnet via Foundry – we reproduce real liquidity conditions, not synthetic ones.

Audit is mandatory before mainnet deployment. For DEX contracts, minimally one firm with manual review (Trail of Bits, Spearbit, Code4rena contest). For CEX custody, audit of key storage processes. We guarantee all contracts undergo formal verification and fuzzing testing (Echidna, Foundry invariant).

Estimated timelines

Cost is calculated individually after a technical briefing: chain selection, throughput requirements, custodial model. Our certified engineers with 10+ years of experience will help you choose the optimal architecture and avoid common pitfalls. Contact our team for a detailed proposal.

Pitfalls to avoid at launch

• Forgetting the price oracle in AMM. Spot price can be manipulated with a flash loan in one transaction. If your lending protocol uses the spot price from its own pool, that's a bug.
• Hot wallet without limits. A CEX without daily limits on automatic withdrawals is an invitation for attackers. Compromising one key should lose at most 10% of total funds.
• Absence of circuit breaker. A 40% price drop in 5 minutes should halt automatic liquidations or withdrawals until manual review. Without this, a cascading liquidation spiral destroys all TVL.
• Incorrect decimal handling. USDC uses 6 decimals, WBTC – 8, most tokens – 18. Mixing without normalization leads to either precision loss or overflow. Solidity has no float; we work with fixed-point using FullMath (mulDiv with overflow protection).

Want to avoid these problems? Get a consultation — we will select the architecture for your project and provide exact timelines. Order exchange development with quality guarantee and ongoing support.