Not a retail wallet or consumer app. The counterpart is the merchant and the field operation.
Run deposits and withdrawals under one operations roof
Controlled collection, approval, payout pool and reconciliation for merchants, field teams and finance.
Panel, API and reconciliation share the same ledger.
6
Methods
6
Solutions
4
Process
4
Upcoming
01 — Company
Who we are
We sit between merchant sites and field teams. The goal is not faster cash-in for its own sake; it is to keep deposits, withdrawals and balances under one rule and one record.
Merchant integration, field approval, the payout pool and daily reconciliation live in a single product. Nobody needs a parallel spreadsheet.
Between the site request and the bank movement: approval, routing, documents and balance entries.
A transaction is written once. Rates lock at creation. The audit trail does not disappear.
02 — Methods
How money moves today
Bank transfer deposit
The customer sends to the issued IBAN. The field desk or operations confirm amount and receipt.
Bank withdrawal
The request enters the pool, is routed to a capable desk, and closes with a receipt.
API deposit and payout
The merchant opens the order in its own UI. Status arrives as JSON and webhook.
Routing and pool
A withdrawal is not locked to one account; it is spread by capacity to field or provider.
H2H / provider
When needed, an external rail is used with the same approval and reconciliation language.
Receipt and trail
High-value payouts can require a document. The transaction footprint stays readable.
03 — Upcoming
Methods we are adding
These rails are being prepared. They will join the same approval and reconciliation model.
QR
Accountable QR collection that lands in the same approval queue.
Cepbank
In-app bank transfer confirmation without leaving the merchant flow.
Card
Card acquiring with the same merchant callback and ledger rules.
Crypto
On-chain rails reported back into the same reconciliation day.
04 — Solutions
What we operate
Institutional collection
Deposits and withdrawals under one roof; field, site and centre balances stay separate.
Controlled approval
Every order ends as approve, reject or review. Who processed which amount is stored.
Merchant API
Sites connect on standard endpoints. The result returns once via callback.
Daily reconciliation
Field and site balances are settled at day end; gaps appear on the operations screen.
Field network
Dealers and staff work with their own limits, accounts and queues.
Operations desk
Pending deposits, the payout pool and alerts are run from one panel.
05 — Process
How a transaction travels
-
Step 1 — Request
The site opens a deposit or withdrawal via API or the panel. Amount and identity lock immediately.
-
Step 2 — Match
A suitable account or field desk is selected. Withdrawals can enter the pool instead of one fixed account.
-
Step 3 — Approve
Operations or the field desk approve or reject. The actor and the reason stay on the record.
-
Step 4 — Close
The callback returns to the site, balances update, and day-end reconciliation sees the same figure.
Let’s plan the integration
Site onboarding, field setup and the operating rule are designed together on Solo Havale.