Skip to content

Give an employee a wallet

In this guide, you’ll fund your workspace treasury, create a wallet for an employee, set its budget and limits, and watch it make its first x402 payment to a paid data API. Payments are made in USDC on Base. It takes about 15 minutes.

  • The Admin or Owner role. Only these roles can fund wallets.
  • The Team plan or above. Wallets and x402 aren’t available on Free.
  • An employee to give the wallet to. This guide uses Ada, at L1 Approve.
  • A card, or USDC on Base in a wallet you control, to fund the treasury.
  • The URL of a paid API that supports x402. This guide uses a company data API that charges 0.05 USDC per lookup.

Fund the treasury

Go to Settings > Treasury and click Add funds. Choose a method:

Method How it works Available after
Card Pay by card. Orqane converts the amount to USDC. A few minutes
Bank transfer Pay from your bank account. Orqane converts the amount to USDC. 1 to 3 business days
USDC transfer Send USDC on Base to the treasury address shown on the page. About a minute, after confirmation

Add 100 USDC. The treasury balance updates when the funds arrive.

Create the employee's wallet

Open Employees, select Ada and go to the Wallet tab. Click Create wallet. Orqane creates a wallet in Ada’s name and manages its keys for you: Ada never sees or handles a private key.

Click Fund, enter 20 USDC and confirm. Leave Auto top-up off for now.

Set the budget

Open Ada’s Costs tab and edit her budget:

Setting Value
Period Monthly
Credits 20 (unchanged)
Payments 20 USDC
At 80% Notify the human manager
At 100% Stop and ask for approval for any further spend

Set the spend limits

Back on the Wallet tab, click Edit limits:

Limit Value
Per payment 1 USDC
Per task 5 USDC
Per merchant per period 10 USDC per month

Spend limits are hard caps. A payment above them is blocked, not sent for approval, unless an Admin raises the limit.

Add the merchant to the allowlist

Under Merchant allowlist, click Add merchant and enter the API’s domain, such as api.companydata.example. Keep the mode on Allowlist only: a payment request from any other service is blocked, and the refusal appears in Activity.

Give Ada a task that needs paid data

Open Chat with Ada and write:

Look up the headcount and annual revenue of Acme Corp using the company
data API at https://api.companydata.example.

Ada calls the API. The API answers 402 Payment Required with its price: 0.05 USDC. Ada checks the amount against her limits and the allowlist.

Approve the payment

Because Ada is at L1 Approve, every Spend action waits for approval. Open Approvals. The request shows the merchant, the amount, the reason and Ada’s remaining budget.

Click Approve. Ada signs the payment, retries the call with proof of payment and receives the data.

Find the receipt

Open Ada’s Activity tab and select the run. The Payment step shows the receipt:

Field Example
Merchant api.companydata.example
Amount 0.05 USDC
Network Base
Transaction 0x8f3a…c21e, with a link to the block explorer
Approved by You

The payment also appears in Costs, under Payments.

You’ve funded your treasury, given Ada a wallet with clear limits and watched her pay for data with x402.

When Ada reaches L2 Act within limits, set a Spend per payment threshold on her Autonomy tab, such as 0.10 USDC. She then pays small amounts to allowlisted merchants on her own and asks only above that. Her spend limits, budget and allowlist still apply at every level.