Help center

How can we
help?

Search quick answers about wallet behavior, integration patterns, identity gates, and operational controls.

01

Start building

Install the SDK, configure a sandbox key, retrieve a wallet, and make your first balance request.

Open quickstart →
02

Operate safely

Understand sessions, idempotency, locks, spending limits, reserves, and domain-specific errors.

Review safety patterns →
03

Get support

Ask about architecture, sandbox access, payment integrations, or an issue in your implementation.

Contact support →

Quick answers

Common questions.

No. MojoWallet is the internal value ledger and orchestration layer. Charges and payouts happen through the payment stack you choose. MojoWallet records the resulting value, controls its behavior, and coordinates safe settlement patterns.
Wallets support multiple currencies and categories, including fiat-denominated balances, loyalty points, sweepstakes value, bonuses, and reserved value. Holdings can be cashable or non-cashable and grouped into root currency families.
A stable reference_id makes retries safe. If a response is lost and you resend the same operation, MojoWallet returns the existing transaction instead of moving value twice. If the payload differs, it raises an explicit replay error.
Withdrawals require an active session. Only one withdrawal-capable session may be active per wallet, which prevents concurrent flows from racing the same balance. The Python context manager closes the session automatically.
Reserve the value into a hold currency, run the external payout, then confirm the reservation on success or release it on failure. If the reservation expires, MojoWallet releases it automatically and emits an event.
Most mutations stop, while the wallet remains readable. Rewards may still be credited to locked wallets so program obligations can continue without reopening customer spending.
Every rules- or promo-funded bonus currency creates its own grant and playthrough obligation. Progress is tracked per grant. Once the obligation reaches zero, residual promotional value converts to the configured cashable currency and a webhook fires.
Balance is the total quantity in a currency. Cashable value is the subset permitted for cashout. Spending power accounts for the available balance plus any active spending controls or limits.
No. The Python SDK provides convenient domain methods, but every wallet primitive is also available through the REST API for any server-side language.
Sandbox keys begin with mvs-; production keys begin with mvp-. Both use the Authorization: apikey … header. Keep keys on your server and scope their permissions to the operations required.

No matching answers. Try a broader term or contact support.

Still working through it?

Send us the flow you are building and where it is getting stuck. We’ll help you map it to the right wallet primitive.