Mainnet validation is in progress. Payments and new API keys are disabled.View readiness
XMRGate
Mainnet validation · Payments temporarily gated

Crypto payments with explicit release gates. Mainnet, monitored, auditable.

XMRGate is validating hosted checkouts, transaction proofs, merchant balances and wallet payouts across XMR, ETH, USDT, SOL and USDC. Public payment creation remains disabled until each enabled rail completes a funded canary.

dashboard.xmrgate.comInterface preview

Received (30d)

No production volume yet

Confirmed TX

Canaries pending

Payment mode

Locked

Release gate active

Coin
Address
Amount
Status
Conf.
XMR
Mainnet wallet
Syncing
ETH
Mainnet verifier
Ready
USDT
ERC-20 / TRC-20
Ready
SOL
Mainnet verifier
Ready

Supported coins

Five assets. Explicit readiness per rail.

Add or remove coins per merchant. Confirmation thresholds, rotation rules, and webhooks are configured independently for each.

XMR

Monero

Mainnet node syncing

ETH

Ethereum

Mainnet verifier ready

USDT

Tether

TRC-20 / ERC-20 validation

SOL

Solana

Mainnet verifier ready

USDC

USD Coin

SPL validation

What makes XMRgate different

A payment processor that takes privacy as seriously as your customers do.

Data minimization

Payment records retain settlement and security data only. Contact forms no longer store IP addresses or browser user-agent strings.

Merchant payout controls

Set wallet destinations, payout thresholds and coin preferences from the dashboard while XMRGate handles receive-wallet monitoring.

Monero-first

Built around XMR privacy guarantees with full subaddress support, then extended to BTC, ETH and stablecoins.

REST API + webhooks

Drop-in REST endpoints, HMAC-signed webhooks, and an official TypeScript SDK. Integrate in an afternoon.

Release-gated onboarding

New payment accounts stay closed until mainnet canaries pass. Existing merchant records and API keys remain preserved during validation.

Server-side SDK

Use the public Node SDK or raw REST from your backend without exposing merchant secret keys to browsers.

How it works

From checkout to reconciled settlement.

01

Customer checks out

Your backend calls POST /api/v1/checkouts with a USD-cent amount and currency. We return a hosted pay-page URL.

02

We watch the chain

Mempool and confirmed-block monitoring across every supported network. Confirmation thresholds are per-coin configurable.

03

Webhook fires

Signed payload hits your endpoint with TX hash, USD value, and confirmation count. Up to 5 retries with backoff.

04

You fulfill the order

Verify the HMAC, unlock content, ship the product. Confirmed funds credit your merchant balance and pay out to your configured wallet.

Developer experience

One POST. A signed webhook back.

Create a checkout with a single API call. We return a unique receiving address, QR payload, expiry, and hosted pay page. When the payment confirms, your webhook gets an HMAC-signed event you can verify in three lines.

  • · Bearer-token auth, 100 req/min default rate limit
  • · TypeScript SDK and raw REST support
  • · Hosted checkout pages for every supported currency
  • · Webhook retries with exponential backoff
POST /api/v1/checkouts201 Created
curl https://xmrgate.com/api/v1/checkouts \
  -H "Authorization: Bearer xmr_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "priceUsd": 2250,
    "currency": "XMR",
    "metadata": { "orderId": "A-1042" }
  }'

{
  "id": "ck_abc123",
  "currency": "XMR",
  "payToAddress": "84Hsk…q9Lm",
  "amount": { "atomic": "150000000000", "display": "0.15" },
  "priceUsd": 2250,
  "payPageUrl": "https://xmrgate.com/pay/ck_abc123"
}

Ready to take privacy-respecting payments?

Read the integration guide while mainnet validation completes. Payment creation and new account issuance remain locked until the release gate passes.