Retrieve the unique ID and details of a specific payment card by its identifier.
Get Payment Card ID
The Get Payment Card ID endpoint retrieves the unique identifier and relevant details for a specific payment card. This is essential for payment card management workflows, enabling partners to reference a particular card for subsequent operations such as updates, status changes, or deletions.
Endpoint
GET /api/paymentCards/v2/viewPaymentCard
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 when you need to look up the details of a specific payment card and confirm its current state before performing further operations. It is commonly called prior to updating card settings, freezing or closing a card, or displaying card information to the cardholder. The response is AES-encrypted to protect sensitive card data in transit.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| paymentCardId | string | Yes | The unique identifier of the payment card to retrieve. |
Response
200 OK
| Field | Type | Description |
|---|---|---|
| aes | string | AES-encrypted payload containing the payment card details. Decrypt using the shared AES key established during partner onboarding. |
{
"aes": "U2FsdGVkX1+exampleEncryptedPayloadString..."
}Error Codes
| Code | When it happens |
|---|---|
| 400 | paymentCardId is missing or not a valid format |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to access the specified payment card |
| 404 | No payment card found for the provided paymentCardId |
| 500 | Internal server error |
Common Mistakes
- Omitting the
paymentCardIdquery parameter will result in a 400 error — it is required for every request. - Attempting to retrieve a card that belongs to a different partner or customer scope will return 403; ensure the token is scoped to the correct partner and customer.
- The response body is AES-encrypted. Passing the raw
aesvalue directly to downstream systems without decryption will yield unreadable data. - Tokens expire after 10 minutes. Refresh via
POST /api/auth/refreshbefore making this call if the token may have elapsed.
Related Endpoints
GET /api/paymentCards/v2/viewPaymentCards— List all payment cards for a customerPOST /api/paymentCards/v2/createPaymentCard— Issue a new physical, virtual, or burner payment cardPUT /api/paymentCards/v2/updatePaymentCard— Update settings or status for an existing payment cardDELETE /api/paymentCards/v2/deletePaymentCard— Remove a payment card from a customer account
Example
curl -X GET "https://api.banking.netevia.dev/api/paymentCards/v2/viewPaymentCard?paymentCardId=YOUR_PAYMENT_CARD_ID" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Accept: application/json"