Updates the specified card. Use this endpoint to:
- Activate or deactivate a card
- Allocate funds to a card
- Configure recurring allocations
- Set spending limits
Permissions
| Action | Required permission |
|---|---|
Change status_preference or name | Card owner, admin, or vendor_cards_manage permission |
| Change allocation params | Admin or vendor_cards_manage permission |
| Change spending limit params | Admin or vendor_cards_manage permission |
Top-up
If you send allocated_amount_preference_cents with the same value the card already has, but the card has spent some of those funds (i.e. the actual balance is lower), the system will automatically top-up the card back to the requested amount. This is useful for refilling a card to its original balance after spending.
Example: A card was allocated 50,000 CLP. The user spent 20,000 CLP, so the actual balance is 30,000 CLP. Sending {"allocated_amount_preference_cents": 50000} again will top-up the card back to 50,000 CLP.
For a complete guide with examples, see Card Allocations.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Unauthorized. The API key user does not have the required permissions (admin or vendor_cards_manage) to modify allocations or spending limits.
Vendor card not found (or not visible to the caller).
Unprocessable Entity. Possible causes: read-only spending-limit fields sent
(limit_amount_cents / limit_interval / allocated_amount_cents →
{ "error_code": "vendor_cards/spending_limits_readonly" }), modifying a
canceled card, invalid interval value, insufficient company balance, a
missing user ({ "message": "User not found" }), or a generic update
failure ({ "error_code": "vendor_cards/update_failed" }).