Skip to main content

Funding sources

An agent wallet pays in USDC, so it needs USDC in it. This page explains the ways money reaches a wallet, who holds the funds at each step and who has to sign.

  1. USDC you holdSent to the wallet's address
  2. Multisig treasuryRefills the wallets of a fleet
  3. Agent walletHolds the USDC the agent spends
  4. Bank cardStripe Link, Base mainnet only
  5. Refill requestAsked to a teammate, who uses one of the above
An agent wallet is funded with USDC you already hold, with a bank card through Stripe Link on Base mainnet, from the multisig treasury, or after a refill request to a teammate.

In short, a wallet is funded with USDC you send, a card purchase, a refill from the multisig treasury or a request to a teammate, and the welcome offer is not funding: it pays sellers on your behalf.

One rule underneath: funds sit in smart accounts​

An agent wallet is a smart account: a contract on the blockchain that holds the USDC. Keyban does not keep a balance for you in a database. The funds are in the wallet's own contract. The agent cannot sign without being authenticated on Keyban, and Keyban co-signs only what the spending policy allows. See Shared key.

The multisig treasury is also a smart account. It is a separate pot, with its own signers, that sits one step upstream of the agent wallets.

The ways to fund a wallet​

USDC you already hold​

Send USDC on the wallet's network to the wallet's address. This is the simplest source and it works for any wallet. The address is known once the wallet is deployed, even before the agent has connected.

Bank card​

A person can buy USDC with a bank card from the wallet's page, when card top-ups are enabled for the account. The purchase goes through Stripe Link, and the USDC is delivered to the wallet address.

  • It runs on Base mainnet only.
  • Each purchase is between 5 and 999 euros.
  • Stripe may ask the buyer to sign in to or create a Link account and to complete identity verification before it takes the payment.

A card purchase is made by a person, never by the agent: the agent has no tool to buy funds.

A request to a teammate​

An operator of a wallet can raise a refill request for it, with an optional amount and a note. The request appears in the Inbox, and the people who manage the treasury are notified by e-mail. It stays open until one of these happens:

  • a treasury manager declines it, with an optional reason;
  • the requester cancels it;
  • it is fulfilled: either the treasury transfers delivered the requested amount to the wallet, in which case Keyban closes the request by itself, or a treasury manager closed it by hand, for example after a card top-up.

A wallet can have only one open request at a time.

The multisig treasury, for fleets​

When you run several agents, you can keep your money in a multisig treasury, a shared pot that several signers control together, and refill the agents from it instead of funding each wallet by hand. It is available from the Growth plan and above.

The Keyban welcome offer​

A new account can receive a Keyban welcome offer: a small USDC credit, granted for your first agent wallet on Base, that pays x402 payments for a limited time. It does not put USDC in the wallet. Keyban pays the seller itself, from a Keyban sponsor wallet, and the payment is deducted from the offer.

  • It covers a payment only when the whole price fits in what is left of the offer. A payment that costs more is paid entirely from the wallet, never split.
  • It only applies to x402 payments of the wallet that earned it, on the network of the offer, before it expires.
  • It pays only an agent that declares the sponsored-x402 capability. The Keyban wallet MCP declares it on its own, so the user has nothing to configure; a custom agent that does not declare it is never covered by the offer, and its payments come from the wallet.
  • The wallet's spending policy applies to these payments as it does to any other.
  • It is granted when the wallet is created, but it pays only once the organization has accepted Keyban's terms. Until then, a payment the offer would cover is refused with policy/terms-not-accepted, and the wallet's own USDC does not pay in its place.
  • It is not guaranteed: it depends on the offer still being available when the wallet is created.

Warm wallet Coming soon​

A warm wallet Coming soon is planned to make topping up smoother. It is not available yet.

Who holds the funds and who signs​

  1. Agent wallet

    One per agent

    • Funds in the wallet's smart account
    • The agent must be authenticated on Keyban to sign
    • Keyban co-signs only a payment that passes the spending policy
    • A payment above the approval threshold waits for an operator
  2. Multisig treasury

    One per organization and network

    • Funds in the treasury's smart account
    • A transfer needs a threshold of signers, each signing with a passkey
    • It refills agent wallets of the organization and address-book contacts
    • Available from the Growth plan
An agent wallet is spent by one agent, with its own key share and Keyban's, inside a spending policy. The multisig treasury is moved by a threshold of human signers, each with a passkey, and refills the agent wallets.

In short, people decide how much goes into the treasury and from there into each agent's wallet, and the agent only ever spends what is already in its own wallet, within its policy. The agent has no way to reach the treasury.