Use this page as a map for issue (create credentials), manage (freeze, labels, policy profile), and test (simulated merchants) without mirroring a full card-program vendor taxonomy.
#Issue
- Dashboard — Agent cards: create a policy profile and card together, or attach flows from Budgets.
- API: proxy-card and spend flows are exposed through the Agent Bank / agent-spend surface your integration already uses; interactive reference lives on api.dino.id.
#Simulated (test) cards
When Issuing runs in simulated mode, Dino can mint flexible card types for dashboard and API experiments. Defaults after provisioning use this path so teams are not silently placed on open-ended live cards.
#Live network cards (Stripe / Lithic)
For live issuance, policy is enforced in the API (not only in the UI):
- Single use card type.
- Per-transaction spend limit only.
- A positive limit in the account currency (e.g. USD cents).
Dino reserves that amount from the team wallet before creating the network card. If creation fails, the reserve is released and the remote card is canceled where possible. If the card is canceled later, the reserve is released. When a charge settles, settlement consumes the reserve (same idea as JIT collateral).
#Manage
- Policy profile: budget, approvals, merchant rules, keys — from Cards → View policy (or Budgets).
- Card row: status (active / frozen / canceled), optional PAN/CVV reveal (when enabled and supported by the provider).
#Test checklist
- Confirm wallet balance covers the intended per-transaction limit for a live single-use card.
- Issue the card; confirm ledger or wallet reflects the reserve where your workspace exposes it.
- Complete or cancel a test authorization; confirm settlement or cancel releases or consumes the reserve as expected.
- Prefer simulated cards for broad type experiments; use live only when you need real network behavior.