Update Payment Card Notification Settings for Subprofile

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

ParameterTypeRequiredDescription
PaymentCardIdstringYesUnique identifier of the payment card whose notification settings are being updated
SubProfileIdinteger (int32)YesUnique identifier of the subprofile (authorized user) associated with the payment card
IsEmailNotifybooleanNoSet to true to enable email notifications for card activity; false to disable
IsPushNotifybooleanNoSet 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

CodeWhen it happens
400Missing required fields (PaymentCardId or SubProfileId) or invalid parameter values
401Token missing, expired, or invalid
403Insufficient permissions — caller is not authorized to modify settings for this subprofile or card
404Specified PaymentCardId or SubProfileId not found
500Internal server error

Common Mistakes

  • Omitting PaymentCardId or SubProfileId — both are required query parameters; omitting either will result in a 400 error
  • Using a PaymentCardId that belongs to a different subprofile than the one specified by SubProfileId — 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 customer
  • POST /api/subProfiles — create a new subprofile (authorized user) for a business customer
  • PUT /api/subProfiles — update subprofile details and access level
  • POST /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"
Query Params
string
required
int32
required
boolean
boolean
Response
200

Success

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here!