Static Wallets vs Invoices for Crypto Payments

Crypto payment integrations usually start with one question: should every customer payment use a new invoice, or should each customer receive a reusable deposit address? The answer depends on the product flow.

Invoices work best for one-time checkout sessions. Static wallets work best for repeat deposits, balances and customer account funding. Many platforms use both models in the same product.

Quick answer

Use a crypto invoice when the customer is paying for a specific order, amount or checkout session. Use a static wallet when the customer needs a permanent crypto deposit address that can be reused over time.

For example, an e-commerce order should usually use an invoice. A marketplace user balance, gaming top-up wallet or Telegram bot deposit account usually fits static wallets better.

When to use static wallets

A static wallet assigns a reusable deposit address to a customer, merchant-side account or internal entity. The customer can send funds to the same address more than once, and the merchant backend maps incoming deposits back to that customer.

• Customer balances and account funding.
• Marketplaces where sellers or buyers deposit repeatedly.
• Gaming, wallet, bot and top-up products.
• Products where the amount can vary from deposit to deposit.

See the Static wallets page for the permanent deposit address model.

When to use invoices

A crypto invoice represents one payment request. It has a selected amount, payment details, expiration and status. The merchant creates an invoice for an order, displays payment details and waits for the final status.

• One-time checkout orders.
• Payment links for a fixed amount.
• Digital products and paid reports.
• Backend-driven checkout with webhooks.

See the Crypto Invoice API page for the developer flow.

Side-by-side comparison

Invoices are easier to reason about when the customer is paying for one order. Static wallets are easier when the customer will deposit many times. Invoices usually expire; static wallets are meant to stay assigned. Invoices are order-first; static wallets are account-first.

The main operational rule is simple: do not use a permanent address when you need a strict one-time checkout amount, and do not create unnecessary invoice sessions when the product is naturally a balance or deposit account.

Implementation notes

Whichever model you choose, your backend should reconcile payment status instead of relying on customer screenshots or wallet intent. Use webhooks, payment status checks and clear support rules for underpaid, overpaid, expired or wrong-network payments.

For stablecoin checkout, start with Accept USDT payments. For repeat deposits, start with static wallets.