Non-custodial payment infrastructure

Accept crypto payments without giving up control of your funds.

Customers pay your wallet directly. LevinGate watches five chains block-by-block, matches every transfer, locks the quote at checkout, and fires a signed webhook the moment a payment is final. We never hold keys — so we can never hold your money.

Settlement fee
0% settlement fee · early access
Chains
5 chains · 1 REST API
Keys held
0 keys ever held
  1. 1Select Coin
  2. 2Pay
  3. 3Confirm

Paying

XYZ Store
25.00 USD≈ 25.00 USDT

Complete Your Payment

Choose your preferred network and coin.

Select Network
Select Coin

Expires in 29:41

Powered byLevinGate — crypto payments, simplified
  • BSC · 15 confirmations · ~3s blocks · BEP-20
  • TRON · 20 confirmations · TRC-20
  • ETHEREUM · ERC-20 · contract-verified
  • BITCOIN · UTXO · BIP-21 payment URIs
  • LITECOIN · UTXO · per-address scanning
  • USDT · BSC + TRON
  • USDC · ETHEREUM
  • QUOTES LOCKED AT CHECKOUT
  • HMAC-SHA256 SIGNED WEBHOOKS
  • NON-CUSTODIAL · 0 KEYS HELD
  • WRONG-NETWORK TRANSFERS FLAGGED, NEVER CREDITED

How it works

From invoice to webhook, in four real steps

This is the exact path every payment takes through the engine — the same states your webhook receives and your dashboard shows.

  1. 01

    Create the invoice

    One REST call with an idempotency key. The quote locks for a window at checkout, so the amount is fixed while the customer pays.

    POST /api/v1/invoices

  2. 02

    Customer pays, scanners detect

    The hosted checkout shows a QR and a per-asset address. Chain scanners watch every block and detect the transfer — typically within seconds of broadcast.

    PENDING → DETECTED

  3. 03

    Confirmations accumulate

    A payment is only PAID after the chain-specific confirmation threshold you configured. Under- and overpayments are measured against your tolerance and policy.

    DETECTED → CONFIRMING

  4. 04

    Signed webhook fires

    HMAC-SHA256 over timestamp + raw body, retried with exponential backoff until acknowledged — with full delivery history in the dashboard.

    CONFIRMING → PAID

The platform

Everything the payment needs, nothing it doesn't

Scanning, matching, quoting, checkout, notifications, reconciliation and account hardening — one platform, one integration.

Non-custodial by design

Settlement addresses are yours, verified by wallet signature where the chain allows. No keys are ever stored, no transaction is ever signed, no funds can ever be frozen.

Multi-chain engine

BNB Smart Chain, TRON, Ethereum, Bitcoin and Litecoin behind one API. Add a chain to your account and it behaves exactly like the rest.

Hosted checkout

A live payment page with locked quotes, QR codes, real-time confirmation progress and per-store branding. Or build your own on the same states.

Signed webhooks

Every state change delivered with an HMAC signature, exponential-backoff retries, manual redelivery and complete delivery history.

Reconciliation built in

Underpaid, overpaid, late, duplicate, wrong-network and reorged payments are flagged with severity and a resolution workflow — nothing slips through silently.

Developer-first API

Clean REST with idempotency keys, cursor pagination, test/live key isolation and a testnet-first environment. Your first invoice is minutes of work.

Edge cases, handled

What happens when the chain doesn't behave

Most gateways go quiet here. LevinGate records exactly what arrived, where, and why it didn't match — then hands you the recovery workflow. This is the section competitors don't have.

  • UNDERPAID

    Measured against your per-store tolerance (up to 10%). Below it: auto-acknowledged. Beyond: flagged for review, per your policy.

  • OVERPAID

    Recorded with the exact amount received — you decide the refund, directly from your wallet. We never touch the funds to make it right.

  • WRONG NETWORK

    USDT sent on Ethereum for a BSC invoice is detected on-chain, recorded with tx hash and amount — and never credited to the invoice.

  • WRONG TOKEN

    Tokens are identified by contract address, never symbol. A look-alike token transfer is flagged as wrong-asset, not credited.

  • LATE PAYMENT

    Paid after expiry? The transfer is recorded with an is_late flag and a reconciliation record. The invoice stays EXPIRED — no surprise state changes.

  • REORG

    Chain reorganizations are detected and the payment state walks back honestly, with a reconciliation record instead of a phantom PAID.

For developers

Your first invoice in minutes

Create invoices over REST from any backend, redirect to the hosted checkout, and receive signed webhooks. No frontend SDK required — and the states you subscribe to are the same ones shown on this page.

  • Idempotency keys on every write
  • Test / live key isolation — testnet first, mainnet is a deliberate switch
  • Cursor pagination on every list endpoint
  • API keys displayed exactly once, revocable per key
Open the API quickstart
create-invoice.shPOST /api/v1/invoices
curl -X POST https://api.levingate.example/api/v1/invoices \
  -H "Authorization: Bearer sk_test_…" \
  -H "Idempotency-Key: 0b9e…" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": "25.00",
    "currency": "USD",
    "metadata": { "order_id": "2026-0147" }
  }'

Your keys. Your funds. Period.

If LevinGate disappeared tomorrow, your money would be exactly where it always lands — your wallet. Custody is the risk we were built to remove, and the only way to remove it is to never have it.

Private keys and seed phrases are never stored, requested, or transmitted

Receiving addresses verified by wallet signature on EVM chains

TOTP two-factor auth and server-side session revocation

Every security-relevant action lands in an append-only audit trail

Start accepting crypto