Unsuspend Banking Card
This endpoint lifts an existing suspension from a payment card, returning it to an active state so it can resume processing transactions. Use this after resolving the issue that originally triggered the suspension. The response confirms whether the action was successful and includes a change log of the operation.
Endpoint
POST /netevia/paymentCard/unsuspendPaymentCard
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 previously suspended card needs to be reactivated. This is typically called after a fraud investigation is resolved, a customer dispute is settled, or an administrative hold is lifted. Partners can call this to restore full card functionality for their customers without issuing a new card.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| paymentCardId | string | Yes | Unique identifier of the payment card to unsuspend. Minimum length: 1 character. |
| notes | string | No | Optional notes documenting the reason for unsuspending. Maximum 600 characters. |
| last4 | string | No | Last 4 digits of the card number, used as an additional verification check. |
{
"paymentCardId": "card_abc123xyz456",
"notes": "Fraud investigation resolved — card cleared for reactivation.",
"last4": "4321"
}Response
200 OK
The response is one of two schemas: boardingresponse (standard action result) or openfinancialaccountresponse (extends boarding response with a financial account ID).
| Field | Type | Description |
|---|---|---|
| profileId | integer (int32) | ID of the customer profile associated with the card. |
| errors | string | null | Error message if the action encountered a problem; null on success. |
| success | boolean | Indicates whether the unsuspend action completed successfully. |
| changeLog | array | null | List of change log entries recording the operations performed. |
| changeLog[].requestType | integer (int32) | Numeric code representing the type of banking request performed. |
| changeLog[].changes | string | null | Description of the specific changes applied during this request. |
| financialAccountId | string | null | (openfinancialaccountresponse only) Financial account ID linked to the card, if applicable. |
{
"profileId": 100234,
"errors": null,
"success": true,
"changeLog": [
{
"requestType": 5,
"changes": "Payment card unsuspended successfully."
}
]
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields (e.g., paymentCardId not provided) or validation error (e.g., notes exceed 600 characters) |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to manage this card or profile |
| 404 | Payment card not found for the given paymentCardId |
| 500 | Internal server error |
Common Mistakes
- Omitting
paymentCardId— this is the only required field and the request will fail with a 400 if absent. - Attempting to unsuspend a card that is not currently suspended — verify the card's status before calling this endpoint.
- Sending
noteslonger than 600 characters — truncate or summarize before submitting. - Using an expired Bearer token — tokens last 10 minutes; refresh via
POST /api/auth/refreshbefore calling.
Related Endpoints
POST /netevia/paymentCard/suspendPaymentCard— Suspend an active payment card.POST /netevia/paymentCard/closePaymentCard— Permanently close a payment card.POST /netevia/paymentCard/getPaymentCard— Retrieve current status and details of a payment card.POST /netevia/paymentCard/createPaymentCard— Issue a new payment card for a customer.
Example
curl -X POST https://api.banking.netevia.dev/netevia/paymentCard/unsuspendPaymentCard \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"paymentCardId": "card_abc123xyz456",
"notes": "Fraud investigation resolved — card cleared for reactivation.",
"last4": "4321"
}'