Get Payment Card Features
This endpoint returns the set of features that are enabled and available for a given payment card. The response is an array of feature identifiers, each representing a capability such as activating the card, locking/unlocking it, setting a PIN, or viewing spending reports. Use this endpoint to determine which card management actions are permitted for a card before presenting options to a customer.
Endpoint
GET /api/paymentCards/cardFeatures
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint when building a card management UI to dynamically display only the actions available for a given card. The available features may differ by card type (Physical, Virtual, or Burner) or by the card's current state (e.g., a closed card will not expose Activate or LockUnlock). Checking this endpoint before rendering controls prevents users from attempting unsupported operations.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| cardId | string | No | The unique identifier of the payment card whose features should be returned. |
Response
200 OK
Returns an array of feature strings. Each element is one of the following enumerated values:
| Value | Description |
|---|---|
| Activate | The card can be activated. |
| Close | The card can be closed/cancelled. |
| LockUnlock | The card can be locked or unlocked. |
| ReissueCard | The card can be reissued (e.g., replacement). |
| SetUpPin | A PIN can be set or changed for the card. |
| OrderStatus | The shipping or order status of the card can be checked. |
| SpendingReport | A spending report is available for the card. |
| TransactionLimits | Transaction limits can be viewed and modified. |
| TransactionLimitsViewOnly | Transaction limits can be viewed but not modified. |
[
"Activate",
"LockUnlock",
"SetUpPin",
"SpendingReport",
"TransactionLimits"
]Error Codes
| Code | When it happens |
|---|---|
| 400 | The cardId parameter is malformed or in an invalid format. |
| 401 | Token missing, expired, or invalid. |
| 403 | Insufficient permissions to view features for this card. |
| 404 | No card found matching the provided cardId. |
| 500 | Internal server error. |
Common Mistakes
- Omitting the
cardIdquery parameter may return a default or empty feature set rather than card-specific features; always pass a specific card ID to get accurate results. - Rendering all possible card actions in the UI without first checking this endpoint can expose options that the card's current state or type does not support, leading to failed API calls downstream.
- The
TransactionLimitsandTransactionLimitsViewOnlyvalues are mutually exclusive — ifTransactionLimitsViewOnlyis present, do not render controls that write limit changes.
Related Endpoints
GET /api/paymentCards— Retrieve all payment cards for a customer.POST /api/paymentCards/lockUnlock— Lock or unlock a payment card.POST /api/paymentCards/setPin— Set or update the PIN for a payment card.POST /api/paymentCards/activate— Activate a payment card.POST /api/paymentCards/reissue— Reissue a payment card.
Example
curl -X GET "https://api.banking.netevia.dev/api/paymentCards/cardFeatures?cardId=card_abc123" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"