Real, bonus and locked, kept apart
Each balance type is tracked in its own right, so a bonus liability is never mistaken for cash the brand can draw on.
Payments and wallet
Give players payment choice without splitting your books
Fiat through MiFinity, crypto through NOWPayments, one ledger underneath. Real, bonus and locked balances stay distinct, and compliance is checked before money moves.
Fiat and crypto arrive in the same account structure
A player pays with a card, an e-wallet or a supported crypto asset. Whatever they choose, the deposit credits the same balance on the same player record, in one settlement currency per brand. Operators keep a single view of money in and money out rather than two systems that have to be argued into agreement at the end of the month.
Fiat through MiFinity
Card and bank funded deposits, and e-wallet payouts, land in the same ledger as everything else.
Crypto through NOWPayments
The player pays in the asset they hold, it converts at the rate quoted at that moment, and the balance credits when the network confirms.
One settlement currency per brand
Whatever a player paid with, the brand reports and reconciles in a single currency.
- Real, bonus and locked balances
- Consistent controls across wallet activity
- Reconciled ledger history
- Deposit and withdrawal visibility
- Fiat and crypto support
One ledger, three kinds of balance
Real money, bonus money and locked funds are three different obligations. The ledger keeps them apart and reports them separately, inside one set of books.
Compliance standing on the same record
The tier, the verification state and any screening result sit on the record the wallet reads before it moves anything.
Every movement in the audit trail
Deposit initiated, deposit confirmed, withdrawal requested, approved, processing, sent. Each one is its own event with its own actor.
Duplicate safe settlement
A retried message from a game provider settles once. The books balance without a manual repair at the end of the month.
Screenshots are captures of the demo tenants MaxBet and LuckyOni. Every figure on screen is demo data.
The wallet asks before it moves money
Compliance and payments are one system here rather than two that exchange messages. Before a deposit or a withdrawal proceeds, the wallet reads the compliance standing on the player record and either allows the movement or refuses it, with the reason attached.
The tier decides eligibility
A T0 to T4 standing sets deposit limits and withdrawal eligibility, with thresholds configured per brand.
A refusal is a record, not a silence
A denied transaction keeps its reason and its timestamp, so a reviewer sees the standing that applied at the time rather than the standing today.
Decided in the account core
The check runs in real time, so a player who has just cleared verification is not waiting for somebody to notice.
What happens when a game provider retries
Providers retry. Networks drop halfway through a response. Without protection that produces the two failures every finance team knows: a bet taken twice, or a win paid twice.
- 01
The round arrives
A bet reaches the wallet carrying its own identity, not just an amount and a player.
- 02
The connection stutters
The provider does not receive the response, so it sends the same message again.
- 03
The ledger recognises it
The retry is matched to the event already settled, whatever order the retries arrive in.
- 04
The books stay balanced
One entry, one balance, and nothing for finance to unpick at the end of the month.
Every withdrawal passes a person
Paying out is the irreversible action in a casino, so it is deliberately not automatic. The context is assembled before the reviewer opens the request.
What the reviewer sees before approving
Compliance tier
The T0 to T4 standing that applied when the request was made.
Verification state
Whether identity and source of funds checks are complete, and when they cleared.
Deposit history
What the player funded the account with, and through which rail.
Screening result
Any anti money laundering screening outcome attached to the player.
The amount requested
Shown next to the context rather than on a separate screen.
What the platform does with the decision
Approve, hold or escalate
Three outcomes, each recorded with the reason the reviewer gave.
The decision joins the audit trail
Request, approval, processing and payout are four separate events, not one status field.
Payments intelligence supports the reviewer
Yaspa adds signal to the payment picture. It informs the decision rather than making it.
Where the wallet stops
What the platform owns
The wallet, the ledger and the compliance gate are ours, and so is the record of what happened: every deposit, every bet settlement, every withdrawal decision and the reason behind it. That record is the same stream the audit trail publishes, which is why a payments question and a compliance question have the same answer here.
What sits outside it
Scalara is not a customer relationship platform, a customer data platform or a business intelligence suite, and it does not run affiliate management. Payment processing fees are charged by the payment providers themselves. Which crypto assets and which markets are open to a brand depends on that brand's licence, so those are confirmed during discovery rather than promised in advance. Operators building around digital assets should start with the crypto casino route. The whole boundary is written down on what we do not do.
Whose payment relationships
On the Turnkey Platform route you keep your own payment relationships, because you hold the licence and the operation. On White Label, payments run through the orchestration that sits under our licence, which is part of what that route provides. If you have a provider you need to keep, raise it early. The answer depends on the route, the market and the provider, and we would rather scope it properly than agree in principle and renegotiate later.
The partners behind the wallet
Three technology relationships carry payments on this platform. Each one has a page describing what it does and where the boundary of that work sits.
Payments and payments intelligence
Fiat, crypto, and the signal that helps a reviewer read a transaction.
MiFinity
Payments
Fiat payments and e-wallet. MiFinity is the fiat side of the hybrid wallet that sits beside crypto in one reconciled ledger.
NOWPayments
Payments
Crypto payment processing. Deposits arrive over major crypto rails, convert at the quoted rate and credit the wallet on confirmation.
Yaspa
Payments
Payments intelligence. Yaspa adds signal to the payment picture that a raw transaction record on its own does not carry.
More about wallet and payments
They are not reconciled against each other, because they were never separate books. Both rails credit the same ledger, in one settlement currency per brand, against the same player record.
Inside that ledger, real, bonus and locked balances stay distinct and are reported separately. Bet settlement is duplicate safe, so a game provider retrying a message does not produce a second entry. The month end position is one figure with one history behind it.
Every withdrawal goes to a person, with the context already assembled: the player's compliance tier, verification state, deposit history and any screening result, shown next to the amount requested. The reviewer approves, holds or escalates, and the decision joins the audit trail with its reason.
It is deliberately not automatic. Paying out is the irreversible action in a casino. The audit trail then shows the request, the approval, the processing and the payout as separate events.
On the Turnkey Platform route you keep your own payment relationships, because you hold the licence and the operation. On White Label, payments run through the orchestration that sits under our licence, which is part of what the route provides.
If you have an existing provider you need to keep, raise it in discovery. The answer depends on the route, the market and the provider, and we would rather scope it properly than agree in principle and renegotiate later.
What this page covers in the feature matrix
Each capability below is a row in the platform index, where its tier sits beside the method and the date behind it. Read the full feature matrix.
Compliance-gated transactions
The wallet checks a player's compliance standing before any money moves, so compliance and payments behave as one system rather than two.
Exactly-once bet settlement
Every bet and win is recorded exactly once, even when a game provider's connection stutters and retries. The books balance without manual repair.
Crypto deposits
Deposits arrive over major crypto rails at live exchange rates, convert automatically and credit the player's balance on confirmation.
Reviewed payouts
Every withdrawal passes a staffed review, with the player's compliance profile shown next to the amount before anyone approves it.
Bring us the reconciliation that never balances
We will open four screens in the running platform: deposits, the ledger, a withdrawal review and the audit trail behind all three.
We ask what you are building and which markets you are targeting before we show anything, so the session is about your operation rather than a script.
