Tokens mirror deposits.
Every token corresponds one-for-one to money held in an ordinary account in your core. Your general ledger, regulatory returns, deposit-insurance treatment and liquidity reporting do not change.
1.0 Built, tested and ready for your pilot
MVESCROW · Programmable fund control
MVESCROW
Escrow that enforces itself, beside the core you already run.
MVESCROW turns each escrowed balance into tokens on a bank-controlled ledger. The rules of the escrow travel with the money. Evidence is checked by AI under human control. Every regulator and auditor gets a record they can verify for themselves. Your core banking system stays exactly as it is.
- The rules travel with the money
- AI under human control
- Your core stays exactly as it is
0changes to your core banking system
5capabilities needed from your core
6languages in the portals
0AI outputs that can move money
How a release works
One release, end to end
Step 1
Buyer money arrives through your normal rails
Step 2
Tokens mirror it one-for-one; the pack splits it
Step 3
Certifier signs; AI cross-checks the evidence
Step 4
Rule engine decides, officer approves
Step 5
Your core pays out; the record is sealed
1 · What it is
A control ledger for conditional money, built for banks.
Escrow is a simple legal idea with a hard operational problem: hold money for two or more parties and release it only when agreed conditions are evidenced. MVESCROW automates that execution. It does not replace the escrow agreement or the trustee.
Rules ride with the money.
Split ratios, certificate requirements, approver quorums, retention periods, time locks and lien blocks are attached to the balance as versioned, deterministic rule packs.
Every change is provable.
State changes are signed, hash-chained and externally time-stamped, so a bank, an auditor or a court can verify the history independently.
The core stays the book of record for the balance.
MVESCROW becomes the book of record for the conditions.
Swipe sideways to see the full diagram →
Plainly
MVESCROW tokens are not a stablecoin and are never transferable to the public. They are issued by the bank, against its own deposit liability, inside its own systems. MVESCROW has no dependency on any public crypto-asset and runs on PostgreSQL, a database your teams already operate and audit.
2 · Next generation
From accounts that are policed after the fact, to money that carries its own rules.
Regulators are moving escrow from a single designated account audited later to multi-account structures with automatic sweeps and bank-side enforcement. Spreadsheets, standing instructions and manual certificate checks were not built for that.
Legacy escrow account
- Where rules liveIn manuals, spreadsheets and officers' heads
- Release decisionManual review of paper or PDF certificates
- Evidence of what happenedReconstructed from mail, files and core entries
- ReconciliationPeriodic, manual, break found late
- SupervisionRegulator asks; bank assembles a pack
- Why was this refused?A phone call to the relationship manager
- New regulationMonths of change requests
- Path to tokenised settlementA new programme later
With MVESCROW
- Where rules liveIn versioned rule packs the engine executes the same way every time
- Release decisionSigned digital attestations, cross-checked, then decided by the rule engine and approved by people
- Evidence of what happenedSigned, hash-chained, externally time-stamped record of every state change
- ReconciliationContinuous comparison of token supply with core balances; breaks raised within minutes
- SupervisionRegulator and auditor portal plus machine interface, scoped by jurisdiction
- Why was this refused?An explanation in the user's language, taken from the same decision log the API returns
- New regulationA rule-pack change, tested and approved, with the old version preserved
- Path to tokenised settlementA defined connector interface, added only when your bank joins a live network
3 · Coexistence
A sidecar, not a replacement. Your core never needs to know we are there.
Core replacement is slow and costly: IBM's Institute for Business Value reported in September 2025 that 94% of core modernisation projects exceed their timelines. MVESCROW takes the sidecar route that EY, FIS and others now describe as a standard approach.
The integration contract is deliberately narrow
MVESCROW needs five capabilities from your core. Every mainstream core exposes them.
- Open or designate an account for an arrangement
- Notify a credit when money arrives
- Place and release a hold or earmark
- Post a transfer when a release is approved
- Return a balance and statement for reconciliation
How money moves
- In: collections arrive through your normal rails. MVESCROW hears the credit event, mints tokens, applies the split and instructs the core to sweep.
- Out: MVESCROW instructs a release only after policy is satisfied. Your core executes it on your normal payment rails.
- Always: reconciliation compares token supply with core balances and raises a break when they differ.
- Exit: bank-held keys and data, source-code escrow and a documented exit plan mean you are never locked in or locked out.
Out of scope by design: replacing or modifying your core, general ledger, payment switches, or AML and sanctions engines. MVESCROW integrates with them.
Adapter certification
Each core adapter is proven against a published capability suite before it is trusted in production.
Idempotent by design
Retries, duplicate notifications and partial failures cannot create or lose value. Money movements are safe to repeat.
Optional, never required
MVKYC, MVGRC and MVPAY connect when you want them. MVESCROW deploys on its own.
4 · Interfaces
Every person and every system meets MVESCROW through the right door.
Your bank owns the customer experience. Portals are white-label and the same components embed inside your internet and mobile banking.
Operations portal
Release queue, exceptions, cases and dual control for your escrow officers.
Developer portal
Depositors raise release requests, see position and track every decision.
Buyer view
Home buyers and counterparties see where their money is and why.
Regulator portal
Supervision, statutory reports and audit packs, scoped to the regulator's jurisdiction.
Executive dashboard
Portfolio position, breaks, cases and early-warning indicators on one screen.
Lender portal and certifier workspace
Lender views, and a web workspace for architects, engineers and chartered accountants who sign attestations. Certifiers can also sign on their phones, online or offline.
REST and webhooks
One merged, versioned API catalogue. Signed webhooks, a cursor-based event feed and per-client usage reporting.
Core adapter
The five-capability contract to your core, with a simulator and certification harness.
Regulator machine interface
Programmatic access for supervisors and auditors, with the same jurisdiction scoping as the portal.
Zero-trust service identity
Every service call carries a scoped identity. No shared secrets between services.
Embeddable components
White-label theming and widgets for your internet and mobile banking.
Settlement connectors
Isolated connectors to tokenised deposit, CBDC and land-registry networks, built when your bank joins one.
Agent gateway (MCP)
A Model Context Protocol server for customers' own AI agents, with five tools: position, attestations, explain a decision, request a release, receipts.
Signed mandates
An agent acts only under a signed credential with a scope, limits and usage counters, and it can be revoked at once.
Know-Your-Agent register
Every external agent is registered and attributable. A request from an agent still waits for a bank checker.
Six languages
English, Arabic (right-to-left), Hindi, Tamil, Russian and Uzbek in the portals, with decision explanations in each.
Plain-language refusals
Every block returns a code and an explanation drawn from the rule pack, so users learn what would unlock the money.
Reviewed by native speakers
Every explanation text is reviewed by native speakers before an edition goes live.
5 · Easy to adopt
No migration. No core project. A new capability your teams can switch on.
The sidecar model removes the three things that slow banks down: touching the core, retraining every branch, and waiting for regulation to settle.
Connect
Wire the five-capability adapter to your core or API gateway. A simulator lets your team test first.
Choose a pack
Select the rule pack for your product and jurisdiction. Review it with your compliance and legal teams.
Brand it
Apply your theme to the portals, or embed the components into your own channels.
Pilot
Run a first arrangement in parallel with your existing process. Reconciliation shows the two agree.
Scale
Add arrangements, packs and jurisdictions. Turn on AI agents one at a time, at your pace.
Your keys, your data, your database
Runs on PostgreSQL under your control, within your IT outsourcing and data-residency rules.
Your model, your region
AI is model-agnostic. Use an in-region hosted model or a fully in-bank open-weight model. Nothing leaves without your configuration.
Built to be left
Source-code escrow, a perpetual licence on insolvency and a documented exit plan.
6 · Features
Everything an escrow desk does, with a control behind each step.
Arrangement lifecycle
Origination, party onboarding, configuration, operation, amendment, dispute, closure and archival in one guided flow.
Token ledger with buckets
Balances held in free, collection and protected buckets. Protected funds never move automatically.
Rule-pack engine
Jurisdiction and product templates as code: splits, certifier quorum, cumulative drawdown caps, retention, time locks and regulator override. Rules cannot read the clock or the network.
Signed attestations
Architects, engineers, chartered accountants and auditors sign digitally. On-device checks reject blurred, duplicate or off-site photographs before upload.
Holds, releases, reversals
Instruct holds and payments through your core. Dual control with a maker and a checker on every sensitive operation, including reversals.
Collections and splits
Percentage splits, sweeps, earmarks and retention applied at the moment money lands.
Disputes and cases
Raise, evidence, decide and record disputes with the full history attached.
Continuous reconciliation
Token supply against core balances, with breaks classified and queued for a maker and a checker.
Supervision and reporting
Statutory reports, audit packs and governance reports. Regulators see only their own jurisdiction.
Notifications and fees
Event-driven notices to every party in their language, and configurable fee and billing rules.
Conventional and Sharia-compliant
Both operate on one platform, with segregated entities and windows.
Crypto-agile security
Algorithm tags, key rotation and a path to hybrid post-quantum signatures, so today's records stay verifiable.
7 · AI agents
Agents that read, check and warn. People and the rule engine decide.
Each agent works inside a fence: read-only tools, typed output, a signed record of what it did, and a named person who accepts, edits or rejects the result.
No AI output can create, approve or execute a movement of money. Only the deterministic rule engine, fed by human attestations, human approvals or signed mandates, can do that.
Intake Agent
Reads agreements, registrations and plans, pre-fills the arrangement with a source and confidence on every field, and flags clauses that conflict with the pack. Fields it is unsure of are left blank, not guessed.
Human in control: the relationship manager confirms every field.
Certificate Check Agent
Checks each attestation against its evidence, the certifier registry, earlier certificates and the arithmetic. Returns consistent, query or concern, each with reasons.
Human in control: a concern routes the release to an officer.
Progress Evidence Agent
Compares geotagged site photographs with the claimed stage and catches re-used or manipulated images. A second line only; it never replaces the statutory certifier.
Human in control: certifier and operations officer.
Anomaly Sentinel
Scores drawdown patterns, payee networks and collection behaviour. Opens a case with the top contributing factors when a pattern crosses a threshold.
Human in control: risk and compliance officer.
Reconciliation Assistant
Proposes the cause and the fix for each break, with similar past cases. It never posts a correction itself.
Human in control: operations maker and checker.
Persona Assistant
Answers in the user's language about their own arrangement: why was I refused, what is needed next, where is my money. Answers come from the decision log and link to the record. It always says it is AI and always offers a person.
Human in control: the user; escalation always offered.
Regulatory Watch Agent
Monitors regulators' publications in the jurisdictions you enable and summarises what touches a pack, with a stored copy of the source.
Human in control: compliance analyst.
Rule-Pack Drafting Agent
Drafts a pack change and new test cases from an approved summary. Tests must pass before anything is published.
Human in control: compliance and legal approve.
Ops Triage Agent
Groups alerts, dead-letter events and cases, and drafts the first diagnosis and the run-book step.
Human in control: operations.
Why the bank can trust them
Eight guardrails, applied to every agent, every release.
Never near the money
Agents cannot reach money paths. Only the rule engine can instruct a movement.
Signed AI record
Model and version, prompt version, input hashes, output, confidence and the reviewer's action are stored and signed.
Human override, always
A person with authority can disregard any advice, and the platform records that they did.
Your model, your region
Model-agnostic, including fully in-bank open-weight models. No personal data goes to an external model without your explicit configuration.
Evaluated before release
An AI inventory, risk class and evaluation suite exist for every capability, run before each release and continuously after.
Injection-resistant
Documents are untrusted data. Tools are allow-listed. Injected instructions are flagged. An attack suite runs in the pipeline.
Minimised data
Personal data not needed for the task is redacted before any model sees it.
Told and handed over
People are told when they are talking to AI and can always reach a human.
8 · Fastest route to market
Launch a compliant escrow product without waiting for a core programme.
The fastest path is the one that avoids the slowest dependency. MVESCROW removes the core from the critical path and gives you the product, the portals and the packs ready to configure.
No core change
The adapter uses five capabilities your core already exposes. There is no core release cycle to wait for and no regression risk to the book of record.
Packs, not projects
Jurisdiction and product templates are ready to review. A new state or country is a pack, not a build. Packs ship for India (Tamil Nadu first), the GCC and Central Asia.
Portals on day one
Working portals for operations, depositors, buyers, lenders, certifiers, regulators and executives, in six languages, themeable to your brand and embeddable in your own apps.
Evidence for your regulator
A signed, verifiable record, a supervision portal and an explainable decision for every refusal give your regulator a straight story.
First-mover window
We found no core vendor with a native tokenised escrow module. Banks that move first will help define how regulators expect escrow to be supervised.
9 · Why it is best in class
Rules enforced in the money, not around it.
Escrow fintechs enforce rules in application logic over ordinary accounts. Core vendors have no native module. MVESCROW is built from the control outward.
Enforcement in the ledger
A prohibited movement fails at the ledger. It is not left to a screen, a review or a person's attention.
Tamper-evident by construction
Signatures, hash chains and external time-stamps give an auditor mathematical proof, without the platform risk of a blockchain.
Explainable, every time
Every decision is stored with its inputs and reasons, and is explained in the user's language from the same record.
Banking-grade engineering
Idempotency, consistency under failure, zero-trust service identity, append-only audit and dual control are built in and tested in the release gate.
AI with a fence
Nine agents that help and warn, none that decide. Every AI output is signed, reviewable and overridable.
Part of a composable suite
Works with MVCORE, MVKYC, MVGRC, MVPAY and MVLEND when you want them, and alone when you do not.
- MVCORE
- MVBOOKS
- MVGRC
- MVPAY
- MVLEND
- MVKYC
- MVESCROW
- MVTREASURY
Moneyverse is a technology company providing software. Each bank pilot proceeds only after its entry gates are met: legal opinions, independent security attestations, source-code escrow and written regulator comfort.
Release 1.0
Built, tested and ready for your pilot.
Release 1.0 is complete. Every change passed an automated release gate before it was merged, and the platform was proven end to end against a simulated core banking system. The next step is your bank.
The platform
- Token ledger, proof layer and rule engine
- Rule packs for India (Tamil Nadu first), the GCC and Central Asia
- Signed attestations, web and mobile
- Collections, holds, releases, reversals and fees
- Disputes and continuous reconciliation
- Reporting and regulator supervision
- Administration for multiple entities, branches, calendars and languages
The experience
- Seven portals in six languages, white-label and embeddable
- Open API, signed webhooks and event feed
- Agent gateway with signed mandates
- Nine AI agents with eight guardrails
- Arabic right-to-left and plain-language explanations
- Bank-operated deployment package
With your bank
- Adapter certification on your test core
- Rule-pack review with your counsel
- Regulator comfort in your jurisdiction
- Independent security and audit reports
- Your model endpoint and time-stamp authority
Talk to us
See MVESCROW run on your use case.
A walkthrough shows a real arrangement from collection to release, the decision log behind each step and what your regulator would see.
Moneyverse is a technology company providing software solutions and is not a bank. MVESCROW does not hold customer funds; funds remain in the bank's own accounts. MVESCROW tokens are not a stablecoin or a public crypto-asset and are not the MV Token. Regulatory references are summaries and do not constitute legal advice; local counsel opinions are required in each jurisdiction before launch.