Get paid in USDT and USDC, straight to your own wallet.

Payers pay from any exchange or wallet. VoltPay watches the chain and tells your server. It never holds your money.

VoltPay can’t move your money.

Never asked for

  • seed phrase
  • private key
  • approve
  • permit
  • allowance
  • wallet signature

All it asks for

How the non-custodial model works

One POST, one redirect, one Callback

  1. Your server asks for a Checkout

    One request, with your reference and the amount.

    the Checkout’s link
  2. The Payer pays on VoltPay’s page

    From an exchange, a wallet or a QR code, straight to your address.

  3. Your server is told

    A signed Callback, retried for three days.

    a signed Callback

Build your first CheckoutAPI reference

Let your AI coding agent integrate VoltPay.

One MCP server, two tools

  • searchFinds anything about the API and how to integrate it.No key needed
  • executeCalls the Merchant API with your key.Your key is never stored

Two tools take little of your agent’s context. Neither can move funds.

https://mcp.voltpay.space/mcp

Your coding agent

Claude Code: Run in your project

claude mcp add --transport http voltpay https://mcp.voltpay.space/mcp --header "Authorization: Bearer $VOLTPAY_API_KEY"

Codex: ~/.codex/config.toml

[mcp_servers.voltpay]
url = "https://mcp.voltpay.space/mcp"
bearer_token_env_var = "VOLTPAY_API_KEY"

Cursor: .cursor/mcp.json

{
  "mcpServers": {
    "voltpay": {
      "url": "https://mcp.voltpay.space/mcp",
      "headers": {
        "Authorization": "Bearer ${env:VOLTPAY_API_KEY}"
      }
    }
  }
}

Add to Cursor

Antigravity: ~/.gemini/config/mcp_config.json

{
  "mcpServers": {
    "voltpay": {
      "serverUrl": "https://mcp.voltpay.space/mcp",
      "headers": {
        "Authorization": "Bearer gw_test_YOUR_KEY"
      }
    }
  }
}

OpenCode: opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "voltpay": {
        "type": "remote",
        "url": "https://mcp.voltpay.space/mcp",
        "oauth": false,
        "headers": {
          "Authorization": "Bearer {env:VOLTPAY_API_KEY}"
        }
      }
    }
  }
}

Set VOLTPAY_API_KEY to a gw_test_ key while you integrate.

Then give your agent this

Integrate VoltPay into this backend, using the VoltPay MCP server. 1. Search first. Use the search tool to read how Checkouts, the redirect and Callbacks work. Do not guess a field name. 2. Where an order is placed, create a Checkout with POST /v1/checkouts: the order's id as "reference", its total as a decimal string in "amount", and an Idempotency-Key. Store the Checkout's "id" with the order and redirect the Payer to its "url". 3. Add a Callback handler. Verify the Gateway-Signature header against the raw body with my signing secret, answer 2xx at once, and mark the order paid only when data.payment.status is "confirmed". Credit each Payment once, by its id. 4. Show BALANCE_EXHAUSTED, NO_ADDRESS_FOR_PAIR, PAIR_AT_CAPACITY and PAIR_PAUSED as "payment method unavailable", not as an error page. 5. Use my gw_test_ key until it all works. Use the execute tool to create a test Checkout and read it back. Read every secret from the environment and never write one into the code. Show me the plan before you change any file.

The MCP server in the docs

Two ways to tell payments apart

Two or more addresses

Each Checkout gets its own address. The Payer sends the exact amount.

One address

Each Checkout gets a Unique Amount. Its third and fourth decimals name the order.

Two or more addresses per Pair work best. How matching works

USDT and USDC on five Networks

  • TRON

    USDT

  • Ethereum

    USDTUSDC

  • BNB Smart Chain

    USDTUSDC

  • Solana

    USDTUSDC

  • Arbitrum

    USDTUSDC

Coming later

  • Base
  • Polygon
  • Optimism
  • Avalanche

Contracts, decimals and confirmation times

2.1%of what arrives on each confirmed Payment

No monthly fee. Test mode is free.

The Prepaid Balance is never refundable and never withdrawable. You top it up with a Recharge in USDT or USDC, credited 1:1.

How the Fee and a Recharge work

Can VoltPay freeze or reverse a payment?

No. It has no key to the Payer’s wallet or to yours.

What if a Payer sends the wrong amount?

A small difference still completes the Checkout. A larger one waits for you to match by hand. Either way, the money is already in your wallet.

What if my server is down?

Each Callback is retried for three days, and the API lists every Payment.

What if the Prepaid Balance runs out?

New live Checkouts are refused until you Recharge. Payments already on their way still confirm.

Start in Test mode. Go live when your code works.

Start in Test mode
  1. Sign up with an email
  2. Paste a Receive Address
  3. Take a test payment
  4. Add an authenticator, go live

A new live account starts at

per Checkout
1,000 USD
Checkouts an hour
60
API requests a minute
300

How the limits rise