Crypto Casino
Torrent Gear
How the multi-wallet system works for operators
Multi-wallet is a model where one client has several independent "pockets": real money, bonus balance, cashback/points, held funds (holds), multi-currency sub-accounts and even grocery "wallets" (sports/casino/poker/marketplace). This approach gives flexibility in promo, risks and calculations, but requires a strict ledger architecture, write-off and reconciliation rules.
Why do operators need multi-wallet
Multi-currency and locales. Support for deposits/rates/payments in different currencies without distortions and hidden conversion.
Segmentation of funds. Real money ≠ bonuses ≠ deductions; different spending and withdrawal rules.
Cross-product economy. Different verticals with separate limits, margins and tax regimes.
Responsible play (RG) and compliance. Flexible limits on wallets, closed loop "depozit→vyvod the same method."
Accounting transparency. Easier audit, reporting and investigations (AML/fraud/disputes).
Balance sheet model: what "pockets" are
1. Cash (real money)
Main liquid balance. Rules: freely replenished/output subject to AML/RG.
2. Bonus / Promo
It is credited by shares, has vager conditions (turnover, deadlines, rate limits). Withdrawal - after fulfilling the conditions and transfer to cash.
3. Locked / Hold / Pending
Funds held: pending payment, KYC/EDD, dispute/dispute, technical hold.
4. Points / Cashback / Tokens
Non-monetary units (loyalty). Converted at the rate or participate in promo.
5. Sub-wallets per product
Separate wallets for sports/casino/poker/marketplace - with their own limits, commissions and tax rules.
6. Multi-currency sub-accounts
EUR/USD/GBP/BRL, etc. - each with its own balance sheet, accounting rate and FX rules.
spend priority rules
A clear write-off matrix eliminates disputes and fraud exploits:1. First bonus with marked games/bets and limits, then
2. cash, then
3. holds do not move (read-only), 4. points - by explicit envelope.
Overrides are possible, but always deterministic and logistic.
Architecture: what multi-wallet consists of
Ledger Service (double entry). Single source of truth: 'account _ id', 'wallet _ id', 'currency', 'balance', 'available', 'locked'. Operations - only through atomic records (credit/debit/transfer) with idempotency.
Wallet Orchestrator. Applies business rules (priority, wagering, RG limits), pulls FX service, payout router and bonus engine.
Promo/Wagering Engine. Accounting for conditions, deadlines, ideal games, envelope cascade.
FX Service. Quotes/conversion between sub-accounts, exchange rate differences and weekend restrictions.
Payout Router. Closed loop (reversal/refund), OST/A2A/local rails; limits and compliance matrix.
Risk & Compliance Gate. AML/PEP/sanctions, SoF/SoW, velocity limits, RG restrictions, device risks.
Reconciliation & Reporting. Three-way reconciliation (ledger ↔ provider ↔ bank/network), period-end closing, adjustment logs.
Observability. Logs, metrics, alerts: p95 write-offs/credits, discrepancies, "frozen" holds.
Ledger key invariants (without them, the system breaks down)
Idempotency is everywhere. Each request has a 'request _ id', repetitions do not change the total.
Atomicity. Any operation is a "double entry" transaction, no partial commit.
Non-negative balances. No quiet overdrafts (except for explicitly permitted credit features).
Event Sourcing / Outbox. Wallet events go into the payment/gaming circuit guaranteed and in order.
Strict currency domains. Cash transactions - only in your currency; inter-currency - through an explicit FX transfer.
Multi-currency and FX in multi-wallet
Separate sub-account for currency. No "virtual" recalculations on the fly when decommissioning.
Explicit FX transfer. The user (or system) converts the EUR→USD at the rate with margin and TTL quotes.
Exchange rate differences and returns. Refand - at the current rate of the method/network; keep the quotation rate and source.
Limitations. Anti-arbitration rules, limits on the frequency and volume of the envelope, news/weekend - increased margin.
Payments and deposits: closed-loop and withdrawal policy
Reversal first. Return to deposit source (refund/devolução), then - alternative payout after checks.
OST/A2A/local rails. Routing by country/currency/limit/risk, SLA by p95.
Output freeze. Transfer funds from cash → hold to settlement/checks, then deblock.
Bonus economy and wager
Issuance rules. Triggers: deposit, activity, event; cap by sum and frequency.
Working out conditions. Vager X ×, ban on some games, max bet, deadline.
Conversion to cash. After the conditions are met - atomic transfer bonus→cash, log of the reason.
Abuses. Multiaccounting, drops, chip dumping → graph analysis and promo bans by node.
RG/AML in Wallet Outline
Limits on wallets and currencies. Daily/weekly amounts, frequency of conclusions, new details - through "cool-off."
Affordability. Matching deposits to income, SoF/SoW triggers.
Transaction monitoring. "Cash-in → cash-out," surfing, cross-border; case queues, SAR/STR.
Journals and auditing. Unchangeable logs, explainability of decisions.
User Experience (UX)
Transparent balances. Separately: cash/bonus/hold/points; tips on vager and timing.
Explicit FX translation. Display of course, margin, TTL timer, total amount; history of envelopes.
Real-time statuses. Hold, Pending, Credited/Paid; transaction references.
Write-off rules. Visible priorities ("bonus first, then cash") and game conditions.
Self-control. Limit/pause/self-exclusion buttons right in your wallet.
Metrics and KPIs
Finance: reconciliation discrepancy, share of "hung" holds, p95 enrollment/withdrawal, FX rate/margin.
Risk: FPR/TPR anti-fraud, share of operations closed-loop, SAR-rate.
Promo: conversion of bonus→cash, outflow due to conditions, share of abuse.
Customer: NPS on cashouts, "where's the money?" tickets, case resolution time.
Reliability: share of retrays, provider failures, wallet downtime.
Frequent implementation errors
1. There is no single ledger. Balances in different services "diverge" - endless manual edits.
2. Mixing bonuses with cash. Legal and UX risks, disputes in conclusions.
3. Magical auto-conversion. Write-offs "at the internal rate" without an explicit FX step are a source of conflicts.
4. Lack of idempotency. Doubles at timeouts, races, retreats.
5. Weak write-off rules. Promo exploits and course arbitration.
6. No closed-loop. Conclusions to new details - direct AML trigger.
7. Invisible hold. The user does not understand why the funds "disappeared."
Multi-wallet launch checklist
1. Simulate balance sheet domains and their invariants (cash/bonus/hold/points/currencies).
2. Raise the ledger with double entry, idempotency and outbox event bus.
3. Describe the policy engine: write-offs priority, vager, RG/AML limits, closed-loop.
4. Implement FX service (quotes, margin, TTL, history).
5. Connect a payout router with a fallback and a limit matrix by method/country.
6. Roll up (providers/banks/networks) and anomaly dashboards.
7. Transparent UX: separate balances, course and dates, statuses and references.
8. Test plans: races/retreats, partial write-offs, FX/provider failures, vager boundary cases.
9. Train the support (scripts by holds/FX/bonus/closed-loop).
10. Run A/B tuning of priorities and thresholds, measure approve-rate and NPS.
Mini-FAQ
Can the bonus and cash be combined?
Undesirable. Separation eliminates disputes, simplifies auditing and promo logic.
Do I need a separate wallet for each currency?
Yes I did. This removes the risks of "hidden FX" and makes the calculations predictable.
Why did the refund come at a different rate?
Refand is at the exchange rate at the time of return/scheme. Keep the rate of the original quote and disclose the policy.
How to speed up cashouts?
Route on rails with the best SLA (OST/A2A/local fast), keep closed-loop and minimize manual checks for low-risk.
Multi-wallet is the framework of the operator's financial discipline: separate balances, explicit conversion, strict rules for write-offs and conclusions, transparent statuses and strong reconciliation. Such a system removes disputes, improves UX and KPI payments, and most importantly, ensures compliance and business stability when scaling by markets, currencies and products.