1. Get your credentials
You need an Agentcard organizationclient_id and client_secret from the dashboard. Exchange them for an access token:
$ORG_TOKEN. Sandbox credentials create sandbox users and test cards. Start there.
2. Authenticate a user
Send the user a one-time code, then verify it. In sandbox the code is always111111.
user.id. Every card call names the user with it, using your org token. You don’t need the access_token or refresh_token for the steps below.
Record consent once:
3. Complete KYC
Issued cards require identity verification. Read the status, and hand the user the hosted page it returns:identity.verification.updated or by reading the status again. In sandbox nothing is reviewed, so approve the test user directly:
4. Fund the company balance
Your company balance funds this card. If your organization is user-funded, switch it to company-funded once, in the dashboard under Settings, Issuing. An org owner has to do this. The change takes effect in sandbox immediately, and sandbox needs no plan or subscription. Until you switch, creating the card below is refused withcompany_flow_unavailable.
Then add test money. In sandbox it is a mock balance and never real money:
5. Create a card
Create the card with the user’s id:kyc_required or org_wallet_funding_required, which point back to steps 3 and 4.
More on issuing →
6. Use the card
Read the credentials when your agent is at the checkout, not before:transaction.authorized tells your server money moved.
More on using cards →
What’s next
Authenticating a user
Tokens, consent, refresh, and what each credential may call.
Completing a KYC
Hosted or custom verification, statuses, sandbox simulation.
Issuing a card
Funding, single-use and multi-use cards, merchant locks.
Using the cards
Reading credentials, paying, pausing, closing, webhooks.