Create a single-use virtual card via POST /v1/cards with type SINGLE_USE; Lithic automatically closes the card after the first transaction clears
Retrieve the card's PAN, CVV, and expiry via GET /v1/cards/{token} immediately after creation — these details are only fully returned at creation time
Pass the virtual card details to the payment form or merchant API for the intended one-time purchase
Monitor the transaction via webhook (transaction.created and transaction.updated events) to confirm the authorization and settlement complete
If the card was not used, explicitly close it via POST /v1/cards/{token} with state CLOSED to prevent any future unauthorized use
Reconcile the transaction against your internal order record using the token and merchant fields in the transaction payload
Known gotchas
SINGLE_USE cards on Lithic close after the first settled transaction, but a pending authorization may hold the card open briefly; do not assume the card is closed until you receive the settlement event
Full card PAN details are only returned in the creation response; subsequent GET calls return a masked PAN — store details at creation if needed for downstream use
Lithic charges a card creation fee per card on some program tiers; validate pricing before provisioning large volumes of single-use cards
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp