Wallets and Embedded Finance
Balances, top-up, payouts, conversion and third-party payments as a product. Or the same core inside a business whose main work is something else, with finance running on top of it.
- Wallets
- Embedded finance
- Tariffs
Overview
Accounts and balances
Every charge needs a balance to land on, so the core starts there: customer and counterparty accounts, multi-currency and crypto balances, each with its own state and lifetime. KYC and KYB run through a provider and the result is a contract — this customer's tariffs, limits and rules — which is what the rest of the system reads. An account can belong to a person, to a company with several signatories, or to an agent acting for a customer.
Money in and out
Money arrives by bank transfer, QR scheme or on-chain address, and leaves the same way. Payouts go one at a time or by file, with a queue, statuses and retries, so a failed batch is a list of items and not a lost run. Transfers between customers stay inside the system and never reach an external network, and a customer exchanges between their own balances at the system rate — that spread is the operator's revenue.
Charging and collecting
A service catalog and tariff plans with validity periods turn an event from the client's own systems into a charge you can show a counterparty, priced by volume, time, weight or distance. Receivables are the other half: who owes what, what is overdue, which reminders went out, and the rule under which a counterparty carrying a negative balance does not get the next service. A charge can be contested and corrected, with a record of who changed it and why.
Running it
Any service, currency, conversion or integration sits inside the app, which is what makes a wallet somewhere a customer stays. The operator gets a back office and the counterparty a portal, with fiat and crypto in one view and statements the customer can pull themselves. Charges, payments and turnover break down by counterparty, service and period — the report an operator is asked for at the end of a month.
Ownership
On us
- The coreAccounts, balances in every currency and asset, and the movement between them.
- The tariff engineIt turns an event from your own systems into a charge you can show a counterparty.
- The interfacesMobile app, customer and counterparty portals, and the back office.
On you
- The licenseYour own, or a partner's.
- The eventsWe price what your own systems emit.
- The commercial termsWhich services are charged, and on what plan.
Fit
- Who it is for
- EMIs, fintechs, crypto services and neobanks. Marketplaces and platforms that hold a seller balance. And businesses whose main work is something else: logistics, utility operators, B2B platforms.
- When it comes up
- Customer money sits with a partner. Mass payouts are needed. Crypto has to sit next to fiat. Tariffs are calculated by hand and receivables are not controlled.
- The objection we hear
- That a BaaS is cheaper. In a BaaS the customers and part of the P&L stay with the provider. Here the product and the data belong to the client.
Limits
No deposits, no credit, no lending. A BNPL request is one we turn down.
No merchants of our own, and no P2M.
No EMV, and no acquiring.