Your first payment
Add a counterparty and an invoice, run a cycle, and follow the payment to the explorer and the ledger.
This page takes a workspace from an empty book to its first payment on Arc: add a counterparty and an invoice, let the agent decide, and follow the payment to the explorer and the signed ledger. For a payment on Arc, start with a workspace that is live and has USDC in its operating wallet: testnet USDC on Arc testnet, real USDC on Arc mainnet. Go live sets that up. A sandbox on Arc testnet with no wallet can take the first steps now: it simulates its payments, the payee's address included, so the agent decides on your bill straight away. A workspace on Arc mainnet never simulates: nothing moves until an owner takes it live. Until the first payment settles, the console's Get started checklist follows these steps too, and links the next one. In a sandbox with no wallet it starts with Add a supplier, Add or import a first bill, See the agent's decision and Set or confirm the limits, and lists the wallet after them, under To pay on Arc. Approvers and accountants have checklists of their own: see Your first steps, by role.
Who does what:
- Owners and admins add counterparties and invoices, and run cycles.
- Owners, admins and approvers decide the payments the agent holds.
- Accountants book payments in Xero and apply money received: see Accountants.
- Viewers see everything, but have no controls.
Watch it
Under two minutes: a bill the agent pays on its own, one that waits for a second person, and the record of both. The guide below goes through each part in full.
Read the transcript
Your first payment.
A bill the agent pays on its own, one a person approves, and the record of both.
This workspace is live on Arc testnet: the agent pays the bills that pass every check, on its own.
Lumen Print Co. is screened clear, has a payment limit and an Arc address, so it is ready to pay.
Add its invoice: three USDC for a poster reprint, due today, with its purchase order, and the goods received.
The agent usually decides within a minute.
It paid the bill on its own.
Its reasoning: the match is complete, the supplier is clear and under its limit, and the cash covers it.
No discount applies, so paying on the due date is right.
The transfer settled on Arc testnet within a second.
A first payment to a new supplier's address goes another way.
Code holds it until two different people stand behind that address.
Another member reads the reasons in Approvals, and pays it.
Every decision is signed into the audit log, each entry linked to the one before it.
Verify the chain, and it answers: chain intact.
A paid bill can share a receipt. Anyone with the link can check the payment, and it shows no names.
The receipt checks its own signature in the reader's browser.
The agent pays what passes every check, and holds the rest for a person.
vestiarion.xyz/docs/guides/first-payment
The same video is on YouTube.
Your first steps, by role
Each member sees the checklist of their own role, with the next step highlighted and linked, and each step ticked because it happened in the workspace, never by a box a person ticks:
| Role | Where it shows | Its steps |
|---|---|---|
| Owner or admin | Treasury, as Get started | Create the workspace, Add a supplier, Add or import a first bill, See the agent's decision, Set or confirm the limits, then what paying on Arc needs |
| Approver | Treasury and Approvals, as Get started as an approver | Open Approvals, Read why a bill is held, Decide it, or send it back |
| Accountant | The Accountant console, as Get started as an accountant | See Accountants |
A viewer has no checklist.
- Invited by email, you land on your role's first step when you accept: an approver on Approvals, an accountant on the Accountant console, an owner or admin on Treasury.
- Set or confirm the limits names the agent's spending limit as it stands. It ticks once someone changes that limit, or the figure above which a payment needs two approvals, or chooses Keep these limits; it is the workspace's, so one person doing it ticks it for everyone. Only an owner or admin sees Keep these limits.
- Read why a bill is held ticks when you open Approvals while a bill waits there: its card says what the agent decided, why, and what would let it pay. Deciding a bill ticks it too.
- Don't show again hides your checklist for good, in that workspace. An admin sees the owner's steps that only an owner takes, such as Add a wallet and Go live, marked "An owner of this workspace does this step.", with View instead of Start. No checklist offers a step your role cannot take.
Try it with sample data first
To see the agent at work before you set anything up, open the console of a new workspace on Arc testnet; a workspace on Arc mainnet has no sample data. While the workspace has no counterparties and has not connected Circle, the console shows Try it with sample data. Choose Load sample data: it adds six example counterparties, marked Sample on the Counterparties page, with invoices and milestones chosen so that one cycle shows every outcome. The agent usually runs that cycle within a minute on its own; then read the decisions on the console and on Approvals:
- a hosting invoice with a purchase order and goods received is paid;
- an annual support plan with a 2% early-payment discount is scheduled for its discount deadline;
- an overage with no purchase order waits for information;
- an invoice over the counterparty's payment limit is held for a person;
- a print run billed again under a purchase order that was already paid is flagged;
- a catalogue print run due in three weeks, with no discount, is scheduled for its due date. Turn on the agent's early-payment offers in Pay early for a discount on Bills & receivables, and the agent offers it to pay early, by email to you, so you answer as the supplier (early-payment offers);
- a verified contractor milestone is released, and an unverified one waits.
Sample payments are simulated. While Sample data is loaded, the console offers Remove sample data: it removes the sample counterparties and everything recorded against them, and the ledger keeps its entries. Remove the sample before you connect Circle; until then, connecting answers "Remove the sample data first. It exists only to try the agent with simulated payments."
1.Add a counterparty with an Arc address
A counterparty is a business or person the workspace pays or invoices. Open Counterparties, open Add counterparty, and fill in the form:
- Legal or trading name.
- Role: Vendor or Contractor for someone you pay.
- Payment limit (USDC): the most the agent may pay this counterparty in one payment. Screening can lower it: the card shows the limit you set and the current one.
- Chain: the workspace's own network for a payee paid on Arc, Arc testnet or Arc mainnet. On Arc testnet, for a payee who wants USDC on another chain, choose Base Sepolia, Arbitrum Sepolia or Ethereum Sepolia: see Pay a payee on another chain. On Arc mainnet the field offers Arc mainnet, Base and Arbitrum: see Pay a vendor on Base or Arbitrum from Arc mainnet.
- Payment address: the counterparty's address on the chain you chose,
0xfollowed by 40 hexadecimal characters. An address that mixes capital and small letters must match its checksum, or the form says "This address's capital letters do not match its checksum, so a character is likely wrong." A payment to a mistyped address reaches no one, so copy it again from where it came. An address in one case alone is taken as written. - An ENS name or a Basename typed there, such as
northwind.ethornorthwind.base.eth, is looked up under the field: it shows the address the name points to, with Use this address, which puts that address in the field. The address is what is saved, never the name, since a name can be pointed elsewhere later. An address typed or pasted shows its ENS name, when it has one. When the name does not look like the counterparty's, the hint says so, to check with them by a contact you had before: a person can own a name unlike their business's, so nothing is refused. Edit address looks names up the same way. - Jurisdiction, optional: an ISO code or a country name.
- Billing email, optional: a payee is told there each time it is paid (see Tell the payee it was paid), and a client gets the reminders you turn on (see Let the agent remind the client).
Then choose Add and screen. The counterparty is screened as soon as it is saved, and a message gives the result: "Name added and screened: level risk." The agent never pays a counterparty screened high risk. A live workspace screens against OpenSanctions; a sandbox, whose payments are simulated, screens against a short list built into the app.
Every cycle also checks each counterparty's payout address against the addresses on the US Treasury's sanctions list (OFAC's SDN list). An address on it makes the counterparty high risk at the next cycle, whatever its name screens as, with a note naming the address and the listed entry. Dismissing the match, or screening again, does not clear it while the address is listed. The agent never pays such an address, and Approve and pay refuses it: "This payee's address is on OFAC's sanctions list, so nothing is paid to it." Pay now on a contractor's milestone refuses it the same way.
To check vendors before they are in Vestiarion, use the free OFAC vendor check. It checks one name, or a whole vendor list with its wallet addresses, against OFAC's SDN list in your browser, and says why each possible match matched.
If screening cannot run, for example because the screening service does not answer, the counterparty is still saved, and the message says it "was added, but screening is incomplete". Its row then reads Not screened yet, and the agent pays it nothing: a payable to it is held with the rule counterparty.unscreened, and so is a contractor's milestone. Screening runs again at every cycle. Once it gives a verdict, the agent decides what it held again, within a minute. A person can still pay it from Approvals.
Under Counterparty book, each counterparty is one row: its role and chain, its risk, what it may be paid now (Allowed now), its address, and what it needs before the agent can pay it. The rows that need someone come first: Review match, Confirm address, Address needed and Not screened yet, then Ready to pay. Open a row for its screening, limits, history and address.
If screening matched someone else with the same name, the counterparty's row reads Review match; open it to see the match under Screening match, with what that does to its limit. A member who can approve payments can choose Not this person, say why, and confirm with Dismiss the match. The counterparty is screened again at once without that match (a match with anyone else still counts), the ledger records screening_match_dismissed with the reason, and payments held on the old risk are decided again within a minute. A name can match several people: the box then says how many others it matched, and Not this person lists every one, with its score, so one review dismisses them all under one reason (each is recorded, and a match not listed still counts). A match recorded before October 2, 2026 reads "This match was recorded before Vestiarion kept every possible match." Choose Screen again first, and Not this person appears.
Without an address, a payment is held
The form marks Payment address "Optional until payment setup", but the agent can pay only a counterparty that has one. As the Go live page puts it, "A payment to a counterparty without one is held for review." You can add it later with Edit address on the counterparty's card.
Changing a payment limit
Owners and admins open the counterparty's row and change its limit with Edit limit, under Configured limit. Enter the new Payment limit (USDC) and choose Save limit. Allowed now follows at once: the whole limit for a counterparty screened clear, a quarter of it for medium risk, and 0 for high risk. A vendor or contractor always has a limit, because without one the agent could pay any amount. The ledger records who changed the limit, and from what to what.
To see first which of this counterparty's bills a new limit would have held or let through, choose Try it on past decisions in the same dialog: see Try a limit before you change it.
Pay a counterparty without purchase orders
The agent pays an invoice on its own only when its three-way match is complete: the goods or services received and a purchase order on file. Some suppliers never issue one, such as a utility or a subscription. A vendor's or contractor's row on Counterparties shows Purchase orders: "Needed before the agent pays", as for every counterparty at first, or "Not needed · goods received still is". Owners and admins choose Change beside it, then Pay without purchase orders or Require purchase orders.
In shadow mode, Add counterparty asks about a vendor or contractor: Does this supplier send you purchase orders? No adds it paid without purchase orders, and Yes as needing them. See Shadow mode.
- Paid without purchase orders. The agent pays the counterparty's invoices with no purchase order on file. The goods or services still have to be marked received, and every other check stays. Its invoices that waited only for a purchase order are decided again within a minute.
- Needing them again. The agent asks for a purchase order before it pays or schedules any of its invoices. A payment already scheduled without one waits for the details on its day.
- Enforced in code. The model is told whether the counterparty needs purchase orders, and the written policy asks for information on the same condition. If the model chooses to pay or schedule an invoice whose match is incomplete anyway, code refuses it, and the invoice waits for the details as if the agent had asked.
- Recorded. The ledger records who changed it, as
counterparty_purchase_orders_changed.
Ask a payee for their address
You don't have to collect a payee's address yourself. In the counterparty's row, owners and admins choose Ask for address, then Create link:
- The link is shown once, with Copy link. Send it to the payee however you usually reach them.
- The payee opens it without an account. They see which business wants to pay them, and on which chain, and enter their own address there: the chain the counterparty is paid on, Arc unless you chose another, such as Base.
- Two boxes under the dialog's text ask for more. Both are off unless you tick them, so a link made without them works as above, and so does every link made by Ask every payee for an address, by paying a freelancer or through the API:
- Also ask for their invoice, for a vendor or a contractor. After their address, the page asks for their invoice: its number (one line, no link), the amount in USDC, the due date, and optionally a note of plain text and the invoice as a PDF or text file of up to 4 MB. Only the file's text and its SHA-256 are kept, never the file, and no model reads it. A payee who already has an address of their own on file can keep it and go straight to the invoice, recorded as
counterparty_address_kept; a mirror address made in shadow mode is not theirs to keep. A link takes one invoice, while it works or within 30 days after the payee sent their address, unless you stop it, as below. - Let them choose where they are paid, for a vendor with no address yet, on a network that pays more than one chain: Arc mainnet and Base, or Arc testnet and the Sepolia chains. A workspace that pays from your own wallet through version 1 of its contract pays on its own chain only, so the box is not offered there. Nor is it for a vendor with a milestone not yet paid or closed, or an open bill in another currency than USDC: a milestone is paid on the workspace's own chain, and only USDC crosses chains. The page asks the payee where their wallet receives USDC before their address, and writes the chain with the address. Each network it offers says what sending there costs your business, as Circle quotes it when the page opens: "No fee to send it here." on your own network, and, for example, "Acme pays about 0.055 USDC to send it here." on another, or "Acme pays a small fee to send it here." when Circle did not answer within 3 seconds. Below them: "You get the full amount on any of them: no fee is taken from what you are paid." The chain can be chosen only while the vendor has no address, no payment and nothing of that kind open; otherwise the page names the chain on file.
- Also ask for their invoice, for a vendor or a contractor. After their address, the page asks for their invoice: its number (one line, no link), the amount in USDC, the due date, and optionally a note of plain text and the invoice as a PDF or text file of up to 4 MB. Only the file's text and its SHA-256 are kept, never the file, and no model reads it. A payee who already has an address of their own on file can keep it and go straight to the invoice, recorded as
- An invoice that comes in through a link waits on Bills, under Waiting for review, as "Invoice from payee", where its card says the payee "sent it through their payee link". Their note is shown beside it, in their own words, and is not copied into the bill, which starts from the invoice number. Choose Review and add as bill to add it as you would a captured draft: the duplicate check runs, and the bill counts as entered by you, so you cannot approve it alone. Once added, the agent decides it like any other bill. Or choose Discard. Nothing is paid because an invoice arrived. The owners and admins, who add bills, get one email when it arrives, and the ledger records it as
payee_invoice_submitted. - The link works once and expires after 7 days. A new link replaces the payee's unused one, and Revoke in the row stops it. Once the payee has sent their address, a link still waiting for their invoice shows "Waiting for their invoice" in the row: Revoke stops it taking one, and so does a new link for that payee. The payee still sees their payment's status on it.
- At its foot, as on every page Vestiarion sends your counterparties, a line says it was sent with Vestiarion and links to Vestiarion's site, tagged with the kind of page only, never your business or theirs.
- An address that comes in through a link counts as a change, like any other: the row says "not yet confirmed", and the agent holds payments to that payee until someone here confirms it, as below. The row names the chain beside the address, and Confirm address confirms the two together.
- Whoever creates the link counts as having given the address that comes through it, as if they had typed it in. A link made with an API key counts as made by the member who issued the key. So the first payment to that payee at that address needs a second person: when someone else confirms the address, the agent pays it on its own; when the person who created the link confirms it themselves, the agent holds that first payment as
counterparty.new_payee, and another owner, admin or approver pays it (see Approve a held payment). Who created the link is read from its signedpayee_link_createdentry, so it holds even after that person's account is deleted; if no one can be named, a person approves the first payment. The ledger still records the address as the payee's own. - Send the link yourself; the person who confirms the address should not be the one who handled the link.
- A bill can come before the address. Wherever payments are real, the agent holds a bill to a payee with no address before it tries any transfer (
counterparty.no_address), and its card says to add the address or ask for it. "The agent decides it again on its own once the counterparty has an address and a person has confirmed it."
Ask every payee at once
When several payees have no address of their own, Ask every payee for an address, above the Counterparty book, asks them all at once. It counts vendors and contractors with no address, and those paid at a mirror address in shadow mode. It leaves out a payee that already has a link out, and says how many do. Owners and admins choose Ask N for an address:
- The dialog lists each payee and how its link goes: By email to its notice email, or No email: copy its link. Nothing is sent until Send the links.
- Each payee gets its own link, made exactly as Create link makes one, and the email says which business asks, the network it pays on, and that nothing is paid to the address until someone here confirms it. In shadow mode, where your business still pays its suppliers its own way, it says you are getting ready to pay in USDC.
- The links that were not emailed are shown once, each with Copy link, to send yourself. A link that could not be made is named under Not made: ask that payee from its row.
- At most 25 payees are asked at a press, by name; the panel says how many remain.
- A workspace sends at most 100 of these emails in 24 hours; past that, the links are shown to copy. A sandbox, whose payments are simulated, emails no payee: every link is shown to copy.
- Every rule above holds for each link: the address waits for a person to confirm it, and whoever pressed counts as having given it. The ledger records each link as
payee_link_created, and the press aspayee_addresses_requested: who pressed, each link with whether it was emailed, and each payee whose link could not be made.
Changing an address
Owners and admins change a counterparty's address with Edit address in its row: enter the new Arc address, or leave it empty to clear it, and choose Save address.
Changing where a counterparty is paid is how payments get redirected to the wrong wallet. So after a change, the row reads Confirm address and says "not yet confirmed", and the agent holds every payment to that counterparty, whatever the amount, until a person confirms the new address. There are two ways to confirm it:
- Approve and pay on a held payment to it. The approval card shows where the money goes, after "Pays to". If the address changed after the page loaded, the approval is refused with "This counterparty's address changed after this page loaded. Check the new address and try again." With the payee lock on, approving no longer confirms the address.
- Confirm address in the counterparty's row. Owners, admins and approvers see it, and accountants while an owner lets them co-sign (see Two approvals above a figure). It asks how you checked the address, as Payee lock describes. The row and the confirmation name the chain the address is on, and a chain that changed after the page loaded is refused like a changed address. A payment the agent held for the change goes back to it, and it decides that payment again, with every check, in the cycle the confirmation starts.
Before you confirm an address, check it with the counterparty through a different channel from the one the change came through. The ledger records who changed the address, from what to what, and who confirmed it. A contractor's verified milestone waits the same way: it stays verified, and the first cycle after someone confirms the address decides it.
Payee lock
The payee lock turns confirming a changed address into a recorded check by a second person. On Arc testnet it is off until an owner turns it on in Settings, under Payee lock, with Turn on the payee lock. A workspace created on Arc mainnet starts with it on, with no wait.
Confirm address always asks How did you check it?:
- Called them on a number we had before;
- Messaged them on a channel we used before;
- In person;
- Another way.
It also asks for the Contact used and a Note, and whether This contact was on file before the new address arrived. With the lock off the answers are optional, and whatever you give is signed with the confirmation.
With the lock on:
- Confirm address needs that record. A call or a message names its contact, and ticks that the contact was on file before the new address arrived. A number or a channel that came with the change is the one a fraudster controls.
- Someone else confirms it. Whoever entered the address, or asked the payee for it, cannot confirm it while another member can: "You entered or asked for this address, so someone else confirms it." Where no one else can, they confirm it alone, and the record says so.
- Approve and pay no longer confirms an address. It is refused until someone confirms the address on Counterparties.
- Wait after an address changes keeps a changed address from being paid for 4, 24, 48 or 72 hours after the change, confirmed or not, which gives the real payee time to notice a change they did not make.
- The agent holds a payment to that address until then, and decides it again within about five minutes of the wait ending. Turning the lock off, or choosing a shorter wait, decides it again at once. That includes a payment whose first send never reached Circle and that the wait kept from being sent again, except a payout to another chain, which waits for a person since Circle may still hold its first send.
- Approve and pay and Pay now say when it can be paid.
- A verified milestone waits too. Its card on Contractors reads "Payee lock wait" and says until when.
Here is the lock at work in the team's own workspace, live on Arc testnet, on Oct 20, 2026, with the lock on and a 4-hour wait. A vendor's payment address changed to a new wallet that held 0 USDC. The agent decided to pay the vendor's 3.00 USDC bill, and code held it as counterparty.address_unconfirmed. The member who had entered the address was refused when they tried to confirm it, and a second member confirmed it with a record of how they checked it. The agent decided to pay again, and code held it for the wait as counterparty.cooling_off. Once the wait was over, the agent paid: 0x49787501…0551, 3 USDC to the confirmed address, confirmed on chain in block 68200055 at 15:16:04 UTC and recorded in the ledger at 15:16:07 UTC.
The lock is held by Vestiarion's code and by people, not by a contract. What the transaction shows is what followed: the payment settled only after both holds ended, to the confirmed address, for the bill's amount. The landing page's safety section shows the same case step by step.
Whether the lock is on or off, a counterparty's row warns about an address that is the same as another counterparty's, or that looks like it:
- "Same address as" the other counterparty;
- "Looks like" the other counterparty's address, when the two share their first 6 and last 4 characters after
0x. That is the pattern address poisoning uses.
When a changed address looks like an address the same payee had or was paid at before, but is a different one, the row and Confirm address say so too: "Looks like an earlier address of this payee". A real new wallet almost never shares both ends with the old one; an address made to look like it does.
Confirm address repeats the warning before anyone confirms. It never blocks, since two counterparties can share a wallet on purpose.
To check an address before it is in Vestiarion, use the free address lookalike checker. It compares it with addresses you paste, with a broader rule than this warning, and checks its characters, its checksum and OFAC's list, all in your browser.
To check a whole batch payout before you send it, such as a Safe CSV Airdrop file or a Disperse list, use the free payout batch check. It runs the same checks on every address, compares each with every other in the batch and with the addresses you have paid before, and reads the amounts and tokens, all in your browser.
When an invoice or an email says a vendor has new bank details or a new wallet, use the free invoice details check. It puts the details you have on file beside the invoice's, finds a sender's domain or a wallet made to look like the vendor's and an IBAN or routing number that cannot be right, reads the message for the words such requests use, and writes the call to make to the number on file, all in your browser.
Any member can open the payee lock's evidence pack from Settings, under Payee lock, with Open the evidence pack. It opens on the last 30 days; choose this year, all time, or any days. Each address change shows:
- who entered it;
- how it was checked, and whether by a second person;
- the payments the agent held for its address;
- its first payment;
- the signed ledger entries each fact rests on.
The page counts them, and under What insurers ask, and what these records show answers, from the period's records, the questions an insurer's questionnaire on payment-change fraud asks: a call-back to a contact held before the change, a second person, a record of the check, a hold until it is confirmed, a wait, lookalike addresses, and records someone outside can check. Each insurer words its own questions, so the page puts them in its own words. The answers count the records of those changes, not how the payee lock is set today, and are not a completed questionnaire.
To share it:
- Print or save as PDF prints the page without the workspace's menus; choose Save as PDF in the print dialog.
- Download CSV gives one row per address change, for a spreadsheet.
- Download signed JSON, or Download the evidence pack in Settings, gives the JSON file. It carries every entry the pack cites, in full, so it can be checked offline like the audit export.
Share the evidence pack and receipts goes through the pack step by step: each fact on a change, what each answer counts, the CSV's columns, and checking the JSON offline.
The payee lock covers addresses on Arc and the chains it pays. A payout to a vendor's bank account already waits for a person every time, so the lock adds nothing there.
The ledger records each change to the lock as payee_lock_changed, and the check behind each confirmation in its counterparty_address_confirmed entry.
Was this you?
When a payee's address changes to a new one, Vestiarion emails the payee's billing email on file and asks: "Did you change where" your business "pays you?" The email shows the address before, shortened, and the new address in full. It also says when the address changed and how:
- by someone in your workspace;
- through the payee's own link;
- on GitHub.
Its link opens a page with Yes, I made this change and No, this wasn't me. It takes one answer, works for 7 days and needs no account. Opening the page changes nothing: only a button does.
- Yes shows on the payee's row on Counterparties: "Their contact on file said they made this change." It confirms nothing: someone still confirms the address.
- No, this wasn't me freezes the payee, while that address is still the one on file:
- its address is no longer confirmed, so the agent holds every payment to it, as for any address no one has confirmed;
- no one can confirm it, and no approval pays it, to its address or its bank account: Approve and pay and Pay now are refused, with "is frozen: their contact on file said they did not make the change to its address";
- the owners and admins get an email, whose button opens the address on the payee's page;
- the payee's row, their page and its approval card say it is frozen.
- To unfreeze, an owner or admin checks with the payee by a contact you had before, then chooses Unfreeze on its row and says how they checked. Whoever made the disputed change cannot, while another owner or admin can. The address still needs confirming afterwards, under the payee lock's rules when it is on. To put the old address back, edit it as usual: the billing email is asked again, and the payee stays frozen until someone unfreezes it.
Nothing is asked for a payee's first address, a cleared address, a payee with no billing email, a sandbox or a workspace in shadow mode. Clearing an address and then setting a new one still asks, about the address it had before. A newer change asks again, and the older link stops working. The email goes to the billing email on file when the address changes: check the billing email itself too, if it changed recently.
The ledger records address_change_check_sent, address_change_answered, counterparty_frozen and counterparty_unfrozen.
Anyone who may not add records sees "Only an owner or admin of this workspace can add counterparties." instead of the form.
2.Add an invoice
Open Bills & receivables, choose New, then Bill to pay. New also offers From a document, to have the model read it from a PDF or an email (see Read an invoice from a document), and Import a list, to add many from a spreadsheet, in its own columns, dates and currency (see Import your bill list).
- Direction: Payable, for an invoice you pay. Choosing a counterparty sets it: Receivable for a client, which pays you, and Payable for anyone else; the line under it says which it is. A payable to a client is never paid by the agent: it waits for a person, who pays it in Approvals if it is a refund.
- Counterparty: the one you just added. With none yet, the form says "Add a counterparty first — every invoice is against one." and links to Add counterparty.
- Amount: within the counterparty's payment limit. The agent does not pay an invoice over the limit; it holds it for you.
- Currency: USDC, or EURC for a vendor that bills in euros. See Invoices in EURC.
- Due date.
- Early-payment discount (%) and Discount deadline, if the vendor offers one. See When the agent pays.
- Late fee, if the vendor charges one for paying late: its value, whether the Late fee is "% a month" or "A fixed amount", and Starting on, the first day it applies. Left blank, it starts the day after the due date. See A late fee.
- Memo, if you like.
- Invoice number, the vendor's own number for the bill, if you like. It is recorded with the bill, and its receipt states it. An invoice read from a document fills it in.
- PO reference, and tick Goods or services received. Without confirmed receipt, or without a purchase order from a counterparty that needs one, the three-way match is incomplete, and the agent asks for more information instead of paying. Every counterparty needs a purchase order until it is marked as paid without them: see Pay a counterparty without purchase orders.
Choose Add invoice. The page confirms with "Invoice added for Name. The agent usually decides on it within a minute." As the form says, "The agent usually decides on a payable within a minute of adding it."
Read an invoice from a document
Instead of typing an invoice in, choose New, then From a document. Choose a PDF or an email, or paste the invoice's text under Or paste the invoice's text, then choose Read invoice. The workspace's model reads the vendor, the amount, the currency, the due date, the purchase order, any early-payment discount, any late fee and the address the invoice asks to be paid to. It fills in the invoice form below with them. Nothing is added until you check the form and choose Add invoice.
What the model read is checked before you see it:
- An amount, purchase order or address that the document does not contain is left blank: "The amount the model gave is not in the document, so it was left blank."
- An amount written with a decimal comma, as much of Europe and Vietnam write money, is read as such: 3,50 is 3.50 and 1.200,00 is 1200.00. A comma before three digits is a thousands separator, so 1,250 is 1250.
- A due date read from a date written in numbers whose day and month could swap gets a note naming both days, the one taken first: "The due date, 3 November 2026, was read from 03/11/2026, which can also mean 11 March 2026. Check it against the invoice."
- When you type over the amount that was read, the form names what was read: "The invoice was read as 12.50: check this amount before you add it."
- The counterparty is matched by its address on file, or else by its name. When none matches, the form says so, naming the vendor it read, such as "Northstar Studio is not one of your counterparties yet.", and Add a counterparty opens Add counterparty. Add it, then read the invoice again, or choose another counterparty.
- When the invoice asks to be paid to another address than the one on file, the form warns you. The agent pays the address on file; a document never changes it.
- Once the invoice is added, the address it asked for stays with it. If it is not the address on file, the agent holds the payment for a person, with both addresses in its reason: a changed payment detail on an invoice is how payment redirection usually arrives. Check with the vendor, by a contact you had before, which address is theirs. Approve and pay pays the address on file, and its card shows the address the invoice asked for. To pay the invoice's address instead, change the counterparty's address to it: the change goes through Confirm address and, where it is on, the payee lock, and the agent decides the payment again once the two match. Such a payment is approved in Approvals, never from Slack. This holds for invoices added from a document, by email, from a Google Drive folder, from Telegram or Slack, and from the Chrome extension.
- Goods or services received is never ticked for you: "A document cannot say this; tick it only if you received them."
- An early-payment discount whose percent the document states is filled in even when its deadline cannot be used, and the form then asks you for the deadline: "The discount deadline was left blank: the invoice does not give one that could be read. Enter the last day the discount applies, or clear the discount."
- A late fee is filled in only when the document states it: a percent a month written as a percent, such as "1.5% per month on overdue balances", or a fixed amount the invoice contains, such as "a late fee of 25 USDC". Otherwise it is left out, and the form says why: "The late fee was left out: the document does not state that percent." A percent above 10 a month is left out for you to check, and so is a fixed amount above the invoice's amount, or one the invoice writes only as a percent, such as "a late fee of 2%". Its start is the day the invoice gives, on or after the due date; otherwise Starting on is left blank, so the fee starts the day after the due date you add the invoice with, even one you corrected. A late fee you change from what was read is recorded among the fields you changed.
A PDF is read from its text, and an email (an .eml file) from its own text and the first three PDFs attached to it; when it has more, the form says "PDFs attached to the email after the first three were not read." When it has more and neither the email nor those three PDFs has text, as when a scanner sends three scans before the invoice, nothing is read: "There is no text to read in the email or the first three PDFs attached to it, and the PDFs after those were not read. Choose the invoice's PDF on its own, or paste its text." A scanned PDF has no text: "This PDF has no text to read; it may be a scan. Paste the invoice's text instead." A file can be up to 4 MB, and a workspace can read five a minute. A PDF built to expand to more than 16 MB once decompressed is not read: "This PDF could not be read. Paste the invoice's text instead." A PDF whose contents Vestiarion cannot measure before opening it, such as an encrypted one or one compressed with LZW, is read on its own, apart from the rest of Vestiarion's work, and one of more than 50 pages, or that takes longer than 15 seconds to read, is not read either. If it ran out of time while other PDFs were being read, the form says "The invoice could not be read. Try again in a moment." The document itself is not kept. The invoice's ledger entry records the document's SHA-256 hash, which model read it, which fields you changed, and the address the document asked to be paid to.
Invoices in EURC
A vendor that bills in euros can be paid in EURC, Circle's euro stablecoin, on Arc testnet. Choose EURC under Currency on the invoice form, or write EURC in the currency column of a list you import. As the form says, "A EURC payable is paid in EURC, and checked against the payment limit at its USDC value."
The rate and the swap below come from Circle's Stablecoin Service, which Vestiarion uses on Arc testnet only. On Arc mainnet a EURC payable has no rate, so the agent never pays it on its own: it is held for a person, as under No rate, no payment below.
- The rate. Payment limits stay in USDC. Before it decides a EURC payable, the agent asks Circle's Stablecoin Service what the amount is worth in USDC on Arc testnet, and checks that value against the limit. The decision's ledger entry records the rate and when it was quoted. It is the testnet market's rate, not a reference exchange rate.
- No rate, no payment. When the quote does not answer, the payable is held for a person, and its card shows USDC value "no rate". If the model had decided to pay it anyway, the card's "Blocked by code, not by the model" band names the rule: no exchange rate could be read. You can still approve it on Approvals.
- Decided again when the rate comes back. Arc testnet's route comes and goes. Every 5 minutes, Vestiarion asks Circle again for each EURC payable held for want of a rate, of a swap, of a swap within its cost cap, or of a value within the limit. Once a quote clears what held it, the agent takes it up again within a minute and decides it with every check, with no one pressing anything.
- On the payable. Under How the agent decided, the reopen step names what came back, for example "A EURC rate is quoted again: 0.5 EURC is worth 0.607631 USDC at 1.215262 USDC per EURC, where there was none at the decision".
- In the activity line. For example "Paid Loto 0.50 EURC · decided again once a EURC rate was quoted".
- In the ledger. The reopen and the decision after it record the rate before and after, and the decision they follow.
- Not a loop. A route that comes and goes reopens a payable at most once in 30 minutes. Return to agent on Approvals still works at any time.
- Paid from EURC. A EURC payable is paid in EURC from the operating wallet; USDC is never sent in its place.
- When the wallet's EURC is short: the agent can buy the EURC with USDC first (next point). Otherwise the payable is held. If the model had decided to pay it anyway, the band names the rule: the wallet held too little EURC.
- Testnet EURC: get it at faucet.circle.com for the operating wallet's address, the same way as USDC.
- How much EURC the wallet holds: the Balance on-chain tile on Console shows it under the USDC, read from Arc testnet each time the tile refreshes.
- Paid from USDC by a swap. In a live workspace, when a EURC payment is due now and the wallet's EURC is short of it, the agent is offered a swap of USDC for the EURC it needs.
- Where. The swap goes through Circle's Stablecoin Service, the swap service behind App Kit, on Arc testnet.
- How much. It is sized so that its minimum covers what is missing. EURC above that stays in the wallet.
- Who decides. The model decides whether to pay with it, weighing what it costs.
- What code refuses. A swap that costs more than 3% above the quoted rate (
fx.swap_cost_above_cap), or that would leave the USDC below what falls due in USDC within 7 days (fx.swap_usdc_short). - How it runs. From the operating wallet, before the EURC transfer. It is recorded as its own
fx_swapledger entry, with its rate and its transaction on Arc testnet. The card shows Funded by swap, linked to that transaction. - When it runs. A payable not due yet is scheduled, and the swap is made on its day. A swap still in flight at Circle is finished by the next cycle before the payable is decided again. A sandbox never swaps.
- Repeats. A EURC bill sent again in EURC is refused like any repeat. A purchase order billed once in USDC and again in EURC is shown to the agent as a re-bill to confirm.
- Totals stay USDC. Paid out to date, the treasury buffer and the forecast count USDC only.
Pay a payee on another chain
On Arc testnet, a vendor who wants USDC on Base, Arbitrum or Ethereum Sepolia is still paid from the operating wallet on Arc testnet. As the form says, "Another chain is paid from Arc through CCTP, for a fee." Choose the vendor's chain under Chain, and give their address on that chain under Payment address. Only a vendor can be paid on another chain: a contractor's milestones are released on Arc testnet. A payee link sent to such a vendor asks for their address on that chain.
- How it is paid. The agent burns the USDC on Arc through Circle's Cross-Chain Transfer Protocol (CCTP), and Circle's Forwarding Service mints it to the payee on their chain. The payee is minted the invoice amount, and the fee comes on top of it, from the operating wallet.
- The fee. Before it decides, the agent asks Circle what the transfer costs, and weighs it. The fee depends on the chain: on 2026-10-01 it was about 0.05 USDC to Base Sepolia, 0.13 to Arbitrum Sepolia and 1.85 to Ethereum Sepolia. A payout whose fee is above 10% of the invoice is held for a person, and so is one Circle gave no fee for.
- From a Gateway balance. A live workspace can also hold a balance in Circle Gateway, which pays out on another chain at once.
- On Treasury, an owner or admin opens Manage under Gateway balance, enters an amount in Amount to move from the operating wallet (USDC), and chooses Fund Gateway. The first funding creates the workspace's Gateway signer, a Circle wallet that signs Gateway's transfers; Circle holds its key. USDC moved into Gateway stays there until it is paid out.
- For each payout to another chain, the agent asks both Gateway and CCTP what it costs. It pays from the Gateway balance when that balance covers the payout and Gateway's fee is no higher than CCTP's; otherwise it pays through CCTP.
- The card names the route the payout took, under Payee's chain, with its fee against the other route's, and links the mint on the payee's chain. Once a payout has started on a route, every later attempt uses that route.
- USDC only. An invoice in EURC to a payee on another chain is held: only USDC crosses chains.
- In flight, then paid. The invoice reads "Payment in flight" from the burn on Arc until the mint lands, usually within half a minute. Its card then reads "Settled on chain", naming the chain the money landed on, such as "Settled on Base Sepolia", and links both: the burn on the Arc testnet explorer, and the mint on the payee's chain. A payment still not minted two hours after it was sent is held for a person.
- Approving one. On Approvals, the card names the payee's chain. Approve and pay takes the route the agent would: Gateway when the Gateway balance covers the payout and Gateway costs no more, CCTP otherwise. A payout an earlier attempt started keeps its route. The confirmation names the route and its fee, for example "The Gateway fee, about 0.163 USDC, comes on top, from the Gateway balance." A CCTP payout needs the operating wallet to hold the amount and the fee; a Gateway payout needs the Gateway balance to.
Pay a vendor on Base or Arbitrum from Arc mainnet
A workspace on Arc mainnet pays a vendor on Base or Arbitrum the same way, in real USDC: the operating wallet burns it on Arc through CCTP, Circle mints it to the vendor's address on their chain, and the fee comes on top of the invoice. Circle quoted about 0.054 USDC to Base on 2026-10-19 and about 0.077 USDC to Arbitrum on 2026-10-22, so a bill under about 0.54 USDC to Base, or about 0.77 USDC to Arbitrum, is held for a person under the 10% fee cap. The payment counts as paid once the USDC is minted on the vendor's chain, and its receipt checks that transfer there.
- From your own wallet, through version 2 of its contract. A workspace that pays from your own wallet sends a payout to Base through its spending limit contract, from the agent's wallet: the contract's
payAcrossChainstakes the amount and the CCTP fee from your wallet, counts both against the daily and 7-day figures, and burns them with the forwarding hook, so the agent's wallet never holds your USDC. Before the agent decides, it asks the contract whether it would pay, with the fee just read; a payout past a figure is held for a person with the contract's figures. Approve and pay asks the same, and refuses one past a figure by name, for example "Paying 30.054 USDC with its CCTP fee would pass the contract's daily limit of 50 USDC: 40 USDC paid so far." The contract also refuses a fee above 10% of the payout or above 2 USDC, and any chain it was not deployed for: Base and Arbitrum for a contract deployed since Oct 22, 2026, Base only for one deployed before. Vestiarion reads which chains your contract pays from the contract itself, offers a vendor only those, and Approve and pay refuses another by name: "Your wallet's contract was deployed before it could pay Arbitrum, so it refuses this payout; nothing was paid. Pay this vendor on a chain it pays, or from your own Circle account." A contract deployed before Oct 19, 2026 is version 1, which pays on Arc only: the agent holds such a bill for a person, and Approve and pay refuses it, "Only USDC on Arc mainnet can be paid from your wallet's contract." Upgrade it to version 2 in Go live. On Arc mainnet the field says: "Another chain is paid from Arc through CCTP, for a fee; from your own wallet, version 2 of its contract pays it". - Base and Arbitrum, USDC only. Ethereum and the other chains are not offered on Arc mainnet yet, and EURC is paid on Arc mainnet only.
- A new address, confirmed by a person. A vendor's address on Base or Arbitrum is entered on Arc mainnet and waits for a person's confirmation like any new address. The vendor can also give it themselves: create its payee link with Let them choose where they are paid ticked (see Ask a payee for their address), and they choose Base or Arbitrum before giving their address. Their row then names that chain beside the address until someone confirms it. A workspace started as a live slice does not carry an address on another chain over from shadow mode: a vendor paid on Base Sepolia there goes over as a vendor on Base, and one on Arbitrum Sepolia as a vendor on Arbitrum, with no address, for you to ask for it.
- Bills, not milestones. A milestone is paid on Arc mainnet only, so a vendor on Base or Arbitrum is not offered for one; pay its work as a bill.
3.Run a cycle
A cycle is one run of the agent: it screens counterparties, reads open invoices, and pays, schedules, holds or flags each one. Adding a payable starts a cycle, usually within a minute, so the invoice is decided without anyone pressing a button, and the pages show the decision on their own. The agent also starts one when a person returns a payable to it, confirms a changed address, verifies a milestone, or resumes it. One cycle runs at a time: if one is already running, the next waits for it, and Run cycle now says so instead of starting a second. A live workspace also runs a cycle every 6 hours on its own, for what time alone changes, such as due dates and screening. Two things time changes start one sooner: the end of a payee lock wait that holds a payment back, within about five minutes, and a scheduled cycle the workspace missed, within about 20 minutes of the time it was due.
To run one yourself, open Treasury, the console, and choose Run cycle now. Only owners and admins have this button. When the cycle ends, a message says "Cycle complete at time · n decisions logged." and the console shows a report of what the cycle did.
Watch the agent work
The header at the top of every workspace page says when the last cycle ran. While a cycle runs, it reads "The agent is working · n s" instead, counting the seconds, and on Bills & receivables each payable not yet decided reads Deciding now.
When the agent has decided, a message says what it did, one per decision, how long after your action, who decided and what was checked. For example:
- "Paid Jiren 0.30 USDC · 28 s after details were added; Circle confirmed it on Arc testnet.", then "DeepSeek decided, as the written policy would. Checks passed: purchase order and goods, the 30.00 USDC limit, screening, the spending-limit contract." Under it, How it decided opens the payable's steps on Bills & receivables, and View the transaction opens its transaction on the explorer.
- "Code stopped paying Centronex 0.35 USDC · 19 s after it was added.", then "DeepSeek decided to pay it; code stopped it: the agent's spending limit has no room today, and the agent pays it once there is." Under it, Decide in Approvals.
A payment is called paid only once Circle confirms it. Until then the message says it was submitted, such as "Submitted 0.30 USDC to Jiren; waiting for Circle to confirm it on Arc testnet."; if Circle never answered the send, it says the outcome is unknown, and nothing goes out again until Circle answers. A sandbox's payment says "in the sandbox (simulated)".
When a cycle decides more than two things, one message says "The agent made n decisions." and See them opens the console's report of that cycle. Either way the page shows what changed at once, without a reload.
A page tells what happens while it is open: a cycle started by your own action, by another member's, or by the 6-hourly schedule. It watches closely for a minute and a half after you add or change something, and less often otherwise.
4.Read the decision and its reasoning
On Bills & receivables, the figures at the top count what needs you, what is due in 7 days, what is overdue, and what customers still owe you; each opens the list behind it. When something waits for review, such as bills an accounting tool or email brought in, Waiting for review says so under them. The Bills tab lists your bills, 25 to a page, with the search and an order: Needs you (held, or refused by code), Upcoming (not yet paid, with the day it pays or falls due), Scheduled, Paid and closed, All and Recurring, each with how many it holds. A row says who and what, the date that matters, the amount and the agent's decision in a few words. A row that needs you also says what stands in its way, such as "No PO · Not received", and its next action, such as "Add the purchase order" or "Decide in Approvals". When no check names the reason, it says why it waits: the rule, when code stopped it, such as "Code stopped it: the payout fee is above 10% of the invoice.", or else the first sentence of the agent's reasoning. In shadow mode, a payment that passed every check and waits for your verdict says "Shadow mode: it waits for a person to agree." The name of a row opens its decision as a card, in a panel beside the list (the whole screen on a phone); the panel's address can be shared, and Back closes it. The console's Stopped section also shows the latest decisions the agent stopped. A card shows:
- the outcome: "Settled on Arc", "Scheduled for date", "Held for you" or "Refused by guardrail";
- the amount and the counterparty;
- Agent’s reasoning: why it decided as it did, citing the facts it used, such as the amount, the PO reference, the risk level and the balance;
- the evidence it checked, the ledger entry (
audit #and its number), and, for a payment, the transaction hash; - Why it was paid once it is paid, or Evidence so far before: the payment's whole chain of evidence, from the purchase order to the receipt, each fact marked with how it is known. See Why a payment was paid.
When the model decided to pay but a guardrail stopped it, the card also has a "Blocked by code, not by the model" band. The band names the rule in words, such as that the purchase order or goods receipt was missing, and the amount attempted. Hold the pointer over it for the rule's id, such as invoice.match_incomplete, as the ledger and the API name it. For a limit, it adds the amount allowed; for a rule about something other than the amount, it says why, such as "the first payment to this address, and only one person stands behind it".
At the foot of a payable's card, How the agent decided opens its steps, oldest first, each a signed entry in the ledger: who added it, what a person changed, each decision with who decided and whether the written policy agreed, what it checked (the purchase order and goods, screening, the amount against the limit, duplicates), what code refused, what the spending-limit contract on Arc said, and the transaction that reached Arc. Each step shows its time to the second, how long after the step before it, and the number of its entry in the audit log. Its last line, The whole chain, from purchase order to receipt, opens the payment's evidence.
A payable the agent stopped also says what you can do about it, on the console's Stopped section as on Bills & receivables. Under the card, a line names the cause and the way through, for example "It is above CME's payment limit. Pay it in Approvals, or raise the limit." Decide in Approvals opens Approvals at that payable's card. Owners and admins also get the page that removes the cause:
- Edit limit or Confirm address opens that part of the counterparty's page: its limit, or its address;
- Purchase orders opens their purchase orders on the same page, when code refused a payable for a missing purchase order, for a counterparty that is in fact paid without them;
- Review screening opens their screening, for a counterparty screened high risk, where a wrong match is marked Not this person;
- Spending limit opens the agent's spending limit on Treasury, when it had no room for the payment;
- USYC reserve opens the reserve in Settings, when the operating wallet did not hold the cash a payment needs and the reserve could not cover it: bring cash back there, or add USDC to the operating wallet, and the agent decides the payment again on its own;
- Treasury, when the operating wallet is short of EURC or the Gateway balance of a payout.
A stop only a decision resolves, such as a payout fee above 10% of the invoice or a possible duplicate, says so and offers Decide in Approvals. A payable to a client is one: the agent never pays a client on its own, so the card says to pay it in Approvals if it is a refund, or to reject it and add it as a receivable. A payable missing its purchase order or goods receipt offers Add details (see "Add what the agent was missing" below).
5.When the agent pays
An invoice does not have to be paid the moment it is decided. At intake, a payable can carry an early-payment discount: Early-payment discount (%) and Discount deadline, alongside its other fields. On a cycle, the agent chooses not only whether to pay an invoice but when, within a bound code enforces: never later than the invoice's due date.
A discount needs its deadline. Once you enter a percent, Discount deadline is no longer optional. As the form says, "Needed with a discount: the last day it applies, on or before the due date." An invoice with a percent and no deadline is not added, and the form says under the field: "Enter the last day the discount applies, on or before the due date, or clear the discount." An imported row's discount and discount deadline columns follow the same rule: both, or neither.
- With an early-payment discount still available, it schedules the payment for the discount's last day, and pays the discounted amount then.
- Otherwise, it schedules the payment for the due date, holding the cash until it is owed.
- A payable due today, or overdue, is paid at once rather than scheduled.
- Before it decides, the agent brings back from the reserve what today's payments need beyond the operating balance: the payables due today, and the verified milestones waiting to be paid.
- If the cash still cannot cover a payable after the payables that fall due on or before its day, the agent holds it rather than scheduling or paying it. It decides the payable again at the first cycle after cash comes in.
A scheduled invoice's decision card reads "Scheduled for date", with the agent's reasoning for choosing that day. On the day itself, the next cycle checks everything again before anything moves: the counterparty's risk level, its payment limit, whether its address is confirmed, and whether the agent is paused. Pausing the agent stops a scheduled payment exactly as it stops any other.
An invoice with an early-payment discount shows its terms on its card as "pct% off if paid by date", and a late fee beside it. Until the agent has decided a payable, its card reads "Not yet decided", and while its transfer is in flight, "Payment in flight". The console's Scheduled payments section lists what the agent will pay next, soonest first: the date, the counterparty, the amount it will actually transfer — discounted, when the discount will still apply that day — and why.
To see what an invoice's terms come to before it is in Vestiarion, use the free payment terms calculator. It works out the due date and the discount deadline from terms such as 2/10 net 30 or net 30 EOM, what skipping the discount costs as a yearly rate, and the day to pay by this same written policy, with your rate applied to the discounted amount, all in your browser.
A late fee
Many invoices charge for paying late: "1.5% per month on overdue balances", or a flat fee. Give a payable its late fee in the invoice form, as Late fee, with whether the Late fee is "% a month" or "A fixed amount", and Starting on, the first day it applies. As the form says, "As the invoice states it. Shown when you approve; never added to what is paid." A percent a month can be more than 0 and at most 10; a fixed amount, more than 0 and at most the invoice's amount; and it starts on or after the due date: "The late fee cannot start before the due date." An invoice you are owed takes none. In shadow mode, a bill in your own currency takes a late fee as a percent a month only: "A fixed late fee is taken only on a bill in USDC or EURC: give it as a percent a month." When a supplier agrees to more time, the fee's start moves with the due date.
A late fee is never added to a transfer. A bill paid late is paid at its amount, and you settle any fee with the vendor. What the fee changes is what the agent weighs, and what you see:
- The approval card. Its cost box ends with the fee: "Late after date", the day before it starts, and "1.5% a month (1.50 USDC)", what a month of it costs, or the fixed amount. A bank payout's box names it too.
- Its terms. The bill's card on Bills & receivables names the fee beside an early-payment discount.
- Its decide-by day. A late fee never moves the day a bill is to be decided by, nor its priority. Past its due date, a bill with a fee names it beside that day: "Decide by Oct 20, 2026; a late fee of 1.5% a month starts Oct 30, 2026", and "applies since" once it has. Approvals, the bill's row, the accountant console and the escalation emails say so. The escalation email comes once the day has passed, as for any bill, and once more on the eve of the fee, while paying still avoids it: "A late fee starts tomorrow on 1 payment". When the eve comes before the usual email has gone out, as on the first day past the due date, the usual email goes out that day instead, naming the day the fee starts, and no second one follows.
- Short cash. When the cash cannot cover every bill due soon, the written policy pays first, among the bills due or overdue, the one whose late fee costs most in the coming month. See Which bill first when cash is short.
- The agent's reasoning. The agent is told the fee, and names the one a payment avoids, as its written policy does: "before a 1.5% monthly late fee (1.50 USDC) starts Oct 30, 2026".
The payment terms calculator shows what a late fee comes to 7, 30 or 60 days after the due date, or any number of days, charged for each month or part of one, by the day, or as a fixed amount.
Pay something every period
A retainer, a subscription or a monthly fee does not need a new invoice each time. Choose New, then Recurring, and fill in the form:
- Pay: a vendor or contractor.
- For: what it is for.
- Amount each period, in USDC or EURC.
- How often: Every 1 or more days, weeks or months.
- First due date, and a Last due date if it ends (optional).
- A Contract or PO reference if you have one.
Above the button, the form reads the schedule back as you fill it in, for example "Pays Jiren 0.3 USDC every day, from Oct 2, 2026 to Oct 3, 2026: 2 payments.". Check the period and the number of payments there before you go on. Choose Set up recurring payment. The setup is signed in the audit log as recurring_payable_created.
- Each period becomes an invoice as it comes near. At most a week before its due date, a cycle creates it: a daily one on its day, a weekly one 6 days ahead, a monthly one 7 days ahead. The agent then decides it like any other: when to pay, within every guardrail. Each one is signed as
recurring_invoice_createdand appears on the Bills tab, named after the period; the Recurring filter lists the bills the schedules made. - Months are counted from the first due date. A payment due on the 31st falls on the last day of a shorter month and goes back to the 31st after.
- Periods of one schedule are never taken for duplicates of each other. The same retainer billed every week is not refused as a repeat bill. An invoice typed by hand that repeats one of them still is.
- Delivered every period is ticked by default: you confirm the work or service continues, so each period's invoice counts as received. Untick it to confirm each period yourself.
- Stopping. Recurring payments, a folded line under the list on the Bills tab, says how many schedules run and which period falls due next. Open it to list each schedule with its next due date and status. Stop ends it, signed as
recurring_payable_stopped; invoices it already created stay as they are.
Cap what the agent pays on its own
The console's Agent spending limit panel shows what the agent has paid on its own today (UTC) and in the last 7 days. To cap it, an owner or admin chooses Set limit and fills in Per day (USDC), Per 7 days (USDC), or both, then Save limit. A blank figure means no limit, except while an owner lets the agent pay earned vendors on its own: the dialog then says "Leave a figure blank for no limit on it, but keep one while the agent pays earned vendors on its own.", and leaving both blank is refused with "Keep a daily or 7-day figure while the agent pays earned vendors on its own, or have an owner turn that off first, under Earned vendors in Settings." On Arc mainnet a workspace keeps a daily or 7-day figure: it starts at 50 and 150 USDC, and the dialog says "A workspace on Arc mainnet keeps a daily or 7-day limit." Each change is recorded in the audit log as agent_budget_changed.
- Past the limit, a payment waits. A payment or milestone release that would take the agent past either figure is held before anything is sent. Its card's "Blocked by code, not by the model" band names the rule, that it would pass the workspace's spending limit (its id is
workspace.outflow_budget), with the amount attempted and what the limit had left. - A person's approval does not count. A held payable waits in Approvals, and what you approve there is never stopped by the limit, nor counted against it.
- It comes back by itself. When the limit has room again (a new day, a higher figure, or no limit), the agent decides the held payment again. Raising a figure brings it back within a minute, and the audit log records the reopening with "the agent's spending limit has room for it again".
- Schedules are checked on their day. Scheduling a payment does not count against the limit; paying it does.
- Try a figure first. In the same dialog, Try it on past decisions replays the agent's payments of the last 30 or 90 days, in order, under the figures you entered: see Try a limit before you change it.
Enforce the limit on Arc
The limit above is checked in Vestiarion's code. Under its figures, the panel's On Arc part makes the same limit binding on Arc testnet too: the agent's own payments then leave through a contract that refuses anything past it, whatever the agent decided. In a live workspace with a daily or 7-day figure, an owner or admin chooses Enforce on Arc.
Enforce on Arc runs on Arc testnet only. On Arc mainnet, a workspace whose treasury is a wallet you hold pays only through a contract your wallet deploys, within the daily and 7-day figures you set in it, and the panel links that contract: see Path C: your own wallet. A workspace on Arc mainnet with your own Circle account checks the limit in code.
- What it sets up. A contract on Arc testnet that holds the figures, and a wallet of the agent's own that holds no USDC: Circle's Gas Station pays its gas. The operating wallet keeps its money and approves the contract to draw from it. Setting up sends 0.1 USDC from the operating wallet to the deployer for gas, and is signed in the audit log as
spending_limit_enforced. If it is interrupted, the button reads Finish enforcing on Arc and picks up where it stopped. - The agent's payments go through the contract. Each payment the agent makes on its own in USDC on Arc testnet is sent by its own wallet to the contract, which draws the amount from the operating wallet. The contract refuses a payment past the daily figure (the current UTC day) or past the 7-day figure (that day and the six before it), and it pays each invoice or milestone once. The panel shows what the contract counts, Paid through it today and In the last 7 days, with links to the contract and to the agent's wallet on the Arc testnet explorer.
- Vestiarion asks the contract first. Before each payment, it asks the contract whether it would pay, without sending anything. If the contract would refuse, nothing is sent: the payment is held with the rule
workspace.onchain_limit, and its card shows the contract's own figures. The check in code still runs first, so this hold means the two disagreed. Each decision records the contract's answer asonChainLimit. - What the contract cannot carry waits for you. While the limit is enforced on Arc, the agent does not send a payment in EURC, or one to a payee on another chain: it is held with the rule
workspace.onchain_limit_route, and you pay it from Approvals. A milestone locked in escrow is released from the escrow as before; its money left the operating wallet when it was locked. - People's payments do not go through it. Approve and pay and Pay now are transfers from the operating wallet, as before, outside the agent's limit.
- Changing the figures changes the contract first. The new figures are saved once Circle confirms the change on Arc testnet, and
agent_budget_changedrecords its transaction. While the limit is enforced, a figure must stay set. - Turning it off. Turn off on Arc sets the operating wallet's approval to 0, so the contract can draw nothing, and the agent's payments are checked in code only. The contract stays on Arc testnet; Enforce on Arc uses it again. It is signed as
spending_limit_unenforced. - The contract. Its source, its functions and the address it runs at in production are on Contracts on Arc.
- Who holds the keys. The operating wallet, the agent's wallet and the deployer are developer-controlled wallets: Circle signs for them on Vestiarion's behalf. The contract keeps the agent, and the code that pays for it, within the limit. It does not protect against someone who took over Vestiarion's server, who could also sign for the operating wallet.
The agent checks a new payee's history
Before the agent pays an address for the first time, it can buy that address's payment history across Vestiarion. The answer says how many other workspaces here have paid the address, how many payments were confirmed, and when the first and last were made. It names no workspace and no amount. The model weighs it with the payment's other facts: an address no business here has paid deserves a closer look. Code does not act on it.
The agent pays for each answer itself, 0.001 USDC over x402, the HTTP payment standard, settled through Circle Gateway on Arc testnet. Vestiarion is the seller. Today no other x402 seller accepts Arc testnet, so the agent buys only from Vestiarion. Circle Gateway does not run on Arc mainnet, so a workspace there buys no history and has no service budget.
- The service budget. The agent pays from its own small balance, never from the operating wallet. On the console's Service budget panel, an owner or admin opens Manage, enters an amount (at most 1 USDC at a time) and chooses Add to the budget. The operating wallet moves it into Gateway for the workspace's Gateway signer in one transaction. The panel appears once the workspace has funded Gateway, which creates that signer. Each deposit is signed as
service_budget_funded. - When it buys. A payable or milestone must be waiting for a decision, the counterparty's Arc address must be confirmed, and this workspace must never have paid that address. An answer counts for 7 days.
- Code's limits. The agent pays only Vestiarion's own endpoint, only the offer it expects, at most 0.01 USDC a call, at most 0.05 USDC a day, and at most 3 purchases a cycle. It buys nothing while it is paused. A purchase code refuses is not tried again for a day.
- In the audit log. A purchase is
service_purchased, with the price, the authorization's nonce, Gateway's settlement and the answer. A refusal isservice_purchase_refused, with the rule, and a failure isservice_purchase_failed. The decision that follows carries the answer in its observed facts asaddressHistory.
When a payment does not confirm
A payment usually confirms on Arc within seconds of being sent. One that confirms after the agent stopped waiting for it is recorded within seconds too, when the workspace's Circle account sends Vestiarion its notifications and the agent is running: Circle tells Vestiarion, and a cycle starts at once to record it, with the notices the schedule would send. Otherwise the next scheduled cycle records it. If one has not confirmed 15 minutes after it was submitted to Circle, Vestiarion tells the workspace's people, once for each attempt:
- In the console, Slack and Telegram, within minutes, without waiting for a cycle: "Payment of 12.50 USDC to Jiren has not confirmed 18 min after it was submitted to Circle on Arc testnet.", naming the workspace's network, with what Circle says, such as "Circle shows it stuck.", the transaction, and a link: How it decided for a bill, Contractors for a milestone, which opens its own row there.
- By email, to every owner, admin and approver with email notices on: one message listing each payment, such as "A payment of 12.50 USDC to Jiren has not confirmed", each linked to its bill or to the milestone's own row on Contractors.
- In the audit log, as a signed
payment_stuckentry, which every webhook endpoint receives too.
A payment Vestiarion recorded as failed is told too when it may still have moved: a send Circle never answered, or a transfer Circle was asked about and did not answer. Vestiarion sends nothing again while the payment may still settle, and the next cycle checks it again. The invoice's How the agent decided says "Not confirmed 18 minutes after it was submitted; the workspace's people were told.", and each later check says what it found: "still in flight", or that it confirmed. If Circle shows the transfer stuck, check it in Circle's console, or contact Circle support. The watch runs every 5 minutes whether the agent is paused or payments are stopped: a payment already sent can be stuck either way. The email links what to do, and When a payment does not settle is the runbook for each state.
6.Approve a held payment
Approvals lists every payable the agent would not pay on its own, oldest due date first, each marked held, flagged or awaiting information and shown with the agent's reasoning. When the list is empty, it says "Nothing is waiting for a decision."
Owners, admins and approvers decide each one:
- Approve and pay starts the transfer. A dialog asks you to confirm, and Pay now sends it at once. When a transfer for it was already sent, or Circle never answered one, the dialog asks to check that transfer instead, its button reads Check it or Look first, and the notice says it is checking the earlier transfer: nothing new is sent before Circle answers. The ledger records who approved it. While it is sent, a notice in the corner says Payment approved, with the amount and the payee. It then turns into Payment confirmed once Circle confirms the transfer: the amount, who it was paid to, that you approved it, "Confirmed by Circle on" the workspace's network, and View transaction to open it on the explorer. If Circle has not confirmed it yet, the notice says Payment processing instead, with the payment submitted to Circle, and the payment is not called confirmed until it is. In a sandbox, it says Payment simulated.
- Reject marks it not paid. It asks Why reject it?: you can give a reason, which is kept in the ledger.
- Return to agent sends it back to pending, and the agent usually decides it again within a minute. Its confirmation asks Why return it?
- On a payment the agent flagged or held on one of its rules, the confirmation of Approve and pay asks Why pay it anyway?, unless it checks an earlier transfer first, which sends nothing new.
Each of these reasons is optional, one line, and never stops what you are doing. A reason you give is kept with where you gave it and the version of Vestiarion that asked. Owners and admins see the latest ones on Insights, under Why people went against the agent, and Vestiarion's team reads them to improve the agent: Privacy says what is kept and for how long.
With several bills waiting, you can also select them and approve them with one confirmation: see Approve several bills at once.
Under "Pays to", each card waiting for Approve and pay shows what it would cost if you chose it now:
- Invoice: the invoice's amount.
- Early-payment discount: its percent, its deadline and what it takes off, only while it still applies.
- CCTP fee, about or Gateway fee, about: for a payee on another chain, the fee of the route it would take, or "not read just now".
- Leaves the operating wallet, or Leaves the Gateway balance for a Gateway payout: what is paid and the fee, in all.
- What the payee receives, on their chain. For a CCTP payout, "at least" that much: the part of the fee Circle does not charge reaches the payee too.
- Late after a day, for a bill with a late fee: the fee a month of waiting would cost. It is never part of what leaves. See A late fee.
On Arc mainnet, where your wallets pay their own gas, a note adds Arc's network fee, about 0.00319 USDC a transaction, which is not read until the transfer is made. On Arc testnet Circle pays it. The box is not shown for a payment already sent or in flight, or one the agent is paying. A payout to a bank account has a box of its own: see Bank payouts.
Where payments are real, Approve and pay also refuses a payee with no address yet: "This payee has no payment address yet. Add it on Counterparties, or ask them for it with a one-time link."
Approve and pay is disabled in two cases, and the card says why, and what you can do instead:
- You entered this invoice. Beside the disabled button, the card says "You created this invoice". The person who adds an invoice cannot also approve it, so a payment made by hand always has two people behind it: another owner, admin or approver decides it. The card says so, and you can still reject it or return it to the agent. See who can approve opens Members. When a rule stopped the agent, the card also says what happens without anyone approving: for the agent's spending limit, "The agent pays it on its own once its spending limit has room: the next UTC day, or sooner if an owner or admin raises the limit." For a payment held for want of cash, "The agent decides it again on its own once cash comes in: USDC added to the operating wallet, or brought back from the reserve." Owners and admins also get the page that removes the cause, here Spending limit.
- You gave this payee's address. The first payment to this payee at this address needs two people behind it, even if the workspace has paid the same address for someone else. Where payments are real, the agent never makes a first payment that only one person stands behind, and holds it as
counterparty.new_payee. That includes an address one member typed in, or changed and confirmed alone. Whoever gave the address cannot approve that first payment either: beside the disabled button the card says "You gave this payee's address", and another owner, admin or approver pays it.- Already two people. A member's address that a second member confirmed has two parties behind it, so the agent pays it on its own.
- A payee link counts as its creator's. Whoever created the link an address came through counts as having given that address. The agent pays it on its own once someone else confirmed it. Confirmed only by the person who created the link, it waits, and that person cannot approve its first payment: the card says "You asked for this address with a payee link".
- GitHub always takes two members. A GitHub account is tied to no member, and every bounty acts as the person who connected GitHub, whoever typed it. So for an address a contributor sent with
/payto, a confirmation never counts as the second person: the agent holds its first payment, and two different members stand behind it. One confirms the address on Counterparties, and another approves its first payment. Whoever confirmed it cannot approve it: the card says "You confirmed this address". Until someone has confirmed it, no one approves it alone, since approving would confirm it too: the card says "Another member must confirm this address first". The member the bounty acts as, who adds the bounty's milestone, may pay it once someone else confirmed it. A bounty typed by the pull request's own author names no member. - When no one can be named. For an address whose giver no entry names, such as one sent through a payee link whose creator cannot be found, it is the same: one member confirms it, and another approves its first payment.
- Who can act. The card's "Who can act", and the email when a bill passes its decide-by day, leave out whoever cannot approve its first payment. When that leaves no one, the card says nobody can approve it yet. With two approvers, the one who entered a bill is the one to confirm its address, so the other can approve it.
- A payment sent again asks the same. When the outcome of a payment's earlier send was never recorded, the agent first looks the send up at Circle, sending nothing. If Circle took it, it is recorded as paid; if Circle has not listed it yet, the bill waits for the next cycle. Only once Circle has none does the agent send the payment again, to the payee's address as it stands now, so it asks the same question first. If that would still be the first payment to this payee at that address, and two people do not stand behind it, such as an address one member changed and confirmed alone while the payment waited, the agent holds it as
counterparty.new_payeefor a person instead. Its reasoning says "Not sent again: this is the first payment to this address, and only one person stands behind it — another person approves it." Another owner, admin or approver pays it, or the agent decides it again once a second person stands behind the address. A payout to another chain cannot be looked up this way, so it is asked the same question before Circle is asked for it again under the same payment key, and can be held while Circle may hold the transfer; Approve and pay then asks Circle for it under that key, which Circle takes only once. A transfer recorded with its Circle transaction id is only checked, never sent again. - After the first payment, the agent pays this payee at this address on its own, and decides again any other bill to the same payee that it held for this, including one held when it was to be sent again. A payout to another chain held that way waits for a person, since Circle may still hold its first send. A payment counts at the address it was sent to: a held bill a person pays once the payee gave a new address counts as paid at the new address, and the old one stays a first payment.
- Alone in a workspace. The only approver may pay the first payment to an address they gave, asked for with a payee link, or confirmed, or that no one else confirmed, as for an invoice they entered. The agent holds it for them first, and the ledger entry of their approval says they approved it alone; after it, the agent pays that payee at that address on its own.
- Screened high risk. A counterparty screened high risk is never paid, not even by approval. If the screening matched someone else, Review screening opens their screening, on the counterparty's page, where you mark the match Not this person; the agent then decides the invoice again.
If you are the only member of the workspace who can approve payments (the only owner, admin or approver), there is nobody else to approve what you add, so Approve and pay stays enabled on your own invoices and the card says "You entered this invoice. You are the only person in this workspace who can approve payments, so you can approve it yourself, and the ledger records that you did." The confirm dialog adds "It also records that you entered it yourself, as the workspace's only approver." In the audit log, the approval_paid entry ends "(entered and approved by the workspace's only approver)". Every other check still applies: a high-risk counterparty, a changed address and a short balance are still refused. Once a second member can approve payments, the rule applies again, and each of you approves what the other entered.
If a payment attempt fails, the card says "The last payment attempt failed: " and Circle's reason, then "Approving sends a new transfer. Fix what Circle names before approving, such as adding USDC to the operating wallet." Fix the cause first if you need to — for example, fund the operating wallet — then choose Approve and pay again to send it. Vestiarion never sends a second transfer while the first could still settle: a payment still in flight instead says, naming the workspace's network, "The payment is still in flight on Arc testnet. It cannot be rejected or returned until Circle settles it; approving checks it again." Only Reject and Return to agent go away then — Approve and pay stays: for an invoice waiting here, approving is how its in-flight transfer is checked again, and it never sends a second one.
Sometimes Circle does not answer a payment at all, and Circle may still have taken it. Vestiarion then looks for it on Circle before anything else, and the payment stays in flight until it knows. If it waits here meanwhile, the card says "Circle did not answer when this payment was sent, so it may have taken the transfer. Approve and pay, Reject and Return look for it on Circle first: Approve and pay records it if Circle has it, and sends it only once Circle shows none." Until then, each of them sends nothing and says when to try again. Once Circle has listed nothing for 15 minutes after the send, it was never taken: approving sends it then, as a new payment that every check applies to, and Reject or Return to agent closes it.
If every page says "Payments are switched off for every workspace right now.", whoever runs this deployment has stopped all payments. The agent runs no cycle, and Approve and pay says the same, until they turn payments back on. Everything else still reads as usual.
When the operating wallet falls short. A payment leaves from the operating wallet, with a CCTP payout's fee on top. When the wallet holds less, and the USYC reserve holds the rest, Approve and pay brings the difference back from the reserve first, then pays. The reserve runs on Arc testnet only; on Arc mainnet, Approve and pay refuses a payment the operating wallet cannot cover, and sends nothing.
- Before you confirm, the dialog says so, for example "The operating wallet holds 0.184239 USDC, so about 0.215761 USDC comes back from the USYC reserve first." It reads the balances last recorded; the approval reads them again.
- After paying, it says "Paid. 0.215761 USDC came back from the USYC reserve first." The audit log records the move as
cash_brought_back, by you, before theapproval_paidentry. - When the two together fall short, nothing moves, and the card says what each holds.
- If nothing came back from the reserve, nothing is sent. The payable waits in Approvals as it was, and any approval already given still stands. When Arc testnet has not confirmed the redemption yet, it says so, and asking again a minute later finds that same redemption rather than sending a second one.
- A payout to another chain through CCTP brings back a fifth more of the CCTP fee as well, since the fee is read again just before the transfer; what is left of it stays in the operating wallet. One whose fee could not be read is not covered.
Pay now on a held milestone works the same way, except for one whose USDC is being locked in escrow. A Gateway payout is paid from the Gateway balance, which the reserve does not fund.
Approve several bills at once
Back from a few days away, with several bills waiting? Select them on Approvals and approve them with one confirmation. Each bill is still approved as Approve and pay approves it alone: the same checks, its own entry in the ledger and its own receipt. Only the confirmation is shared, and, where the bills can share it, the transaction that pays them.
- Select them. A card you could approve with others has a checkbox beside its payee. Tick from 2 to 20 bills. A bar at the bottom of the screen then says how many are selected and their total, with Clear and Approve and pay followed by the count. With one bill selected it says "Select one more bill to approve them together."; above 20, "Select at most 20 bills to approve together."
- Which bills. A bill in USDC, paid to an address on the workspace's own chain, that you could pay with Approve and pay now, and for which no payment was ever tried. A bank payout, a payout to another chain, a bill in EURC, one someone else is deciding, one a shadow-mode verdict decides, and one with an earlier attempt that failed or that Circle never answered are approved on their own. Vestiarion checks each bill again when you confirm: one that no longer fits is not approved, and its line says why, while the others are still decided. For a bank payout, a payout to another chain, a bill in EURC or one with an earlier attempt, it says "Approve it on its own:" and why.
- One confirmation. It lists each bill, in the page's order, with its payee, the start and end of its address, and its amount, then the Total, for example "Approve and pay 2 bills?". It says "The operating wallet must hold the total: a selection never brings cash back from the reserve." When it holds less, nothing is approved: "These 2 bills come to 31 USDC; the operating wallet holds 5 USDC. Select fewer, or approve them one at a time, which can bring cash back from the reserve." When any bill goes against the agent's hold, it asks Why pay them anyway? once, optional, and keeps the answer for each such bill. Above the figure for two approvals, your approval of a bill may be the first of the two: its row says "First of two approvals: nothing is paid yet." Its button, Pay now (Approve and pay when one of the bills is a first of two approvals, Approve when none pays now), approves them; no key ever pays.
- What it did. One line per bill: Paid with its amount, Submitted while Circle has not confirmed it, Approved when one more approval pays it, or Not paid with the reason. The bills that pay now are sent together. On Arc they go out in one transaction when the operating wallet can send them together, and the result says "Paid 2 bills in one Arc transaction." with View transaction; otherwise each goes out on its own. The selection then clears. If Circle fails that transaction, every bill in it is held with Circle's reason, and approving one again sends it on its own. If Circle's answer is lost, each bill stays submitted and is looked for on Circle, never sent twice.
- In the ledger. Each bill has its own
approval_paidentry, withapprovedTogether, how many bills you chose in that confirmation, andbatch, when its transfer shared a transaction. - Keys. On Approvals,
jandkmove between the cards,xselects or deselects the card in focus,aopens the confirmation, andEscclears the selection. No key does anything while you type in a field, with Ctrl, Cmd or Alt held, or while a dialog is open. The bar names the keys. - Only on Approvals. Slack approves one bill at a time, where an owner lets bills be decided there. Telegram and Discord approve none: their links open the bill on Approvals. Nothing in the API approves a bill, and an accountant co-signs one bill at a time.
Two approvals above a figure
An owner can make larger payments need two people. In Settings, under Two approvals, fill in Payments above (USDC) and choose Save. The section then says, for example, "Payments above 500 USDC need two approvals." Turning it on, or lowering it, needs two people who can approve payments. With fewer, it says "Two approvals need two people who can approve payments. Add an approver on Members first." Each change is signed in the audit log as approval_policy_changed.
- The agent never pays above it. Code holds a payable the agent would pay or schedule above the figure, or a milestone it would release, before anything is sent. The rule is
workspace.two_approvals. A EURC payment counts at its value in USDC. - The first approval sends nothing. A card above the figure says "No one has approved it yet.", and its button reads Approve. Choosing it records your approval, signed as
approval_given(milestone_approval_givenfor a milestone), and says "Approved. One more approval, by another person, pays it." - The second approval pays. Another owner, admin or approver sees who approved it, and Approve and pay. Their approval pays it, and the
approval_paidentry names both approvals. One person cannot give both: the button is disabled, with "You approved it" beside it. - On Contractors, a held milestone above the figure says the same, and Pay now reads Approve until the approval that pays it.
- An approval is of one payment. It holds the amount, the currency and the payee's address. If any of them changes, or the person who gave it can no longer approve payments, it no longer counts. Reject, Return to agent and Close without paying clear it. A transfer that fails needs two approvals again.
- Who gives them. As many of the two approvals as can must come from people who neither entered the payment nor gave a new payee's address. Those two people give the rest only when no one else can approve. In a workspace with one person who can approve, the button is disabled with "Needs a second approver" beside it: nothing above the figure is paid until the figure is raised or someone else can approve.
- Your accountant as the second person. Under the figure, an owner can choose Let accountants co-sign.
- An accountant then sees Co-sign on a bill above the figure. It records one of the two approvals, signed as
approval_givenwithcosign: true, and says "Co-signed. An owner, admin or approver's Approve and pay pays it." - A co-sign never pays, even when another approval stands: the approval that pays is always an owner's, admin's or approver's.
- Co-sign shows only where a co-sign can still help pay. For the usual refusals, such as a bill waiting for a shadow-mode verdict or an address to confirm, the card says why in its place. A few are refused only when it is clicked, such as the first payment to an address the accountant confirmed that no member answers for alone. The accountant's Accountant console lists the bills waiting for their co-sign and the addresses to confirm: see Accountants.
- Accountants count among the people who can approve bills. So a founder alone with their accountant can turn two approvals on, and pay a bill above the figure once the accountant co-signs it.
- Accountants also confirm changed addresses, and a co-signing accountant counts as someone else, so whoever entered an address no longer confirms it alone.
- Turning it off, or changing the person's role, makes their co-signs count for nothing.
- Milestones are not co-signed.
- Each change is signed as
accountant_cosign_changed.
- An accountant then sees Co-sign on a bill above the figure. It records one of the two approvals, signed as
- Raising it or turning it off brings payments held for two approvals back to the agent within a minute. Turn off asks first: "Turn off two approvals?"
- Try a figure first. Try it on past decisions counts the payments the agent made on its own that a lower figure would have put before two people: see Try a limit before you change it.
- On Arc mainnet a workspace starts with two approvals above 100 USDC and keeps a figure: the section offers no Turn off, and says "A workspace on Arc mainnet keeps two approvals above a figure. Raise it to let one person pay more."
- A payment Circle never took is sent again by the agent only when one approval may pay it, or two people's approvals of it paid it. Otherwise it waits in Approvals, or on Contractors, for two people. This covers a figure set or lowered after the first send. Raising the figure does not bring such a payment back: two people approve it, or one returns it to the agent.
- In Slack, a card keeps its buttons after the first approval, with who approved it, so a second person can approve it there.
Add what the agent was missing
The agent pays an invoice on its own only when its three-way match is complete: the goods or services received and, unless its counterparty is paid without them, a purchase order on file. Without them it asks for more information, and the card is marked Awaiting information. If the model chooses to pay or schedule it anyway, code refuses, and the card waits the same way. When you have what it asked for, you do not need to approve the payment yourself: give the agent the facts, and it decides again.
Owners and admins choose Add details on the card. The dialog offers only what the invoice is missing: a PO reference, the Goods or services received box, or both. Fill them in and choose Add details. A message says "Details added. The agent usually decides it again within a minute."
On Bills & receivables, the payable waits under Needs you. Its row says what stands in its way, "No PO" and "Not received", and what to do: "Add the purchase order and goods receipt", "Add the purchase order" or "Confirm the goods were received". A counterparty paid without purchase orders is never asked for one. That next action opens the bill's card: under the agent's reasoning, it asks for what is missing and offers Add details there too, beside Decide in Approvals, which opens Approvals at that payable's card. Once you have added details, the row reads "Details added · the agent decides it again" until it does.
- The agent decides it again. Until it does, the card says what you added, beginning "Since the agent stopped it", and ends "The agent decides it again at its next cycle, usually within a minute." That cycle starts within seconds. The agent sees that the facts changed since its decision, records
invoice_reopenedwith what changed, and decides the invoice again with every check, as it would a new one. It may pay it, schedule it, or hold it again for another reason, such as the payment limit. - Only what is missing. A PO reference already on file, or goods already marked received, cannot be changed here.
- Recorded. The ledger records what you added, and who added it, as
invoice_details_added. A payment made after it is not counted as "Paid on time with no person involved" on www.vestiarion.xyz/open. - When it is offered. Approvers decide payments but do not enter invoices, so they do not see Add details. It is not offered once a payment for the invoice was sent, or while someone else is deciding it.
Ask the vendor for a missing document
The vendor has the missing document, so Vestiarion can ask them for it, through a one-time link that sends it straight to the bill, and check what comes back against it. A person still approves the payment. See Ask a vendor for a missing document.
Tell the payee it was paid
A business usually tells a supplier when it pays them. Give a counterparty a Billing email, when you add it or later on its row on Counterparties, where Billing email shows the address with Add or Edit (owners and admins; empty turns notices off). Someone you pay with Pay a freelancer gets them at the email you gave for the link.
Each time a payment to it is confirmed on Arc, whoever approved it, the agent or a person, Vestiarion emails that address from no-reply@vestiarion.xyz: "Workspace paid you amount", the network, what it pays for (the invoice's memo and purchase order, or the milestone's title), the address it went to, that Circle confirmed the transfer on that network and when, and View the transaction on that network's explorer.
- Real payments only. Only a live workspace sends them: a sandbox's payments are simulated, and it emails no one.
- On Arc. This version sends them for payments made on the workspace's own network, Arc testnet or Arc mainnet; a payee paid on another chain gets none yet.
- Once. Each payment is told once. A notice that cannot be sent is tried again at the next cycle, for three days.
- Recorded. Each notice sent is a
payment_notice_sententry in the audit log, with the address partly hidden.
When the agent suggests a higher limit
When people keep approving one counterparty's payments above its payment limit, the agent notices. It proposes a higher limit, so payments like these stop waiting for a person.
- When. At least two payments approved above the limit in the last 30 days, and none rejected. The counterparty must be screened clear.
- What it proposes. The model decides whether to propose and which limit. Code accepts a limit only between the largest approved payment and twice it; otherwise the proposal is the largest plus 10%, rounded up.
- Where it shows. It appears at the top of Approvals under Suggested by the agent: the new limit, why, and each approval it rests on. The proposal is signed as
policy_proposal_made. - Accept changes the limit exactly as editing it on Counterparties would. Payments held under the old limit are decided again within a minute. It is signed as
policy_proposal_accepted. - Dismiss changes nothing, and is signed as
policy_proposal_dismissed. The agent suggests a limit for that counterparty again only after a new approval above it.
Only owners and admins accept or dismiss, as for any limit change.
7.See it on Arc and in the audit log
On the Arc explorer. On a settled decision card, the transaction hash is a link. It opens the transaction on the Arc testnet explorer, at https://explorer.testnet.arc.io/tx/ followed by the hash, in a new tab. In a workspace on Arc mainnet it opens Arc mainnet's explorer, at https://explorer.arc.io/tx/.
In the audit log. The card's audit # link opens the entry in Audit log. As that page says, "Every decision is appended here, hash-linked to the one before it and signed with Ed25519." Expand an entry to see its hash, the previous entry's hash, its body hash, its signature and the full detail. Verify hash chain checks every signature and every link, and answers "Chain intact" when all of them hold.
To check a signature yourself, see Verifying signatures. To read the ledger from your own code, see List ledger entries and Verify the ledger.
8.Share a receipt
A payee, an accountant or anyone else can check a payment without an account: share its receipt. Share the evidence pack and receipts walks through it step by step, row by row as the payee sees it.
- Sharing it. On Bills & receivables, under Paid and closed, open a paid bill: one with a transaction on chain shows Share receipt to an owner or admin. It makes a link to a public page. Copy the link then: it is shown only once. At its foot, as on every page Vestiarion sends your counterparties, a line says it was sent with Vestiarion and links to Vestiarion's site, tagged with the kind of page only, never your business or theirs.
- What the page shows. The amount, the payee's chain and address, and how it was paid. It also shows the transaction, linked to its explorer; for a CCTP payout, the burn on Arc testnet as well.
- Amounts. The invoice and its number, if it has one, and the invoice's amount when an early-payment discount took something off. The CCTP fee, as the most it could be, or Gateway's fee, as its estimate. That no fee was taken from the payee's payment: your business paid any fee on top. What left your business: the amount and the route's fee, and on Arc mainnet, where your wallet pays its own small network fee, that fee too. What the payee received, read from their chain. A CCTP payout can show slightly more received than the amount: the part of the fee Circle did not charge reaches the payee.
- Save as PDF. It opens the browser's print dialog, where the receipt saves as a PDF. The copy leaves out the site's header and footer and the Check it yourself section, and prints the signed entry's number and hash, to find it again.
- The three checks the page makes.
- Signed by the paying workspace. The receipt is a ledger entry the workspace signed when it was shared. Its signature, body hash and chain hash are checked, and checked again in the reader's browser.
- Recorded when it was paid. The entry that recorded the payment is checked and found to name its transaction. Its content stays private.
- On the payee's chain. The chain shows a transfer of the amount to the payee in that transaction.
- Check it yourself. This section holds the signed entry, its hashes and the workspace's public key, for checking without Vestiarion.
- No names. The page shows no business, payee or person names, and no reasoning. An invoice number shows as the vendor wrote it, so the page then says so.
- Changing the link. A shared receipt shows Receipt shared:
- New link makes a new link, and the old one stops working.
- Stop sharing turns the link off.
- A link that no longer works says so and shows nothing else.
- Which payments. Only live payments have receipts: a simulated payment has nothing on chain to show. A CCTP payout can be shared once the payee's chain has minted it.
9.Get paid by a client
A receivable is money a client owes the business. In a live workspace, an owner or admin can send the client a link to pay it on Arc, on the workspace's network:
- Make the link. On Bills & receivables, on the Receivables tab, open the invoice and choose Get paid on Arc, then Copy link and send it. A new link replaces the old one.
- The client pays. The link opens a page with the amount, the due date, what it is for, the network, Arc testnet or Arc mainnet, and the workspace's address there. The client sends exactly that amount from any wallet on that network and can choose I have paid, which only asks Vestiarion to look now.
- The agent matches it. Every cycle, and on I have paid, Vestiarion reads the transfers that arrived in the operating wallet from Circle. A transfer of the same currency and amount as an open receivable, arriving after the receivable was added, settles it: from the client's own address on file, or, from any address, when it is the only such receivable and its client was sent the link. The receivable becomes received with its transaction, and the ledger records
ar_received. The client's page then says "Workspace marked this invoice paid. Thank you.", with what arrived and on which network, and that Circle reported it complete and the workspace applied it in Vestiarion. When a person marked part of the invoice as a fee, the page shows what was invoiced beside what arrived. Two open receivables of the same amount, with nothing to tell them apart, stay open for a person. - Anything else, a person applies. One transfer for several invoices, part of an invoice now, or a payment a few cents short waits under Apply payments, with the agent's suggestions: see Apply money received to invoices. A part-paid invoice's link then asks for what is still owed, and the agent applies exactly that rest by itself, by the same two rules. An open invoice of that same amount counts as another such receivable: from an address not on file, neither is matched, and a person applies it.
Only a payment matched or applied to a receivable counts as money received. Testnet faucet drips and swaps also arrive in the wallet, and they settle nothing.
The link stays on the invoice's row: Copy link copies it again at any time. A link made before October 3, 2026 cannot be shown again; Make a new link replaces it.
Let the agent remind the client
A client who forgets to pay can be reminded by the agent, by email, with the pay link. On Bills & receivables, on the Receivables tab, open the receivable and choose Remind the client by email (owners and admins, in a live workspace). It needs the client's Billing email: without one, the row offers Add billing email, which opens the billing email on the client's page.
From then on, each cycle, the agent decides whether to send a reminder now or to wait, and how firmly. Code sets the bounds:
- When. From 3 days before the due date to 30 days after it, at most every 3 days, and at most 4 reminders. The written policy sends one 3 days before the due date, one on it, one 3 days after it and the last one 10 days after it; the model may wait up to 3 days at a time, and says why.
- How firmly. Friendly at any time; firm only after the due date; final only 7 days after it, once 2 reminders went out. A firmer tone than allowed goes out as the firmest allowed, and the audit log says so.
- What it says. A fixed text by tone: who asks, how much, what for, when it was due and how late it is, with Pay on Arc testnet, or Pay on Arc mainnet for a workspace on Arc mainnet, which opens the pay link. Nothing the model writes reaches the client.
- What it asks for. The whole invoice; for a part-paid one, what is still owed, saying what arrived.
- When it stops. Once nothing is owed on the receivable, whether the agent matched the payment or a person applied payments to it, or a person rejects the receivable, or after the final reminder. The row then says to follow up with the client yourself.
The row shows the reminders sent so far, with their dates and tones, and until when the agent waits. Turn off reminders stops them. Each reminder is a signed ar_reminder_sent entry, each wait an ar_reminder_deferred one, and both appear under the invoice's How the agent decided. Turning reminders on or off is signed as ar_reminders_on or ar_reminders_off.
Before any reminder, the agent weighs what it knows about the client: a dispute, a payment the client says it made (for a week, then finance is asked to check it) or a day it promised on its statement link holds the reminders, and the client's own rules (a VIP asked about first, a softer tone, more days apart) and the HubSpot deal it was sold through can ask a person first. The card shows the next step, why, and the reminder exactly as the client would read it: see Chase what customers owe.