For payees
This page is for you if you are paid through Dynamo: you deliver work, and a budget pays you for it as you go. In Dynamo you are known by one address, your service node, and you keep the key for that address yourself.
Each feature carries one of three labels:
- Live: usable today in Control Mode (no money anywhere), with test credit cards, or on a test
chain.
- Preview: built, behind a switch that is off unless the operator turns it on.
- Release-gated: needs real money, live credit card keys or operator-run ramps. Not offered in
this release.
Nothing on this page is a promise about real money.
Getting set up
Prove who you are
You sign in to the payee pages by signing a short message with your own key. The signature is checked on the spot and is valid for a few minutes; there is no account or password. If you prefer, the budget owner can give you a longer-lived payee credential, but only after you sign once to agree to it. The credential reaches only your own payee pages, the records of payments to you, and the metering route for allowances that pay you.
Tell Dynamo where you are paid (Live; real payouts Release-gated)
- Stablecoin: your service node address is where you are paid. You can register another
address with a signature from it, but in this release the contracts still pay your service node.
- Credit card payments: Dynamo creates a test account for you with the card processor and gives
you a link to finish its sign-up. You can be paid only once the processor reports the account as verified; until then a budget cannot open a new allowance to you on the credit card rail, unless the operator has listed you directly.
- Bank payouts from stablecoin (Preview): where the operator has turned ramps on, you can
register your own bank account at the ramp provider. Payouts go only there and never exceed what you paid in.
Offer what you accept
When money moves, a payer can by default only open an allowance to you with your signed offer: the kinds of work you accept and how long the offer is valid. (An operator can switch this requirement off.) You can sign it in your own browser wallet on the receive page and send it to the payer. Your key never leaves the wallet.
You can also offer service terms (Preview: only where the operator turns on a terms catalogue): measurable promises such as a response time, with a stated measurement window. A payer accepts your terms when opening an allowance to you.
Getting paid
- As you deliver, the budget signs vouchers: each one is a running total of what you have earned
on one allowance. The latest voucher covers everything before it.
- On stablecoin budgets you collect your vouchers and settle them yourself, with your own key, or on
contract version 2 through a relayer that pays only gas. On contract version 1 the payee kit does this for you: it checks every voucher offline first, settles with your key, and claims the ones with the nearest deadline first (Live on a test chain). It checks version 2 vouchers the same way; on version 2 the relayer submits them.
- On credit card budgets the processor pays your verified account for your signed totals, minus
each fee, which is recorded as its own line.
- The receive page shows what has been signed to you, what has been settled, and what is still
waiting, for every allowance that pays you (Live).
What proves your work
Each voucher is signed and can be checked offline against the signer you expect. Every allowance that pays you, every revoke and every payment record is a signed record linked to the one before it. The budget owner can export them as one evidence file that anyone can check offline with dynamo verify <evidence-file.json> --signer 0x…. The check proves what was signed; whether a payment reached a chain or a bank is a separate check.
What offline verification covers. The verifier checks every signature and digest in the file. On its own the file does not prove billing: the engine-signed records do not yet bind each stream's session key. Verification is complete when you pair it with the on-chain settlement or with the engine-signed payment records. It is weakest on Control Mode and the credit card rail, where there is no chain to check.
When a budget is revoked or expires
Work you delivered and that was signed before the stop stays yours to claim:
- A revoke from the owner API, the SDK or the portal signs and settles your work first, then stops
the allowance and everything below it. If a settlement fails, the revoke still goes ahead and its signed record lists what was not settled; the rules below decide how long you can still claim it.
- On stablecoin contract version 2, vouchers signed at or before a revoke or expiry stay settleable
for 7 days after it. Claim within that window.
- On contract version 1, a revoked allowance still settles work signed before the revoke, but once
the payer closes the budget it can no longer settle. Settle promptly.
- On adopted payment channels (Live on local test setups), the payer's withdrawal is refused while
value covered by your signed vouchers is unclaimed, and the payee side raises an alert when a claim deadline is at risk.
- On credit card payments, if your account is not yet verified, your earnings are held, not moved
or refunded. After 7 days unverified, the operator is alerted once.
Disputes, on objective facts only
Disputes are Live in Control Mode, with test credit cards and on a test chain; cases about a breach of terms are Preview, because terms need a terms catalogue the operator turns on.
- A payer can open a case only on an objective fact: a breach of your agreed terms reported by a
catalogue signer the payer opted into, a task step not delivered against its declared proof, or a payment record that does not match its voucher.
- You answer with your own signature, conceding or contesting. Your answer is recorded; the outcome
is computed from the facts, never from either side's say-so.
- The only money a case moves is a refund of value delivered after an attested breach and still
held, never above the amount in dispute. Value that is already final is not refunded through Dynamo; the case is then escalated with a signed package for someone outside to review.
- Refunds are yours to offer, never imposed: AI inference carries no refunds by default. Only terms you offer and the payer accepts before use can move value back, and Dynamo enforces them exactly without judging a refund itself.
- On contract version 2, a breach report can touch your held value only after you accept, with your
own key, the signer who reports it. Accept only signers you trust to report measurements.
See Recourse.
Keeping your key safe
- Dynamo never holds your key. A deployment configured with a payee's private key refuses to start.
- A lost key is lost. Nobody at Dynamo can recover it. Concretely:
- you can no longer sign payee requests yourself or get a new payee credential. A payee credential
you received earlier keeps working until it is revoked or expires, and it can still reach the payee pages (offer terms, your payments), so revoke it if it may be in the wrong hands. It can never change where you are paid: registering a destination or starting an off-ramp takes your own key;
- on stablecoin contract version 1 your signed vouchers can no longer be settled, because only your
key can settle them;
- on contract version 2 a relayer can still settle, but the money is paid to your service node
address, which you can no longer move;
- on credit card payments your payouts go to your processor account, but new allowances need (by
default) a fresh offer signed with your key.
- Keep the key in a wallet or key store you control, with a backup.
Related pages
- Getting paid as a payee (the developer guide)
- Human payments
- Evidence and disputes
- For people who fund a budget