Get Authorized User Information from Card ID
The GET /api/subProfiles/byPaymentCard endpoint retrieves information about the authorized user linked to a specified payment card. By providing a payment card ID as a query parameter, you receive a detailed profile of the authorized user associated with that card. This is useful for managing and auditing authorized user access within the banking application.
Endpoint
GET /api/subProfiles/byPaymentCard
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 you need to look up the authorized user (subprofile) tied to a specific payment card — for example, to verify who has access to a given card, to display authorized user details in a card management interface, or to audit card-to-user associations for business accounts.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| paymentCardId | string | Yes | The unique identifier of the payment card whose associated authorized user should be retrieved. |
Response
200 OK
| Field | Type | Description |
|---|---|---|
| givenName | string (nullable) | First name of the authorized user. |
| familyName | string (nullable) | Last name of the authorized user. |
| subProfileId | integer (int32) | Unique identifier of the subprofile (authorized user record). |
| string (nullable) | Email address of the authorized user. | |
| department | string (nullable) | Department the authorized user belongs to within the business. |
| nickName | string (nullable) | Nickname or display name assigned to the authorized user. |
{
"givenName": "Jane",
"familyName": "Smith",
"subProfileId": 10042,
"email": "[email protected]",
"department": "Finance",
"nickName": "J.Smith"
}Error Codes
| Code | When it happens |
|---|---|
| 400 | The paymentCardId is missing, empty, or in an invalid format. |
| 401 | Token missing, expired, or invalid. |
| 403 | The authenticated user does not have permission to view the subprofile for this card. |
| 404 | No authorized user or payment card found matching the provided paymentCardId. |
| 500 | Internal server error. |
Common Mistakes
- Omitting the
paymentCardIdquery parameter entirely — the endpoint requires it to identify which card's authorized user to return. - Passing a card ID belonging to a card not assigned to any subprofile — this will result in a 404 response.
- Using a token issued for a personal customer account; subprofiles are available for business customers only.
- Passing a physical or virtual card ID that belongs to the main account holder rather than an authorized user — only cards explicitly linked to a subprofile will return subprofile data.
Related Endpoints
GET /api/subProfiles— List all authorized users (subprofiles) for the authenticated business account.POST /api/subProfiles— Create a new authorized user for a business account.GET /api/subProfiles/{subProfileId}— Retrieve a specific authorized user by their subprofile ID.DELETE /api/subProfiles/{subProfileId}— Remove an authorized user from a business account.
Example
curl -X GET "https://api.banking.netevia.dev/api/subProfiles/byPaymentCard?paymentCardId=XXXX-XXXX-XXXX-XXXX" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"