One address per player, or a new one every time.
Balance-based cashiers and one-off checkouts need different address models. Repiblik supports both, and you can switch without a migration.
Address Strategy
PERSISTENT ROTATING one per player new per deposit ╭─────────────────────╮ ╭──────────────────────╮ │ TQ7vuq5Gu…H9xK │ │ TAjZqjqV1…FQWY │ ╰─────────────────────╯ ╰──────────────────────╯ + 157.00 USDT ✓ + 157.00 USDT live + 83.00 USDT ✓ TQjTTgG… retired + 162.00 USDT ✓ TSxLZgR… retired + 99.00 USDT ✓ TiA9hWC… retired + 112.00 USDT ✓ ThC6bWd… retired + 55.00 USDT ✓ TyaoTbT… retired + 14.00 USDT ✓ TSh9Q1J… retired ────────────────────────────────────────────────── player_8812 · Tron USDT · rotate in one call
Persistent addresses.
Give each player one permanent address per asset and network. They save it once and deposit whenever they like. Network fees can be optimised.
Rotating addresses.
Issue a fresh address for every deposit for cleaner attribution and better on-chain privacy.
Rotate on demand.
Retire a flagged address, refresh after a key rotation, or issue a new one when a player asks. One API call.
Address Strategy
Address models compared
| Persistent | Rotating | |
|---|---|---|
| Best for | Balance-based cashiers | Per-order checkout |
| Player experience | Save once, reuse forever | New address each time |
| Attribution | By address | By address + amount |
| Privacy | Lower | Higher |
| Network fees | Lower with batching | Higher |
On memo-based chains (XRP, XLM, Cosmos) players share one address with a unique destination tag.
Read the address issuance docs →
Or sign up free. No KYC, no approval queue.