What Vaze earns you

One-tap payment

Players pay without leaving your site

They pick their wallet, confirm with one tap, done. No copying addresses, no extra page.

New depositnow

250 USDT · from Trust Wallet

Accept payments in right on your platform.

Read the docsApply for access
More deposits with one-tap payment, money always in cold custody, and an integration measured in days, not months.

Sandbox access as soon as you're approved

Integration in days, not quarters

5

integration endpoints

4 h

business-hour withdrawal commitment

0

treasury keys on servers

Integration in days, not quarters

Your team builds against our sandbox as soon as we approve your application. We supply the cashier.

An OpenAPI spec, a testnet sandbox and a mock server that answers like production. The cashier is an iframe.

This is everything the operator builds on its side:

Five endpoints. That is the whole integration.

operator-api
POST /wallet/credit              credit a confirmed deposit
POST /wallet/lock                check and reserve balance
POST /wallet/lock/{id}/commit    confirm the debit
POST /wallet/lock/{id}/release   return the balance
GET  /wallet/balance/{playerId}  total and withdrawable balance

The money can only go to your treasury

If your payment provider is breached, does your money go with it? With Vaze the answer is no, and not because of trust: because of architecture.

On TRON and Ethereum every player deposits into a contract of their own that can only send to the operator's treasury. On Bitcoin, addresses derive from that treasury's public key. Neither an attacker nor we can redirect a deposit.

Withdrawal queue3 pending

  • wd_8213

    0.04120000 BTC

    Bitcoin · 12 minTo approve

  • wd_8211

    480.00 USDT

    TRON · 34 minTo sign

  • wd_8207

    3,900.00 USDT

    Ethereum · 1 h 05To sign

Withdrawals are not instant. A person signs them on a hardware device, within 4 business hours. A provider that pays instantly keeps the keys to your money on an internet-connected server. We prefer to be predictable.

You can reconcile our books every day

Most payment providers are a black box. We give you the endpoint to audit us.

An immutable double-entry ledger: nothing is edited or deleted. Automatic reconciliation against real on-chain balances; if it doesn't match, withdrawals stop on their own until a person reviews.

Daily reconciliationBalanced
  • Deposit detected+0.04120000 BTC
  • Swept to cold custody−0.04120000 BTC
  • Credited to operator+0.04120000 BTC
On-chain balance0.04120000 BTC
GET /v1/reconciliation/daily

Advantages

What your operation gains

Built so players deposit more and your team works less.

One-tap payment

Players pay from MetaMask, TronLink or any WalletConnect wallet, without copying addresses. More deposits, fewer mistakes, fewer support tickets.

In the player's language

Cashier in English, Spanish and Portuguese. You choose which to offer and which opens by default.

Each button, its own window

Your Deposit button opens only deposits and your Withdraw button only withdrawals. A cashier that feels part of your site.

Compliance built in

Every address is checked against the OFAC sanctions list, and you get multi-account signals to decide welcome bonuses.

Bonuses untouched

Your promo code travels with every deposit, and your platform decides the withdrawable balance. Your rollover rules stay yours.

Optimized network fees

On Ethereum we sweep funds when gas is cheap, and on Bitcoin confirmations scale with the amount: small deposits credit fast, large ones wait as long as they should.

Professional operation

Real-time alerts, encrypted daily backups off the main provider, and a panel with history, player detail and invite-only users.

Service models

Two ways to work with Vaze

You choose the model when you open your account. In both, funds sit in cold custody and a person signs every withdrawal.

Self-custody

You hold custody

Connect your own cold wallet, a Ledger for example. Deposits land in your treasury and you sign the payouts.

  • Vaze never holds a key that can move your money
  • You control every payout from your device
  • Best if you already run your own treasury
Managed custody

Vaze holds custody

If you'd rather not run the signing, we do it, with cold custody and manual signing within 4 business hours.

  • No devices or signing process on your side
  • Daily reconciliation you can audit
  • Best for launching fast

The only key on our servers belongs to a fee wallet that pays network gas. It cannot move player funds.

Flow

How it works

Four steps between a player's deposit and a signed withdrawal. Each leaves a record you can read.

  1. 1

    The player opens the cashier

    The cashier loads inside your platform with a single-use session token. Nothing about the player is stored in the browser.

  2. 2

    We watch the chain

    Each player has their own deposit address. We follow the transaction up to the confirmations that network requires.

  3. 3

    We credit through your API

    Once confirmed we call your Wallet API with an idempotency key. If your system doesn't answer we retry, and a deposit is never credited twice.

  4. 4

    A person signs the withdrawal

    The request reaches the panel with amount, asset and destination. We check the withdrawable balance with you, it is signed on a hardware device, and the player sees the transaction link.

Operator signing a withdrawal on a hardware device

Security

What actually protects the money

Written for your security team to verify, not to take on faith.

Deposits that can only reach your treasury
On TRON and Ethereum each deposit address is a contract bound to your treasury. On Bitcoin, it derives from its public key. A deposit cannot be redirected.
No treasury keys on servers
The treasury lives in a cold wallet. Our servers hold only a fee wallet, which pays gas and cannot touch player money.
Every movement is idempotent
Money calls carry an Idempotency-Key and are signed with HMAC-SHA256. A retry returns the original result, never a second movement.
Two factors on every approval
Operators sign in with a password and a TOTP code, and every withdrawal approval asks for a fresh code.
Reconciliation with an automatic brake
The ledger is compared against real on-chain balances. If it doesn't match, withdrawals stop until a person reviews.
Sanctions and new addresses
Every address is checked against the OFAC list, and the first withdrawal to a new address waits 24 hours.

Designed to the controls a SOC 2 Type II audit requires. We don't claim a certificate we haven't completed.

Getting live

From application to production

No calls in the way: the path a team that already models player balance takes with us.

  1. 1

    Application and approval

    You fill in the access form with your operation's details. We review it and let you know by email.

  2. 2

    Sandbox and documentation

    Once approved you get your sandbox account, your credentials and the full documentation.

  3. 3

    Five endpoints and an iframe

    Your team implements credit, lock, commit, release and balance, and tests real deposits and withdrawals on testnet.

  4. 4

    Custody and go-live

    You choose the custody model, connect your treasury or we open ours, and we open the cashier to your players.

Embedded

One line in your platform

The cashier embeds in your platform as an iframe, in the player's language.

index.html
<iframe src="https://cashier.payvaze.com/w/{session_token}"
        width="100%" height="640" frameborder="0"></iframe>

Coverage

What we support today

The real state of each network, with nothing announced ahead of time.

AssetNetworkStatus
BTCBitcoinLive
USDTTRON (TRC-20)Live
USDTEthereum (ERC-20)Live

Comparison

How it differs from a typical crypto processor

Only the differences that change your risk. No made-up scores or benchmarks.

Custody of funds
VazeYour cold wallet, or ours, cold
Typical processorThe provider's hot wallet
Where a deposit can go
VazeOnly to your treasury
Typical processorWherever the provider decides
Withdrawal
VazeSigned by a person within 4 business hours
Typical processorInstant and automated
Accounting
VazeDouble-entry ledger with a daily endpoint
Typical processorMonthly statement
Integration surface
VazeFive endpoints and an iframe
Typical processorFull cashier replacement
Bonuses and rollover
VazeStay on your platform
Typical processorDuplicated at the provider

Developers

Built for whoever integrates it

A published spec, a testnet sandbox, signed calls and actionable errors.

Two engineers reviewing the integrationRead the docs

OpenAPI specification

Versioned. Generate your client instead of transcribing a PDF.

A real sandbox

TRON, Ethereum and Bitcoin testnets behaving like production, failures and timeouts included.

HMAC-SHA256 signatures

Over method, path, timestamp, nonce and raw body, in both directions. You implement it once.

Actionable errors

Every failure returns a code, a readable message and a requestId to quote when you write to us.

webhook
POST https://your-platform.com/wallet/credit
x-cashier-key-id: vaze
x-cashier-timestamp: 1760277605
x-cashier-nonce: 2f1c6a0e-8b7d-4c1e-9a3f-5d2b7e9c1a40
x-cashier-signature: 8f4c...c19a
Idempotency-Key: 7f9c1d2e-4b1a-4c3d-9e8f-0a1b2c3d4e5f
{
  "operatorId": "your-operator",
  "playerId": "p_10482",
  "transactionId": "7f9c1d2e-4b1a-4c3d-9e8f-0a1b2c3d4e5f",
  "credit": { "currency": "USD", "amount": "24975", "decimals": 2 },
  "source": { "asset": "USDT", "network": "TRON",
              "amount": "250000000", "decimals": 6, "confirmations": 20 },
  "promoContext": "WELCOME100"
}

Pricing

A per-transaction fee, with no setup costs or monthly fee. The price depends on your volume.

The fee applies to the deposit, with a per-transaction minimum. We detail it once your application is approved.

Apply for access

FAQ

Frequently asked questions

How long does integration take?+

The five operator-side endpoints are a matter of days for a team that already models player balance. You start in the sandbox as soon as we approve your application.

Which coins and networks do you support?+

Bitcoin, USDT on TRON (TRC-20) and USDT on Ethereum (ERC-20), all live. New assets appear in the cashier with no changes on your side.

Who holds the funds?+

You choose. With self-custody, deposits land in your cold wallet and you sign the payouts; we hold no key that can move that money. If you'd rather not run the signing, Vaze holds custody cold with manual signing.

What happens if your system goes down while a player deposits?+

The transaction is already on chain and isn't lost. When we're back we detect it and credit it, and the retry is idempotent: a deposit is never credited twice.

How long do withdrawals take?+

The commitment is 4 business hours from the request. The player sees the real status in the cashier at all times and, once paid, the transaction link.

Can players pay from their wallet?+

Yes. Besides the QR code and the address, the cashier opens MetaMask, TronLink or any WalletConnect wallet to pay in one tap, on the right network.

What if a player sends the wrong coin?+

If it's an asset we can read on that network, it's resolved manually case by case. If we don't support it on that network, it may be unrecoverable. The cashier shows this warning before the address.

How do you handle bonuses and rollover?+

They stay on your platform. Before each withdrawal we ask your Wallet API for the withdrawable balance and respect your answer. Your promo code travels with every deposit.

Do you have a test environment?+

Yes. A sandbox on TRON, Ethereum and Bitcoin testnets, with the OpenAPI spec. You get it once your application is approved.

Application

Apply for access

No calls to schedule. Tell us about your operation and, once approved, you get everything you need to integrate.

Apply for access

We review every application within one business day.

  1. 1

    Fill in the application

    Company, license, markets, volume and your preferred custody model. Five minutes.

  2. 2

    We review it

    We verify your operation and let you know by email.

  3. 3

    You get your sandbox

    Credentials and full documentation, ready for your technical team.

  4. 4

    You go live

    Once your integration passes in the sandbox, we switch on production.