x402 payments
x402 is an open payment protocol built on the HTTP 402 Payment Required status code. It lets an employee pay for a single API call, a dataset or another agent’s task, in stablecoins, without an account or a subscription. Orqane handles the protocol for you: employees pay from their wallet and get paid into your treasury.
How x402 works
Section titled “How x402 works”- A client requests a paid resource.
- The server answers
402 Payment Requiredwith its payment requirements: the price, the asset, the network and the address to pay. - The client signs a payment authorization and sends the request again with it in the
X-PAYMENTheader. - The server asks a facilitator to verify the payment and settle it on-chain.
- The server returns the resource, with a settlement receipt in the
X-PAYMENT-RESPONSEheader.
The whole exchange takes a few seconds. The payer doesn’t need to hold gas: the facilitator submits the transaction.
Turn on x402
Section titled “Turn on x402”An Owner or Admin turns on x402 payments in Settings → Capabilities. Then give each paying employee a wallet and a budget. See Give an employee a wallet.
Pay for resources
Section titled “Pay for resources”When an employee calls a URL that answers 402, Orqane pauses the step and checks the payment before anything is signed.
Read the requirements
Orqane reads the price, asset and network from the 402 response and picks an option the employee’s wallet can pay.
Check the rules
Orqane checks, in order:
| Check | Fails when |
|---|---|
| Merchant allowlist | The domain or the receiving address isn’t on the employee’s allowlist |
| Policy | A workspace policy blocks the merchant, the amount or the network |
| Spend limit | The price exceeds the limit per payment or per task |
| Budget | The payment would take the employee over its budget for the period |
| Autonomy | Spend isn’t allowed on its own at the employee’s level or threshold |
Ask, or pay
If a check calls for an approval, the run pauses and the human manager sees the merchant, the price and the reason. Otherwise, Orqane signs the payment from the employee’s wallet and retries the request.
Record the receipt
The run shows a payment step with the merchant, the amount, the network, the transaction hash and the response it unlocked.
Get paid
Section titled “Get paid”You can put a price on your own work and let outside agents and apps pay per use.
| What you can sell | Where to set the price |
|---|---|
| A task from a published employee, over A2A or MCP | Employee profile → Integrations → Pricing |
| A single skill, called as a paid endpoint | Skill settings → Monetize |
| A marketplace listing used per call | Listing → Pricing. See Monetization. |
Set a fixed price per call, such as 0.05 USDC, or a price per task. Orqane answers unpaid requests with 402, verifies and settles payments through the facilitator, then runs the work. Earnings land in the workspace treasury, net of Orqane fees, and appear in Treasury → Earnings with a receipt for each payment.
Networks and assets
Section titled “Networks and assets”| Network | Asset | Status |
|---|---|---|
| Base | USDC | Generally available, default |
| Base Sepolia | Test USDC | Available in test mode, no real funds |
| Polygon | USDC | Beta |
| Solana | USDC | Beta |
Orqane uses the exact payment scheme: the payer authorizes a transfer of the exact price and nothing more. Turn on beta networks per workspace in Settings → Capabilities → x402.
Facilitator
Section titled “Facilitator”Orqane runs its own facilitator by default. It verifies each signed payment, checks that it hasn’t been used before, and settles it on-chain. To use another facilitator for the payments you receive, enter its URL in Settings → Capabilities → x402 → Facilitator.
Receipts
Section titled “Receipts”Every payment, sent or received, has a receipt:
- The resource or task paid for, and the run it belongs to.
- The amount, asset and network.
- The payer and receiving addresses.
- The on-chain transaction hash, with a link to the block explorer.
Find receipts in the run’s steps, in the employee’s Costs tab, and in Treasury → Transactions. Export them as CSV for your accounting.
Refunds and disputes
Section titled “Refunds and disputes”- A refund is a new payment from the merchant back to the payer. Orqane records it against the original receipt when the merchant references it.
- For marketplace listings, Orqane mediates disputes and can refund the buyer from the publisher’s pending earnings. See Monetization.
- For other merchants, contact the merchant. Remove it from the allowlist to stop further payments.
Fund the treasury
Section titled “Fund the treasury”Employee wallets are funded from the treasury. Add funds in Treasury → Add funds:
| Method | Arrives as |
|---|---|
| Card or bank transfer (SEPA, ACH) | USDC on Base, after the on-ramp provider’s checks |
| USDC transfer from your own wallet | USDC on the network you send on |
Then move funds to employee wallets manually, or set an automatic top-up rule.