1. Get your credentials
You need an Agentcard organizationclient_id and client_secret. Create them in the dashboard and exchange them for an access token:
$ORG_TOKEN below. Sandbox credentials create sandbox sessions and sandbox authorizations, so start there. When the rehearsal works, go to production.
2. Store a card
Create a vault session and send the user the link wherever you already talk to them: iMessage, WhatsApp, your app.vault.session_linked webhook with their user_id, or you poll the session until its status is linked. Store that user_id, you need it on every purchase.
For a test run, store a test card: any of Stripe’s published test cards, any future expiry, any CVC.
More on adding cards →
3. Attach Agentcard to your browser
Install the SDK next to your browser provider. This example uses KERNEL; Browserbase and any CDP browser work the same way.4. Complete the purchase
Let your agent shop as usual. At checkout it should fill the card form with placeholder data, any of Stripe’s published test cards, and submit. The Agentcard SDK intercepts the processor request and pauses it.onApprovalUrl fires with a link; send it to the user. They approve with their passkey, their device sends the real card to the processor, and the paused request resumes with the real response.
Then confirm the order with the merchant before you tell the user anything:
Try it against a store that always works
shop.agentcard.sh is a demo store on Stripe test mode, kept running for exactly this rehearsal. Add a product, submit the card form with the placeholder card, approve on the device that holds your passkey, and the order completes with a real test-mode charge.Go to production
The flow does not change. There is no separate production host, and the mode comes from the credential you call with, never from the URL (more on credentials →). Create a production client in the dashboard under Settings → Developers → Credentials and mint$ORG_TOKEN from that pair instead of the sandbox one.
Three things from your sandbox run do not carry over.
Sandbox and production users are separate. A sandbox user_id sent with production credentials is refused with a 404:
vs_ id with the production credentials that created it.
A webhook endpoint belongs to one mode, so add a production endpoint or vault.session_linked never arrives live.
Steps 3 and 4 change in one place: point your agent at the store you sell through, and set merchant to the name that store shows the user. shop.agentcard.sh stays on Stripe test mode whatever credentials you call with, so it never charges a real card. At your own store the purchase charges the user’s real card.
Keep going
Adding a card
Open vs connected sessions, webhooks vs polling, returning users.
Creating a cart
Browsers, SDK options, and the Commerce SDK alternative.
Completing a purchase
Approval, reconciliation, webhooks, supported processors.