Retrieve all digital wallet token subscriptions associated with the authenticated user from the cache.
Get All Subscriptions by User from Cache
This endpoint retrieves all digital wallet token subscriptions belonging to the authenticated user directly from the cache layer. Each subscription record includes the associated payment card details, financial account information, and token status. Use this endpoint when you need a fast read of subscription data without querying the primary data store.
Endpoint
POST /subscriptions/list/cache
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2
Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint to display a user's active and historical digital wallet token subscriptions, for example when rendering a card management dashboard or auditing which payment cards have been provisioned to digital wallets. Because results are served from cache, this endpoint offers lower latency than a live database query and is suitable for high-frequency read scenarios. It is appropriate when near-real-time data is acceptable and you do not need the absolute latest state.
Request Body
This endpoint does not require a request body.
Response
200 OK
Returns an array of carddigitalwallettokenresponse objects.
carddigitalwallettokenresponse Object
carddigitalwallettokenresponse Object| Field | Type | Description |
|---|---|---|
id | string | Unique identifier of the digital wallet token subscription |
status | string | Current status of the subscription (e.g., ACTIVE, SUSPENDED, TERMINATED) |
createdAt | string (date-time) | ISO 8601 timestamp when the subscription was created |
updatedAt | string (date-time) | ISO 8601 timestamp of the most recent update to the subscription |
requesterName | string | Name of the entity or service that requested the token provisioning |
financialAccount | string | Identifier of the financial account linked to the subscription |
financialName | string | Display name of the financial account |
financialNumber | string | Masked account number of the financial account |
iconUrl | string | URL of the icon representing the digital wallet or subscription brand |
paymentCard | object | Nested object containing details of the associated payment card (see below) |
paymentCard Nested Object
paymentCard Nested Object| Field | Type | Description |
|---|---|---|
id | string | Unique identifier of the payment card |
expirationDate | string | Card expiration date (MM/YY format) |
last4 | string | Last four digits of the card number |
cardholder | string | Full name of the primary cardholder |
authorizedUser | string | Name of the authorized user associated with this card, if applicable |
departament | string | Department identifier associated with the card (business accounts) |
cardName | string | Custom display name assigned to the card |
partnerName | string | Name of the partner program associated with the card |
formFactor | string | Card form factor: Physical, Virtual, or Burner |
status | string | Current card status (e.g., OPEN, SUSPENDED, CLOSED) |
[
{
"id": "sub_8a3f21bc4d7e9c01",
"status": "ACTIVE",
"createdAt": "2025-11-14T10:23:45Z",
"updatedAt": "2026-01-07T08:15:00Z",
"requesterName": "Apple Pay",
"financialAccount": "fa_c72a9381de540b6f",
"financialName": "Business Checking",
"financialNumber": "XXXXXXXXXX",
"iconUrl": "https://cdn.netevia.com/icons/apple-pay.png",
"paymentCard": {
"id": "card_91d4f825bc3ea706",
"expirationDate": "09/28",
"last4": "4521",
"cardholder": "Jane Smith",
"authorizedUser": null,
"departament": "Marketing",
"cardName": "Marketing Card",
"partnerName": "Netevia Business",
"formFactor": "Virtual",
"status": "OPEN"
}
},
{
"id": "sub_2d6b07e8a1f43c59",
"status": "SUSPENDED",
"createdAt": "2025-09-03T14:55:12Z",
"updatedAt": "2025-12-20T11:40:30Z",
"requesterName": "Google Pay",
"financialAccount": "fa_c72a9381de540b6f",
"financialName": "Business Checking",
"financialNumber": "XXXXXXXXXX",
"iconUrl": "https://cdn.netevia.com/icons/google-pay.png",
"paymentCard": {
"id": "card_3f8a152cd09b7e24",
"expirationDate": "03/27",
"last4": "8874",
"cardholder": "Jane Smith",
"authorizedUser": "Tom Reynolds",
"departament": "Operations",
"cardName": "Ops Expense Card",
"partnerName": "Netevia Business",
"formFactor": "Physical",
"status": "SUSPENDED"
}
}
]Error Codes
| Code | When it happens |
|---|---|
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to access subscription data |
| 404 | No subscriptions found for the authenticated user |
| 500 | Internal server error or cache service unavailable |
Common Mistakes
- Sending a request body — this endpoint does not accept or require a body; including one will not affect the response but is unnecessary.
- Treating a
404as an error condition — it simply means the user has no digital wallet token subscriptions yet, not that the endpoint is misconfigured. - Assuming cached data is always current — the cache may lag slightly behind the live database; for authoritative real-time state, use the non-cached subscriptions endpoint.
- Not handling an empty array response — a
200 OKwith[]is a valid response when the user has no subscriptions.
Related Endpoints
POST /subscriptions/list— Retrieve all subscriptions by user directly from the primary data store (non-cached)POST /subscriptions/create— Provision a new digital wallet token subscription for a payment cardPOST /subscriptions/update— Update the status or details of an existing subscriptionPOST /cards/list— List all payment cards associated with the authenticated user
Example
curl -X POST https://api.banking.netevia.dev/subscriptions/list/cache \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"