Bitcoin Agentic Payment
An AI agent buys from a merchant and pays in Bitcoin from the user's own wallet — priced in satoshis, confirmed by the user, completed server to server.
Bitcoin Agentic Payment
An agent can pay for a real order in Bitcoin, from the user's own Agnic Bitcoin wallet. The merchant quotes the order natively in satoshis — no currency conversion — the user approves the exact total, and Agnic pays the merchant's invoice and completes the order. No card is involved and no browser is driven.
Payments run on GoBTC Pay, a Bitcoin payment network operated by GoMining. Agnic is the agent side: it holds the user's spending limits, asks for confirmation, and signs on the user's behalf. The merchant side is an integrated merchant that accepts Bitcoin.
Bitcoin Agentic Payment is in preview. The demo merchant is obiscotti (merchant_obiscotti), an artisan biscotti bakery in Toronto, with pickup orders priced in sats. Payments are real Bitcoin on mainnet.
The flow
The order surface is the same Explore then Pay as every other Agnic order — the agent calls preview_order and place_order with payment_method: "bitcoin". What changes is what happens behind Pay.
Step by step:
- Explore. Agnic opens a checkout session with the merchant, marked as a Bitcoin order. The merchant prices it in sats. Agnic returns the total, the user's spendable balance, and a one-use confirmation token bound to that exact total. Nothing is reserved or charged.
- Confirm. The agent shows the user the order and the total in sats, and waits for an explicit yes.
- Invoice. At Pay time the merchant issues a GoBTC invoice for the exact total. Invoices expire after 15 minutes, which is why they are created at Pay and never at Explore.
- Pay. Agnic checks that the invoice equals the approved total and that the payment is inside the user's limits, then signs it from the user's wallet. GoBTC co-signs and marks the invoice paid.
- Complete. Agnic sends the invoice id to the merchant. The merchant checks with GoBTC that the invoice is paid for the full amount, then confirms the order.
Paid is not settled
A Bitcoin order has two milestones, and they are far apart in time.
| Paid | Settled | |
|---|---|---|
| When | Seconds after Pay | Later, when GoBTC broadcasts its batch |
| What it means | GoBTC has committed and co-signed the payment; the funds cannot be spent elsewhere | The transaction is on the Bitcoin blockchain |
| What the merchant does | Confirms and fulfils the order | Receives the funds at its payout address |
Merchants fulfil on paid, as GoBTC Pay is designed for. Settlement is batched by GoBTC and its timing is set by them; it can take hours or longer. Until then the user's balance shows those sats as committed. An agent must never tell a user that a payment is "confirmed on the blockchain" when it has only been paid.
Pricing and fees
- Prices are in satoshis. The merchant sets them; Agnic never converts currency. 1 BTC = 100,000,000 sats.
- 546 sats is the minimum payment. Smaller outputs are below Bitcoin's dust limit and cannot be paid.
- The payer pays the network fee. Expect roughly 200 sats for a single payment. When a payment is already pending, GoBTC folds the new one into the same transaction, so the extra fee can be just a few sats.
Because every payment carries an on-chain fee, Bitcoin suits real orders, not sub-cent micropayments.
The wallet and its limits
Each user's Bitcoin wallet is a 2-of-3 multisig issued by GoBTC Pay: one key is the user's, one is GoMining's co-signer, and the third is a recovery key managed within GoBTC Pay. Every payment needs two signatures — the user's and GoMining's — so a payment exists only when both agree.
The user's key lives in a Privy wallet owned by the user. Agnic is authorised to sign with it on the user's behalf, and only within the limits on their account:
| Limit | Default |
|---|---|
| Per payment | 10,000 sats |
| Per 24 hours | 50,000 sats |
Limits are read from the account at the moment of every payment, in sats — there is no price oracle on the money path. The user funds the wallet by sending Bitcoin to its address from any wallet (in the Agnic app: Bitcoin card → Receive BTC).
Agnic never holds or moves funds itself. The money goes from the user's wallet to the merchant's payout address through GoBTC Pay.
Try it with an AI agent
Connect the Agnic MCP server to Claude or ChatGPT, make sure the Bitcoin wallet has a few thousand sats, and ask:
I'd like to buy one Almond–Orange Small Bag (8 pieces) of biscotti from obiscotti
(merchant_obiscotti), paid with Bitcoin from my Agnic wallet. It's pickup only.
Show me the price in sats before you buy.The agent previews the order, shows the total, and places it only after you confirm:
1× Almond–Orange — Small Bag (8) — 600 sats
Total: 600 sats + ~193 sats Bitcoin network fee, paid from your Agnic Bitcoin wallet.
Pickup only. Reply to confirm.obiscotti's Bitcoin prices are set by size and are the same for every flavour:
| Size | SKU suffix | Price |
|---|---|---|
| Small Bag (8) | _8_bag | 600 sats |
| Gift Box (12) | _12_box | 800 sats |
| Gift Box (16) | _16_box | 1,000 sats |
| Premium Tin (24) | _24_tin | 1,200 sats |
Flavours: almond_orange, pistachio_cardamom, espresso_walnut, gluten_free_almond, chocolate_hazelnut, nut_free_biscotti — for example pistachio_cardamom_12_box.
When something goes wrong
| Code | What happened | Money moved? |
|---|---|---|
INSUFFICIENT_BITCOIN | The wallet cannot cover the total plus fee | No |
BITCOIN_LIMIT_EXCEEDED | The total is above the per-payment limit | No |
AMOUNT_CHANGED | The merchant's price changed after the user approved | No — preview again |
PAYMENT_IN_FLIGHT | Another payment from this wallet is being signed | No — retry in a few seconds |
PAYMENT_FAILED | GoBTC refused the payment | No |
PAYMENT_UNCONFIRMED | The payment was submitted but the outcome is unknown | Possibly — check the balance, never retry |
PAID_ORDER_UNCONFIRMED | The payment went through but the merchant did not confirm the order | Yes — contact the merchant with the payment id |
Retries are safe only where the table says so. Every payment is keyed by its invoice id, so an accidental repeat returns the original result instead of paying twice.
For merchants
A merchant accepts Bitcoin from agents by adding it to its Agentic Commerce Protocol checkout:
- When a session is created with
payment_method: "bitcoin", quote it in sats (currency: "sat") and list only the fulfilment options you offer for Bitcoin. - When the session is ready, create a GoBTC Pay invoice for the exact total, using the session id as its
externalIdso retries return the same invoice, and return it in the session aspayment: { provider: "gobtc", payment_id, amount_sats, expires_at }. - On complete, confirm with GoBTC that the invoice is paid for the full amount before creating the order.
Payouts go to the merchant's own Bitcoin address. The merchant stays the seller of record.