Documentation Index
Fetch the complete documentation index at: https://docs.crossmint.com/llms.txt
Use this file to discover all available pages before exploring further.
Introduction
This page covers the independent lifecycle operations for the cards flow. Pick the section that matches what you need to do — each operation is self-contained.| If you need to… | See |
|---|---|
| Stop a saved card from being used for any future card permissions | Remove a saved card |
| Cut off an agent’s ability to create new card permissions | Delete an agent |
| Immediately invalidate a single active card permission | Revoke a card permission |
| Replace a card permission whose credentials may be compromised | Rotate a card permission |
Prerequisites
- An authenticated user with a valid JWT.
- The ID of the resource you want to modify (
paymentMethodIdfor a card,agentIdfor an agent).
Remove a Saved Card
Send aDELETE request with the paymentMethodId. The card can no longer be used to create new card permissions.
Removing a saved card does not cancel card permissions already created against it. Active order intents keep working until their internal expiration is reached. To cut off an in-flight order intent immediately, revoke it or delete the agent.
Delete an Agent
Send aDELETE request with the agentId. The agent loses the ability to create new card permissions, and any active order intents tied to it stop working.
Revoke a Card Permission
To immediately invalidate a single card permission — for example if its credentials may have been compromised — send aDELETE request with the orderIntentId. The order intent transitions to the revoked phase and its credentials can no longer be used for purchases.
Only order intents currently in the active or requires-verification phase can be revoked. Already-expired or already-revoked order intents return an error.
204 No Content. The underlying saved card and agent are untouched — only the targeted order intent is affected. To replace it with a new card permission, see Rotate a card permission.
For the full schema, see the Revoke Card Permission API Reference.
Rotate a Card Permission
To rotate a card permission — for example if its credentials may have been compromised — revoke the old order intent and create a replacement:- Revoke the old order intent so its credentials can no longer be used.
- Create a new order intent against the same saved card with the same (or updated) spending rules. See Give Card Permission.
- Have the user authorize the new intent via passkey.
- Use the new credentials in your checkout flow.
To cut off an agent’s access to all of its card permissions immediately, delete the agent instead. For the full list of order intent phases — including
revoked and expired — see the Get Order Intent API Reference.Next Steps
Give Card Permission
Set up a new scoped card permission with updated spending rules.
Register an Agent
Create a new agent after deleting one.

