Programmable fund control
Money moves only when the conditions are proven.
MVESCROW turns every escrow agreement into rules your bank can run, prove and audit. It sits beside your existing core banking system, works natively with MVCORE, and keeps every dirham, rupee and dollar inside your bank — with AI agents that verify evidence and stop fraud before a single release is approved.
Figures are MVESCROW design targets for pilot deployments, not historical performance.
Why bank CEOs are acting now
Regulators have written escrow into the structure of bank accounts, fraudsters target every high-value release, and fintechs are building escrow franchises on top of partner banks. The bank that runs escrow digitally keeps the balances, the fees and the regulator's trust.
How it works
Every escrow in MVESCROW follows the same controlled path. A deterministic rules engine decides how much can be released. Named officers decide whether it is.
The Agreement Intake Agent reads the signed escrow agreement and drafts a versioned rule set: parties, accounts, conditions, release waterfall, retentions, fees and expiry. Every rule is linked to the clause it implements.
# rule set v3 — clause links shown arrangement: "Marina Crest Tower" accounts: collection: core:AE07-…-0412 # no debits project: core:AE07-…-0413 # protected release_rule: # clause 7.2 type: proportional_completion base: approved_cost evidence: [consultant_certificate] retention: per_template # clause 9.1 approvals: maker_checker
Every payer, unit or order gets its own virtual account number, so incoming money is identified the moment it arrives. MVESCROW keeps a sub-ledger per arrangement, per party and per unit, reconciled to your core account every 15 minutes.
# receipt of INR 25,00,000 via virtual account amount_minor: 250000000 # paise → rera_account: 175000000 # 70% → txn_account: 75000000 # 30% collection_after: 0 sweep: same_day status: settled
Certificates, invoices, bills of lading and system events arrive by portal, API or controlled mailbox. Each is hashed, time-stamped and verified. AI agents check signatures, professional registrations, arithmetic and document tampering before an officer ever opens the file.
evidence: consultant_certificate #CC-0419 sha256: 9f2c…e71a signature: valid registration: verified completion: 35% # claimed agent_E2: "13-pt jump in one month vs expected curve; 2 photos reused" status: under_review
Entitlement is computed by a deterministic, versioned rules engine — never by an AI model. It shows the arithmetic, the rules applied and the evidence used, so officers, auditors and regulators see the same answer.
entitlement = certified_pct × approved_cost − released = 28% × AED 300,000,000.00 − 72,000,000.00 = AED 12,000,000.00 # 1,200,000,000 fils requested: AED 60,000,000.00 decision: capped_to_entitlement
Every release is scored by the Release Fraud Shield, sent only to a pre-verified beneficiary, and approved under your maker-checker matrix. The instruction goes to your core or MVPAY as a standard payment; signing for tokenised rails happens outside any database transaction.
release R-2291 AED 12,000,000.00 fraud_score: low beneficiary: pre-verified (name match ✓) maker: ops.officer.14 ✓ checker: ops.checker.03 ✓ dispatch: core.payment → executed grc_evidence: recorded
Legacy coexistence
MVESCROW never asks you to move money out of your core banking system or change a line of its code. Your core keeps the accounts and the balances. MVESCROW adds the rules, the evidence, the sub-ledger and the release controls — and talks to your core through the interfaces it already has.
Swipe sideways to see the full diagram →
Integration options
POST /v1/arrangements
POST /v1/arrangements/{id}/evidence
GET /v1/arrangements/{id}/entitlement
POST /v1/arrangements/{id}/release-requests
POST /v1/release-requests/{id}/decision # maker-checker
webhook: escrow.release.executed # no personal dataBetter together
MVESCROW works with any core. With MVCORE, escrow stops being an overlay and becomes a first-class product — configured in smart contracts, backed by native virtual accounts and holds, and ready for tokenised money on the same infrastructure.
Land with one module. Expand to all. Never rip and replace.
Governed AI
MVESCROW's agents read, verify, detect and explain at machine speed. They never approve or execute a release. That line is enforced by the platform, not by policy.
Every agent finding carries its evidence, model version and confidence. Agents run in your environment or an approved no-retention endpoint, are registered in your model inventory, and send every finding to MVGRC.
Built for the boardroom
Escrow stops being an operational risk you hope is under control and becomes a franchise you can measure, show your regulator and grow.
Illustrative projects.
What MVESCROW powers
Start with the escrow your regulator already demands, then extend the same engine across your franchise.
Try the engine
Two of MVESCROW's everyday calculations, running in your browser. Money is handled in integer minor units — paise, fils, cents — exactly as the platform does it. No floating-point money, ever.
Illustrative scenario
A fictional developer asks its escrow bank for a large release against an optimistic progress certificate. Here is what happens when the bank runs MVESCROW.
The developer submits a consultant's certificate showing 35% completion and asks for AED 60 million. Approved cost is AED 300 million; AED 72 million has already been released.
→ Rules engine caps the request at AED 33 million (35% × 300m − 72m) and shows its working.
The Evidence Verification Agent notices last month's certificate said 22% — a 13-point jump far outside the expected build curve — and two site photos reused from another project.
→ The Certifier Integrity Agent adds that the consultant signed 14 certificates this month against an average of 3.
The escrow officer orders the independent inspection the agreement allows. It certifies 28%.
→ Entitlement recalculated to AED 12 million, approved by maker and checker, executed through the core.
An email asks to change the main contractor's bank account.
→ Release Fraud Shield holds it for out-of-band confirmation. The request came from a look-alike domain and is rejected.
Buyers' money that would have left under the original request stays in escrow — with a complete, regulator-ready record of every check and decision.
Fictional entities and figures, for illustration only.
Compliance-first
Jurisdiction templates are configuration, not code — so new regulatory requirements become new rules, not new projects.
Banking-grade by design
Deployment velocity
A controlled pilot that starts read-only, proves itself against your core to the paise, and goes live on real projects inside one quarter.
Questions bank leaders ask
No. Every fiat balance stays in accounts in your core. MVESCROW holds the rules, evidence and a sub-ledger that reconciles to your core. Tokenised escrow runs in wallets controlled by your bank or its approved custodian.
No. Your bank, or the licensed entity named in the agreement, is the escrow agent and keeps the legal duties and the client relationship. Moneyverse provides the software.
No. MVESCROW runs beside Temenos, Finacle, FLEXCUBE, BaNCS, mainframe and in-house cores. MVCORE makes escrow a native product with built-in virtual accounts, holds and tokenised rails — either as an augmentation layer beside your core or as your core.
Never. The deterministic rules engine calculates the entitlement, and named officers approve releases under maker-checker. Agents are capped at "prepare" — they verify, detect and explain, and the platform blocks them from approving or executing.
The agreement always prevails. Every rule links to its clause, every rule set is verified by your legal or escrow team before activation, and changes create a new approved version.
Usually with real-estate project escrow, where regulation already requires the controls. Marketplace and payment-aggregator escrow can run in the same pilot; M&A, trade, purpose-bound and tokenised escrow follow on the same engine.
Pilot programme
We're selecting a small group of pilot banks for MVESCROW. Avoid the long forms and endless fields — book a 30-minute call with our architects and see the engine run on your use case.
MVESCROW capabilities marked as roadmap are under development; pilot availability is subject to agreement. All financial services, payments, escrow and custody services depicted are performed by our licensed partners or the regulated entities utilizing our software.