Every trade on Splitvy carries two natural fears. The buyer thinks: "What if I pay and never get working access?" The seller thinks: "What if I hand over access and never get paid?" A good system has to answer both at the same time — protecting one side can't mean exposing the other. Escrow is how Splitvy answers both at once.

This article opens up that machinery so you can see exactly where your money is at every moment, and why it can only ever move in a way that's fair.

What escrow actually means here

"Escrow" just means a neutral party holds the money until the deal is done. On Splitvy, that neutral party is the platform's internal ledger.

When you join a group, the seat price does not go to the creator. It moves out of your spendable balance and into a held balance inside your own wallet. The money has left your control — so you can't accidentally spend it twice — but it hasn't reached the creator either. It sits in the middle, committed but not delivered, waiting for the one event that unlocks it: your confirmation that access works.

The wallet, in buckets

To keep money in flight from ever being confused with money you can spend, your wallet balance is split into buckets. For escrow, three matter most:

• Available — your spendable balance. Deposits land here; joins and offers are funded from here.

• Pending — money held in escrow for a group you've joined. Committed, but not yet released.

• Earnings — money released to you as a creator, ready to withdraw.

Every time money moves between buckets, the change is written to an immutable ledger in the same breath. The buckets can never quietly drift out of sync with the record.

The lifecycle of a single trade

Here's the full journey of one payment, step by step:

1. Join. You pay the seat price plus the platform fee. The seat price moves from available into pending (escrow). The fee is the platform's; the rest is held for the creator.

2. Deliver. The creator marks the access as delivered and provides the details.

3. Confirm. You log in, verify it works, and confirm.

4. Release. Only now does the held seat price move from your pending bucket into the creator's earnings. The trade is complete.

Read that ordering carefully, because it's the whole safety model. The release only happens after your confirmation — so a creator can never be paid for access they didn't deliver. And the money is already committed the moment you join — so you can never take access and then refuse to pay. Both fears, answered by the same sequence.

A worked example

Suppose a seat costs $10 and the join fee is 5%. When you join, $10.50 leaves your available balance: $10 goes into pending (escrow) and $0.50 is the platform fee. The creator sees a new member but hasn't been paid yet. They deliver access; you confirm; the $10 moves from your pending bucket into their earnings. The platform keeps the $0.50 as its fee for providing the escrow, the marketplace, and the dispute protection. If the trade had failed instead, the full $10 — often the fee too — would have come back to you.

When the creator goes quiet

What if a creator takes your money's worth of a seat but never delivers? You're covered by a timer. Every escrow has a delivery window. If the creator doesn't deliver and you don't confirm within it, an automatic job refunds the held amount back to your available balance. You don't have to notice, complain, or chase anyone — the refund fires on its own.

When the two of you disagree

Sometimes access is delivered but something's wrong — it doesn't work, it's not what was described, or it breaks. That's what disputes are for.

1. Raise it. You open a dispute on the membership. The instant you do, the escrow freezes — the money can't be released or refunded while the dispute is open.

2. Both sides submit evidence. You explain the problem; the creator responds.

3. An administrator rules. They review the evidence and either refund you (and free the seat) or release the funds to the creator.

4. Or it auto-resolves. If the creator never responds within the configured window, the dispute resolves in your favour.

A frozen dispute is untouchable until it's resolved, which is what stops the nightmare scenario of a refund and a release both firing on the same money.

Why it can't be gamed

Under the hood, every money movement is protected by the same discipline. Balance changes and their ledger entries are written together, inside a single database transaction. State changes — like releasing escrow — use an atomic check that only succeeds if the money is in exactly the state it's expected to be. If a dispute just froze the escrow, a release attempt finds nothing to release and simply does nothing. Duplicate credits are rejected at the database level. And every administrator action is written to a tamper-evident audit log with a reason attached.

Nobody has to trust anybody, because the money can only move in ways that are fair to both sides — and every move is on the record.

Frequently asked questions

Where exactly is my money after I join?

In your own wallet's pending (escrow) bucket. It's left your spendable balance but hasn't reached the creator. You can see it there until you confirm or a refund fires.

Can a creator force me to release the funds?

No. Release only happens on your confirmation, on an automatic timeout in your favour, or on an administrator's dispute ruling. A creator can't trigger it themselves.

What happens to the fee on a refund?

A refund returns the amount that was held. The platform's fee model is designed so a failed trade doesn't leave you out of pocket for the platform's cut.

That's escrow: not a slogan, but a sequence — hold, deliver, confirm, release — that quietly makes every Splitvy trade safe for both people in it.