Lifecycle
- OPEN — Card is active and can be used for a single purchase
- CLOSED — Card is revoked and cannot be used. A card moves to CLOSED automatically after its first authorization settles (single-use), or when you close it explicitly. Any uncaptured PaymentIntent hold is cancelled to release funds back to the cardholder’s payment method.
Properties
| Field | Type | Description |
|---|---|---|
id | string | Unique card identifier |
cardholderId | string | Cardholder the card belongs to |
last4 | string | Last 4 digits of the card number |
expiry | string | Expiration date (MM/YY) |
spendLimitCents | integer | Original spend limit in cents |
balanceCents | integer | Remaining balance in cents |
status | string | OPEN or CLOSED |
createdAt | string | ISO 8601 timestamp |
Sensitive fields
The full card number (pan) and security code (cvv) are only returned by the Get Card Details endpoint. All other endpoints return only the last4.
Limits
- Minimum card amount: 25.00 — sending
25would create a $0.25 card and is rejected. - Maximum card amount: $50.00 (5,000 cents) by default for API organizations. Contact support to request a higher limit.
The plan-scoped consumer limits (500.00 on Basic) apply to the
agent-cards consumer CLI / MCP product, not to the REST API. See Choosing the right product.How card funding works
Every card belongs to a cardholder. When you create a card, a PaymentIntent hold is placed on the cardholder’s saved payment method for the card’s spend limit. The funds are authorized but not captured until the card is used. If the card is closed before the hold is captured, the hold is cancelled and the funds are released. This means:- The cardholder must have a payment method attached before cards can be created.
- The cardholder’s payment method must have sufficient funds to authorize the hold.
- Closing a card releases any uncaptured hold — funds are never moved to an intermediate wallet.