Skip to main content
These flows are actively being refined. Crossmint’s customer success engineers (CSE) will work with you to review your architecture. Contact Crossmint to get started.

​
Overview

Virtual cards let your agent make credit card purchases without ever seeing the user’s real card number. Crossmint derives a scoped virtual card number from the user’s saved card, with configurable spend limits and issuer verification.

​
Key Properties

These are not new cards. Virtual cards are tokenized representations of the user’s existing card. This means:
  • Charges appear on the user’s regular bank statement
  • The user keeps their rewards points and cashback
  • Standard dispute resolution and fraud protection apply
  • No separate account or card to manage
Each virtual card (called an order intent in the API) comes with configurable mandates (spend limits, period, description) and requires card issuer verification before it can be used.

​
How It Works

The system has three layers:
ConceptAPI nameWhat it is
Saved cardPayment Method (paymentMethodId)The user’s tokenized credit card
Agentic enrollmentEnrollment (enrollmentId)Registers the card for agent use; requires cardholder verification
Virtual cardOrder Intent (orderIntentId)A scoped spending authorization with mandates
The flow is: save card → enroll for agentic use → create order intents against it.
Integration guide coming soon. Contact Crossmint to get early access.