Skip to main content
Every payment on Fundwork follows the same transparent, on-chain flow — work gets approved, USDC moves on Base, and both parties receive a verifiable completion receipt. This process applies to all three work types: contracts, bounties, and campaigns.

​
End-to-End Payment Flow

1

Work is submitted and reviewed

Talent submits their completed work through Fundwork. The client reviews the deliverables against the agreed scope before taking any payment action.
2

Client approves the work

When the client is satisfied, they approve the work inside Fundwork. Approval is the trigger that initiates the payment — no manual transfer is required.
3

USDC is sent on Base

Fundwork sends the agreed USDC amount directly on Base (Coinbase’s Ethereum L2). The transaction is recorded on-chain and assigned a unique transaction hash.
4

Talent receives funds at their payout address

The USDC lands in the talent’s configured payout address — a Base-compatible wallet they set in their Fundwork profile. Funds are available as soon as the transaction confirms, which typically takes seconds on Base.
5

A completion receipt is generated

Fundwork automatically creates a completion receipt for both parties. The receipt includes the USDC amount, work title, the .base.eth names of both parties, a status of Paid, and the on-chain transaction hash you can verify at any time.
This same flow applies whether you’re working on a contract (ongoing scope), a bounty (single deliverable), or a campaign (milestone-based project). Payment always settles in USDC on Base.

​
What Each Party Sees

Talent

You receive USDC at your configured payout address and can view the completion receipt — including the transaction hash — directly in your Fundwork dashboard.

Client

You initiate approval and can view the same completion receipt confirming the payment amount, recipient, and on-chain transaction proof.
Make sure your payout address is set and correct in your profile before a client approves your work. Payments are sent directly to that address and cannot be redirected after the transaction is submitted.

​
Under the Hood

The flow above is what you see as a user. If you want to understand what actually happens across the stack when a payment settles, the following technical pages go deeper.

Payment Architecture

How the backend prepares a payment, how USDC moves on Base, and how transactions are verified server-side before a payment is marked confirmed.

Escrow Design

The planned escrow model for opportunities that need funds committed before work begins. Escrow is not yet deployed in alpha.

Accounts & Authentication

How Privy authentication and Base Account fit together, and what account abstraction means for the payment flow.

Gasless Transactions

What paymasters solve, and the planned policy for sponsoring eligible Base transactions before public launch.
Fundwork is in alpha. Direct settlement is the current payment model. Escrow, gas sponsorship, and related capabilities are planned architecture and are labeled as such on their respective pages.