Trust · Escrow Explained

How Escrow Works

Escrow is a simple idea with a strict order: the scope is agreed in writing, the buyer’s payment is held by the platform, the dev builds, and the money moves only when the buyer approves the delivered work. This page explains each step, the dispute route, and the legal document underneath it.

BLOXWORK, the most trusted Roblox developer marketplace in the world.

Escrow on every order

Your money stays held until you approve the finished work. Only then does the dev get paid.

How escrow works
Devs verified with real ID

Every dev shows ID to earn the Verified badge. The document stays private. Only the badge is public.

About the badge
One fair fee

10% of the job, never more than $1,000. No buyer fees. Nothing stacked on top.

The fee rule

Step one, the scope is the contract

Every BLOXWORK order begins as a package: a named deliverable, a written scope of what is included, a delivery time, a revision count and a price, set by the developer and accepted by the buyer before payment. At checkout the buyer also accepts the Terms of Service and the Escrow and Payments Agreement, and that acceptance is recorded with its date and document version. There is no "we talked about it in DMs" layer, the order is the agreement, and both sides can point at the same words.

This step does more work than it looks. Most commission disputes in this market are not theft; they are two people discovering at delivery that they meant different things. A scope written before money moves turns that discovery into a conversation that happens when it is still free.

Step two, payment is captured and held

The buyer pays the full package price, and the payment is captured to BLOXWORK and held. It is not transferred to the developer, not partially, not as a deposit. The developer can see the order is funded, which is their proof the client is real and committed; the buyer’s money has not left the platform’s hands, which is their proof it can come back if the work never comes. Checkout runs through Stripe. Stripe holds the payment in escrow from the moment it is paid, and it stays held until the buyer approves the delivered work. BLOXWORK tracks the state of the order and shows it to both sides at every step.

While the money is held, the order moves through visible states: in escrow, in progress, delivered. Revisions included in the package are tracked against the order, so "you already used your revisions" is a fact on a screen, not a claim in an argument.

Step three, approval releases, nothing else does

The developer delivers through the order. The buyer tests the work against the written scope, plays it, walks it, runs the reproduction case, taps through the screens, and either requests an included revision or approves. Approval is the single trigger that releases the payment: a transfer of the price minus the platform fee (10%, capped at $1,000) goes to the developer’s connected payout account. Silence does not release it; time passing does not release it; only the buyer’s approval does.

After release, the buyer can leave a star review with a written reason, required, not optional, and that review moves the developer’s Trust Score: +2 for five stars, +1 for four, 0 for three, minus 1 for two, minus 2 for one. The review system is welded to released orders, so the record a future client reads was written by people who actually paid, received and judged real work.

When it goes wrong, disputes and refunds

If the delivered work fundamentally misses the agreed scope, or never arrives, the buyer opens a dispute instead of approving. The held payment freezes where it is, still on the platform, not with either party, and the Refund and Dispute Policy governs the review: what the scope promised, what was delivered, what the order record shows. Where the policy finds for the buyer, the refund is paid out of the held funds. Where work was delivered as scoped, the release stands. Either way the decision stands on documents both sides accepted at checkout, not on who argues longest.

This is the entire difference between escrow and a promise. A promise depends on the other party’s mood at the worst moment of the relationship. Escrow was designed before the worst moment, by people who assumed it might come, and it keeps the money exactly where the decision needs it to be.

The legal document underneath

The mechanics on this page are the plain language version of the Escrow and Payments Agreement (version 2026 to 11 to 18), which is the governing text: it defines the holding, the approval trigger, the fee, the dispute route and the refund terms, and it sits in the legal hub linked from every page footer, next to the Terms of Service, the Developer Agreement and the Refund and Dispute Policy. BLOXWORK is independent and is not affiliated with Roblox Corporation; the escrow described here is BLOXWORK’s own arrangement with its users, run through Stripe’s payment and Connect infrastructure.

Read the agreement before your first order, the way you would read any document that will hold your money. It is written to be read, and the fact that it exists, in public, before you pay, is itself part of the protection.

How hiring works here

1
Agree the scope & pay into escrow

The scope is in writing before you pay. BLOXWORK holds your money. It does not go to the dev yet.

2
The dev builds

Work runs against the agreed scope and delivery time. Revisions in the package are tracked on the order.

3
You approve, money releases

Check the work. Only your approval releases the pay, minus the 10% fee capped at $1,000.

Are you a Roblox developer?

Keep 90% of every job. The fee never takes more than $1,000, even on a $25,000 job where a 20% platform takes $5,000. Your pay sits in escrow before you start and lands in USD when the client approves. Show your ID once, wear the Verified badge, and let clients trust you on sight.

Questions, answered

Who holds the money during escrow?

BLOXWORK holds the order’s payment state, with the payment itself processed and captured through Stripe to the platform, never sent directly to the developer. It is released to the developer’s payout account only when you approve the delivered work, or resolved under the dispute policy.

What does escrow cost?

There is no separate escrow charge and no buyer fee. The platform’s single fee is 10% of the order, capped at a flat $1,000, taken from the release to the developer and shown in the checkout math before you pay. The buyer pays the package price, exactly.

Can a developer get paid without my approval?

No. Approval is the only release trigger in the normal flow. If a dispute is opened, the held funds are resolved under the Refund and Dispute Policy based on the scope and the order record, the developer cannot unilaterally take the money at any point.

What if the developer never delivers?

Open a dispute on the order. The payment is still held, so a failure to deliver resolves as a refund from held funds under the policy rather than a loss you chase. Delivery deadlines live in the package scope, which is what the dispute is measured against.

Is escrow live right now?

Yes, it is live. Checkout runs through Stripe, and your payment is held in escrow by Stripe until you approve the delivered work. On approval the payment releases to the developer minus the platform fee of 10%, capped at $1,000, taken from the release and never added on top of the price you pay. If a dispute lands before release and the policy finds for you, the held payment comes back to you as a refund.

Keep going

Ready when you are

Browse the marketplace with escrow on every order, or put your own work in front of the clients arriving here.