Update email and push notification preferences for a payment card associated with a business subprofile.
Update Payment Card Notification Settings for Subprofile
This endpoint allows a primary business user to update notification settings for a payment card linked to a specific subprofile (authorized user). Notification preferences include email alerts and push notifications for card-related activity. Changes take effect immediately and apply only to the specified subprofile and payment card combination.
Endpoint
POST /api/subProfiles/PaymentCard
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 a business customer or their primary account holder needs to configure how a subprofile receives alerts for a specific payment card. This is useful for managing notification preferences per authorized user — for example, enabling push notifications for a limited-access employee card while disabling email alerts. This endpoint is relevant only for business customers who have existing subprofiles with assigned payment cards.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| PaymentCardId | string | Yes | Unique identifier of the payment card whose notification settings are being updated |
| SubProfileId | integer (int32) | Yes | Unique identifier of the subprofile (authorized user) associated with the payment card |
| IsEmailNotify | boolean | No | Set to true to enable email notifications for card activity; false to disable |
| IsPushNotify | boolean | No | Set to true to enable push notifications for card activity; false to disable |
Response
200 OK
A successful response confirms that the notification settings have been updated. No response body fields are returned.
{}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields (PaymentCardId or SubProfileId) or invalid parameter values |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions — caller is not authorized to modify settings for this subprofile or card |
| 404 | Specified PaymentCardId or SubProfileId not found |
| 500 | Internal server error |
Common Mistakes
- Omitting
PaymentCardIdorSubProfileId— both are required query parameters; omitting either will result in a 400 error - Using a
PaymentCardIdthat belongs to a different subprofile than the one specified bySubProfileId— the card and subprofile must be associated - Passing string values (e.g.,
"true"as a quoted string in a JSON body) instead of proper boolean query parameters (true/false) - Attempting to use this endpoint for personal customer accounts — subprofiles and their payment card notification settings apply to business customers only
Related Endpoints
GET /api/subProfiles— retrieve a list of subprofiles for a business customerPOST /api/subProfiles— create a new subprofile (authorized user) for a business customerPUT /api/subProfiles— update subprofile details and access levelPOST /api/paymentCards— issue a new payment card for a subprofile
Example
curl -X POST "https://api.banking.netevia.dev/api/subProfiles/PaymentCard?PaymentCardId=XXXX-XXXX-XXXX-XXXX&SubProfileId=1042&IsEmailNotify=true&IsPushNotify=false" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" 200Success
