Where the money
waits.
Money on a car deal usually moves in the dark: a wire sent on trust, conditions unwritten, release at the other side’s convenience. This page posts the escrowed-funds face of the deal — held balance, release conditions, settlement events — each with value, source, and timestamp on platform.do financial rails. Both sides read the same page. Reading it is free. No account.
An agent settling for you under a Mandate reads this same face — what it brings back is the posted state you are reading now.
A VIN is 17 characters and never uses I, O, or Q.
7MMVABDM3RN163785
2024 Mazda CX-50
- 01Held balancefunds received into escrow for this deal · value · source · timestamp — never “in process”posts live
- 02Release conditionstitle.vin/
7MMVABDM3RN163785 transport.vin/ 7MMVABDM3RN163785what must post before funds move — title conveyed · delivery confirmed · signatures captured — one condition per line, met or unmet, each naming the event that meets itmet or unmet - 03Eventsreceived · conditioned · released — each dated, sourced, and typedas they happen
- 04Releasedbuy.vin/
7MMVABDM3RN163785funds out, to whom the order names — the release posts back from the one order as an eventposts live
Figures render live at the address. This page states structure, not balances — a slot the record cannot fill reads $ — and says so, never an estimate.
escrow.vin read: $0 · every VIN, every visit · no account
the money railplatform.do financial rails hold the funds; settlement runs inside the one order at buy.vin. This address attests the rail and transacts nothing.
Look up. Read. Settle.
The Held-Funds Plan — three steps, and the third one is the close.
- 01Look upA VIN at escrow.vin/{VIN} — the deal’s funds face assembles from the record: what came in, what holds it, what lets it go. Reading it is free, no account.
- 02ReadHeld balance, release conditions, and settlement events, each posted with value, source, and timestamp. A condition is a line, not a vibe: a condition not yet met posts as unmet, with what would meet it named. “In process” is not a state on this page.
- 03SettleInside the one order at buy.vin — settlement is that order’s act, and the release posts back to this record as an event, dated and sourced. You are one step from the close.
One page, both sides of the wire.
Sending the funds
you wire against conditions, not against trust
The wire lands in the held balance and posts with source and timestamp the moment it does. Release waits on lines you can read — title conveyed, delivery confirmed, signatures captured — each a typed event the record either carries or does not. Nobody’s convenience is a condition.
the held balance · conditions, met or unmet · the release
Waiting on the funds
the money is posted before anything conveys
The seller reads the same page: the balance is posted, not promised, and the conditions name exactly what conveys before funds move. Sign the title over against a posted balance — not a screenshot of one, not an inbox that answers first.
the held balance · the release event · the payee
The same page, the same lines, the same timestamps — read from opposite sides of the wire. That is the point.
Questions with posted answers.
Where is my money?
In the held-balance slot, posted with value, source, and timestamp — or the slot reads $ — and says the record does not carry it. Never “in process.”
What releases it?
The conditions, one per line. Each names the event that meets it — title conveyed posts from the paper lane at title.vin, delivery confirmed posts from transport.vin — and each event posts when it happens, dated and sourced.
Does escrow.vin hold the funds?
No. The rail holds them — platform.do financial rails — and settlement runs inside the one order at buy.vin. This address attests the rail and transacts nothing: it is the deal’s funds face, not its counterparty.
Both sides see this?
The same page, the same lines, the same timestamps. A buyer, a seller, and any agent settling under a Mandate read one funds face — that is the point.
What does a read cost?
$0, posted like every other number — escrow.vin read: $0. Every VIN, every visit, no account.
The release carries.
answers forescrowsserves this address — 301, one door
on the rail, heldpayments.vinthe Stripe Connect settlement rail — where counterparties onboard for payouts, held until it binds; the rail settles, this address attests
the free facesvalues.vin · specs.vin · listings.vin · sticker.vin — read free before any paid report; the record deepens at vhr.vin when the deal needs it
For the agent you send
The agent reads the same record you do. Same two routes, three representations — the numbers never differ between them.
motions: B2A2C · B2A2B
- B2A2C — an agent acting for a consumer — everything it does survives being shown to them afterward
- B2A2B — agents brokering between businesses — Mandate presented, fee disclosed, settlement three-way
curl https://escrow.vin/ -H 'accept: text/markdown' → the markdown twin of this page
curl https://escrow.vin/{VIN} -H 'accept: application/json' → the record as typed evidence objects
curl https://escrow.vin/{VIN} -H 'accept: text/markdown' → the record's markdown twinMachine surfaces on this host: /llms.txt · /icp.json · /.well-known/agents.json · one estate MCP server — apis.vin/mcp (every door a lens; tool results carry the door URL).
Attribution: X-Client-Type: html | md | json | mcp — read for agent-led demand attribution; it never changes the record.
No gate on this door's two routes — keyless reads, no account. Gated actions elsewhere on the estate return a typed OFFER (posted price · hard ceiling) or a NEEDS_HUMAN handoff, never a dead end.