Skip to content

Pay a contractor for delivered work

Add a milestone, verify the work by hand or by a merged pull request, and let the agent release the pay.

A milestone pays a contractor for a piece of work once that work is verified, instead of on an invoice's due date: five social posts delivered, a design approved, a pull request merged. You add the milestone, someone verifies the work (or GitHub does, for a pull request), and the agent decides on the release within a minute and pays it in USDC on Arc, on the workspace's network: Arc testnet or Arc mainnet. Start with a workspace that is live and has USDC in its operating wallet, testnet USDC on Arc testnet or real USDC on Arc mainnet; Go live sets that up.

Owners and admins add milestones and verify them. Owners, admins and approvers decide a milestone the agent held. Other members see every milestone and its decision, but have no controls here.

Watch it

About a minute: a freelancer paid through a one-time link, released by the agent, and milestone escrow. The guide below goes through each part in full.

Pay a contractor for verified workLength: The live product on Arc testnet, with demo data in the team's own workspace. The freelancer's payment, from the one-time link to the agent paying it, was recorded Oct 15. Recorded Oct 17, 2026.
Read the transcript

Pay a contractor.

Pay that follows verified work, released by the agent.

On Contractors, pay follows verified work instead of a calendar, and every release passes the same checks as any payment.

To pay a freelancer in one step, give their name, what they delivered and the amount.

Vestiarion makes a one-time link for them.

The freelancer adds their own Arc address through it.

A different teammate confirms the address.

Then the agent pays on its own: code checked the payee and the limit before anything was sent.

No person pressed pay.

A milestone's USDC can also be locked in escrow on Arc testnet before the work starts.

Once the work is verified, the agent releases it; from a refund date you set, it can come back instead.

Pay follows the work, and code checks every release.

vestiarion.xyz/docs/guides/pay-a-contractor

The same video is on YouTube.

Pay someone new in one step

To pay someone who is not yet on file for work they have delivered, open Contractors, open New payment, and fill in Pay a freelancer with their details, not yours: Freelancer's name, Freelancer's email if you have it, What they delivered, the Amount (USDC) and, if there is one, a Link to the work. Choose Set up payment. Vestiarion then:

  • adds them as a contractor, with that amount as their payment limit, and screens them;
  • adds the work as a milestone, verified by you, with the note "Delivered work confirmed when the payment was set up";
  • emails them a one-time link to add the address they want to be paid at, and shows you the same link to copy. Copy link is there if they have no email or it does not arrive. The link is shown only then: if it is lost, make a new one on their page, which the line under the link opens. The same email is where they are told once they are paid, with the transaction (see Tell the payee it was paid).
One form sets up the payment; the link goes to the freelancer by email and is shown once to copy.

The link takes them through their side in three steps, and afterwards shows them their payment's status, up to a confirmation with the transaction: Get paid as a freelancer is the guide to send them. When they add their address, the members who can confirm addresses get an email, whose button opens that address on the freelancer's own page (see One page for each contractor). Once someone other than whoever set up the payment confirms it with Confirm address, there or in their row on Counterparties, the agent pays the milestone within a minute. Whoever set up the payment created the link, so they count as having given the address: if they confirm it themselves, the first payment waits for another owner, admin or approver to pay it with Pay now, or for them to, if they are the only person in the workspace who can approve payments. Until the address is confirmed the milestone is listed under Needs you on Contractors, reading "Address to confirm"; opened, its row says to confirm it on their page, and Open their address opens it there. Before they add an address, it reads "Waiting for an address". In a live workspace nothing is paid before that; a sandbox pays them simulated, at once. The steps below are the same path one at a time, for someone already on file.

1.Add the contractor

Open Counterparties and add the person or studio you pay, with Role set to Contractor and a Payment limit (USDC) at least as large as the milestones you will add. A vendor can be paid for milestones too; a client cannot.

The agent pays to the counterparty's Arc address. To have the contractor enter it themselves, open their row on Counterparties and choose Ask for address, then Create link, and send them the link. The row's Open their page opens their page, which has the same controls under Payee link and Payment address, with the links made before. They need no account. Once they have entered it, choose Confirm address: until someone confirms a new address, the agent waits. Whoever created the link counts as having given the address, so its first payment needs a second person: someone else confirms it, or someone else pays that first milestone with Pay now (see Two people before the first payment).

2.Add the milestone

Open Contractors, open New payment, and choose Milestone intake:

  • Contractor: who is paid.
  • Amount (USDC): what the work is worth.
  • Work delivered: what they did, in a few words. It is the title on the milestone's card.
  • Evidence link (optional): where the work can be seen. A GitHub pull request is checked for you; once your workspace connects GitHub, one in a private repository too, and the pull request gets a comment once it is paid. Any other https:// link, to a design file or a shared folder, is kept on the card for whoever verifies the work.

Choose Add milestone. The milestone starts pending, and its card says "The agent is waiting for milestone verification." Adding it is signed in the audit log as create_milestone.

3.Verify the work

On Contractors, the tiles count what needs you, what waits for verification, what is verified and being paid, and what has been paid. Under Milestones, each milestone is one row, in three groups: Needs you (held, or refused by code), In progress (waiting for verification, or verified) and Paid and closed (the latest ten; Show all lists every one). Open a row to see its card, and under it the milestone's verification and escrow.

How a milestone becomes verified depends on its evidence:

  • A GitHub pull request. The form answers "The agent checks the pull request within a minute, and decides on pay once it is merged." Each cycle asks GitHub whether the pull request was merged. Once it was, the card's Verified by reads "merged PR", linked to the pull request, and the ledger records verify_milestone_github.
  • An Asana task. Once your workspace connects Asana, open the milestone's row and link it to the task the work is delivered in, under Accept from Asana, and write the acceptance criteria from your agreement. When the task is completed in Asana, the card says Ready for acceptance: check the deliverables against the criteria and choose Accept the work. A completed task alone never verifies the milestone, an acceptance by the payee is refused where Vestiarion can tell who the payee is, and a task reopened or changed after acceptance is held for review once Vestiarion reads that before the payment is sent. The ledger records milestone_accepted.
  • A Linear issue. Once your workspace connects Linear, open the milestone's row and link it to the issue the work is delivered in, under Accept from Linear, and write the acceptance criteria from your agreement. When the issue is done in Linear, the card says Ready for acceptance: check the deliverables against the criteria and choose Accept the work. An issue marked done alone never verifies the milestone, an acceptance by the payee is refused where Vestiarion can tell who the payee is, and an issue reopened, canceled or changed after acceptance is held for review once Vestiarion reads that before the payment is sent. The ledger records linear_work_accepted.
  • A Jira issue. Once your workspace connects Jira, open the milestone's row and link it to the issue the work is delivered in, under Accept from Jira, and write the acceptance criteria from your agreement. When the issue is done in Jira, the card says Ready for acceptance: check the deliverables against the criteria and choose Accept the work. An issue marked done alone never verifies the milestone, an acceptance by the payee is refused where Vestiarion can tell who the payee is, and an issue reopened, resolved as not done or changed after acceptance is held for review once Vestiarion reads that before the payment is sent. The ledger records jira_work_accepted.
  • Anything else. The form answers "Verify it once the work is delivered, and the agent decides on pay within a minute." When the work is in, open the milestone's row, open the work from the card's Evidence link, type what you checked into the box under the card (it reads "Evidence checked or approver note") and choose Verify manually. The ledger records verify_milestone_manual, with your note and who you are. Revoke manually takes it back, until the milestone is paid.

4.The agent releases the pay

Within a minute of a milestone being verified, the agent decides whether to release it now, and writes its reasoning on the card: who the contractor is, their screening, and their history with the workspace. The decision is signed as milestone_release or milestone_hold.

Code checks every release the model asks for. It refuses one for a contractor screened high risk, or one above the contractor's payment limit, and the card says so. It also holds a release the operating wallet cannot cover, counting the releases before it in the same cycle, rather than send a transfer that would fail. A milestone locked in escrow is paid from the escrow. A released milestone's card links its transaction on Arc.

A held milestone is decided again once something it was held for changes: the contractor's payment limit, their screening, the milestone's evidence, or, for one held for want of cash, the cash in the operating wallet and the reserve. Raising the limit on the counterparty brings the agent back within a minute. The ledger records milestone_reopened with what changed, followed by the new decision.

Several milestones at once

On Arc testnet, when a cycle releases two or more milestones, the agent pays them together: one transaction pays every contractor. Each milestone is still decided and checked on its own, and keeps its own signed milestone_release entry. On Arc mainnet each milestone is paid in its own transaction, never in a batch.

  • One transaction, all or none. The operating wallet is a Circle smart account, and the batch is one call to its own executeBatch. The wallet sends USDC to each contractor in turn, and if any transfer fails, none happens. So the agent sends a batch only when the operating balance covers all of it. Otherwise it pays each milestone alone, as many as the balance allows.
  • What the card says. A milestone paid this way says it was paid in one Arc transaction with the others, for example "paid in one Arc transaction with 2 other milestones". It links the shared transaction. The ledger entry's execution.batch holds the batch's key and size.
  • Fees. The transaction's fee is split equally between its milestones.
  • What is never batched. A milestone locked in escrow is released on its own, as is the only milestone released in a cycle.
  • If Circle's answer is lost. The milestone stays verified, and the agent looks the batch up on Circle the next cycle. It never sends the batch's payments again alone while Circle might have it. If Circle never received the batch, each milestone is then paid alone.

When a milestone is held

A held milestone is listed under Needs you, and its row says in a few words what it waits for, under its title: for example "Circle did not send it" or "Limit lowered by a screening match". Open the row. Above its card, What it waits for says it in a sentence, with a link to where it is settled.

Each held row says what it waits for; opened, it offers Pay now and Close without paying.

What it waits for decides what you can do:

  • The contractor's screening, limit or address. For example "A screening match lowered Quoc Duong's limit to 0.25 USDC, below this milestone's 1 USDC." Settle it on their page: Open Counterparty, at the end of What it waits for, opens the part of it that settles the hold, where you review the match, raise the limit, or confirm the address. Once the limit or the screening changes, the agent decides the milestone again within a minute. It cannot be paid by hand before then.
  • Circle did not send it. Nothing moved. Pay now sends it again, on its own, as a new attempt.
  • Not screened yet. Screening could not run when the contractor was added, so the agent releases nothing to them. Screening runs again at every cycle, and once it gives a verdict the agent decides the milestone again. Pay now pays it anyway.
  • Waiting for cash. The operating wallet did not hold the milestone's USDC when the agent released it, so nothing was sent. The agent decides it again on its own once cash comes in: USDC added to the operating wallet, or brought back from the reserve. Pay now pays it once the wallet holds it, or the reserve covers what it lacks. On Arc mainnet, the figure it names leaves out the 0.10 USDC the wallet keeps for gas.
  • The agent held it, by its own reasoning or because paying it would have taken the agent past its spending limit. Pay now overrides the hold. Someone other than whoever added the milestone must choose it: "You added this milestone, so someone else must approve paying it." If you are the only member of the workspace who can approve payments, there is nobody else to choose it, so Pay now stays enabled for you and the row says "You added this milestone. You are the only person in this workspace who can approve payments, so you can pay it yourself, and the ledger records that you did." The milestone_approval_paid entry then ends "(entered and approved by the workspace's only approver)".

Pay now asks first, naming the amount and who is paid. It then pays the milestone as the agent would, from escrow if it is locked there. It still refuses a contractor screened high risk, a milestone above the contractor's limit, an address no one has confirmed, and an operating balance below the milestone. A transfer that may still settle is never sent twice: Pay now only records it, and its confirmation asks to check that payment instead, with Check it. One Circle never answered is looked for on Circle first, with Look first. The audit log signs the payment as milestone_approval_paid, with who chose it. What to do about a payment that does not go through is in When a payment does not settle.

Close without paying asks for a reason. The reason is kept on the milestone and in the audit log, signed as milestone_closed. The milestone moves to Paid and closed, marked "Closed without paying", and is never paid after: it cannot be verified again, and the agent never decides it. Closing is refused while a transfer for the milestone may still settle, and while its USDC is locked in escrow: refund the hold first.

Lock a milestone in escrow

A live workspace on Arc testnet can lock a milestone's USDC in a contract on Arc testnet before the work starts, so the contractor can see the money is set aside for them. Escrow runs on Arc testnet only: on Arc mainnet, Contractors shows no escrow.

  • Set it up once. On Contractors, an owner or admin opens Milestone escrow and chooses Set up escrow. Setting it up:

    • creates a deployer wallet;
    • sends that wallet 0.1 USDC of gas from the operating wallet;
    • deploys the contract through Circle's Smart Contract Platform.

    If it is interrupted, choose Finish setting up: nothing is deployed twice.

  • Lock a milestone. Open the row of a milestone that is not verified yet; under its card, set Refundable to this workspace from and choose Lock in escrow.

    • The contractor needs a confirmed Arc testnet address. The form names the address the hold will pay; that address cannot change afterwards.
    • The card then reads, for example, "2 USDC locked in escrow for 0x67C8…0504 until 31 Oct 2026", with the transaction that funded it.
  • What the contract allows. Only the workspace's operating wallet can call it, and only two things can happen to a hold, once:

    • it is released to the contractor's address;
    • from the refund date, it is refunded to the workspace.

    Before that date, the money can go nowhere but to the contractor.

  • Release. Once the milestone is verified, the agent pays it by releasing the hold instead of sending a transfer. It holds the milestone for a person instead when:

    • its amount changed after it was locked;
    • the contractor's address is no longer the one the hold pays. Refund it from its date, then pay the new address.
  • Refund. From the refund date, a hold that is still on chain shows Refund from escrow.

The contract was written for Vestiarion and is not audited. Its source, its functions and the address it runs at in production are on Contracts on Arc.

5.Read it in the audit log

Open Audit log to see the milestone's whole story in order, each entry signed: create_milestone when it was added, the verification, and the agent's release decision with its reasoning and its transaction. Verify an audit export shows how someone outside the workspace can check the same entries.

For one milestone, its card's Why it was paid (or Evidence so far, before it is paid) puts the same story on one page, link by link: its terms and who added them, the merged pull request GitHub reported or the person who verified the work, the payee, the decision, the people, and the payment read back from Arc, each fact marked with how it is known. See Why a payment was paid.

One page for each contractor

Every counterparty has a page of its own, a contractor, a vendor or a client alike. Open their row on Counterparties and choose Open their page; All counterparties takes you back to the row. The page puts everything Vestiarion holds about them in one place, for every member of the workspace, viewers included. Nothing here makes a payment: the agent pays under its rules, and people decide in Approvals and on Contractors.

From the top:

  • The tiles. What is Owed to them and what was Paid to them, each per currency: USDC and EURC are never added together. Then the state of their Address, and, for an owner or admin, their Payee link.
  • Needs you and Waiting on them. Under the tiles, what is waiting and on whom, each line a link to the part below that holds it. Needs you is your side: a changed address to confirm or a frozen one, milestones held for a decision, their bills waiting for a person, and, for a client, refunds to them to pay in Approvals. Waiting on them is theirs: an address when they have none, their answer to a payee link that is out, milestones they have still to deliver, documents asked for on their bills, and, for a client, invoices to them not paid yet. Both come from what the page has already read; when part of it could not be read just now, they say so rather than showing nothing.
  • Profile. Their screening, their limits, where they are, when they were last screened, their billing email, and whether the agent needs a purchase order before it pays them. An owner or admin edits each here, as on the list; whoever decides payments reviews a screening match.
  • Payment address. The whole address, never cut short, with Open on the explorer. An owner or admin edits it; an owner, admin or approver confirms a changed one with Confirm address, as does an accountant while co-signing is on.
  • Payee link. The one-time link that asks them for their address, and for their invoice (see Payee link states below). Only an owner or admin sees it; anyone else reads "An owner or admin sends and stops payee links."
  • Milestones. The open ones, and those closed without paying. Each row opens its milestone with Open in Contractors, where it is verified, paid or closed: none of that is done from this page.
  • Bills from them. Their open bills, by due date, and the latest rejected ones. Open in Bills & receivables opens a bill where it is decided. For a client, this part is their invoices instead, and below them Refunds to them: what you pay a client back, open by due date, then the latest 10 Refunded. The agent never pays a client, so each refund waits for a person, who pays it in Approvals. A refund is not counted in what the client owes, nor in Payments from them.
  • Payments. Their paid milestones and bills, newest first: the latest 10, or every one with Show every payment. A paid milestone is dated by when its payment was confirmed; one whose payment and history could not be read just now names no day and comes last. Each paid bill says where its receipt is, to every member: Receipt shared, Receipt link stopped, No receipt shared, or "No receipt: not paid on chain". In a live workspace, an owner or admin shares one from here too, except while whether it is shared could not be read: sharing again would stop a link already sent. A payment sent to an address they no longer have says "Paid to an earlier address", with that address on the explorer.
  • Documents. The documents the agent asked them for on their bills, with the purchase order number and note they typed, and the Invoices sent for review that name them: captured with the browser extension, or sent by them through their payee link.
  • History. The latest changes to them, each linked to its entry in the Audit log, where its signature is checked. All of it in the Audit log lists every one.

A part that could not be read says "Not read just now. Reload the page in a moment.", and its tile says it was not read: never zero, never none. A record whose history was read only in part says "Some of this record's history was not read; the Audit log has all of it."

Copy an address safely

Copy address shows only for an address that was set when they were added, or confirmed since, that is not frozen, and that looks like no other counterparty's address and none they had before. Otherwise one line says why, for example "Copy comes back once someone confirms this address." A lookalike address is made to pass a glance at its first and last characters, so its line ends "Check every character on the explorer." Do that before you paste it anywhere money is sent from.

Under Payee link, an owner or admin sends, renews and stops the link with the same controls as on the list. Below them are the latest five links, newest first, each naming who made it, in one of these states:

  • Out: not used, not expired and not revoked.
  • Replaced by a newer link: making a new link stops every earlier one that was not used.
  • Revoked: someone stopped it.
  • Expired unused: it ran out before they used it.
  • Used, with their invoice when the link asked for one: Invoice sent, Waiting for their invoice until 30 days after they used it, or Invoice closed.

The list ends "The latest 5 links; every one is in History and the Audit log." and "A used link's status page stays open to the payee for 30 days." A link's address is shown once, when it is made, and a receipt's link once, when it is shared: this page never shows either again.

Edit this page on GitHub (opens in a new tab)