Payments from an agent's wallet, the RentAHuman connection, and payment links into your own Stripe. The steps are in the USDC wallet, Hiring humans and Payment links guides.
Body: { typed_data, agent_signature }. The agent signs a Base USDC transfer with its own wallet key; STACK checks the budget, the caps, your controls and any approval, then passes the request to the wallet provider unchanged, or refuses it, and a refused payment is never sent. STACK holds no key to the wallet and cannot move funds. GET /v1/accounts/wallet-owner reports whether the customer has become the owner of their agents' wallets, which is done in the Console. Caps are optional and need controls: with none, or without controls, the wallet's own balance is the limit. With "Ask me first" a payment waits for the owner: the first request is refused with CONTROL_DENIED and a retry.ref, and the agent asks again with the same payment and X-Control-Ref once the owner has approved it.
Body: { per_payment_cap_usdc?, daily_cap_usdc? }, any positive amount, null removes a cap. Owner or admin only, needs controls; an agent is refused.
Body: { monthly_budget_cents }, a whole number of USD cents above zero, or null to remove the budget. Owner or admin only; an agent is refused. Lowering applies at once and never needs controls. Setting a first budget or raising one needs controls (402 CONTROLS_REQUIRED otherwise). Raising or removing a budget is a loosening, so it needs the owner's approval in a signed-in browser (account_control_loosen): any other credential gets 403 GOVERNANCE_APPROVAL_REQUIRED with a link, and sends the approval back in X-Governance-Approval. The approval names the account and the old and new amounts. What the month has already spent is kept; a budget below it refuses further spend at once.
An agent can hire people for real-world tasks through your own RentAHuman account. STACK holds the account's key, sends the agent's calls with it and never shows it to the agent or its model. There is one RentAHuman connection per customer, granted to as many of your agents as you choose. Connect your own key the usual way, or let the agent open an account with its own wallet in two steps, because only the agent can sign for its wallet. The first step takes nothing; the second is a payment from the wallet and goes through the same Mission admission, meter, decider, caps and budget as POST /v1/accounts/:id/wallet/payments. STACK takes no fee for it.
The agent calls RentAHuman through the connection with stack_service_tools and stack_service_call_tool (or the proxy: a POST to /v1/proxy with RentAHuman's MCP endpoint): searching people, posting and funding a bounty, reading applications and deliveries. It talks with the people it hires through the same call tool (send_message, get_conversation, list_conversations). A person who applies, delivers or writes wakes the agent with the wake source service_event, which carries the service, the kind of event and the ids and never what the person wrote; the agent reads the conversation and answers through the call tool. What RentAHuman returns is untrusted text, marked as such. Disconnecting the connection or erasing the account deletes the endpoint and revokes the key at RentAHuman first; the RentAHuman account and its balance stay yours.
Card payments go through your own Stripe, and USDC payments for priced paths go into the agent's own wallet. STACK holds no money on either. Every payment is in the signed record.
Refunds are made where the money is: in your Stripe dashboard for a card payment, and by the agent paying the payer back from its own wallet for a USDC payment. STACK reads Stripe's refund and dispute events and updates the payment.