Temporary Lock the Card

Temporary Lock the Card

The Suspend Payment Card endpoint allows you to temporarily lock a payment card, immediately blocking all transactions on that card. The card's information is preserved so it can be reactivated at any time. This provides an instant security response for lost, misplaced, or potentially compromised cards.

Endpoint

POST /api/paymentCards/suspendPaymentCard

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 cardholder reports a card as lost, misplaced, or suspects unauthorized activity and wants to block transactions immediately without closing the card permanently. Because suspension is reversible, it is the preferred first response before escalating to card cancellation or reissuance. This is applicable to Physical, Virtual, and Burner card types for both business and personal customers.

Request Body

The request body accepts a paymentCardId as the minimum required field. All request variants extend the base paymentcardrequest schema.

Base request (minimum required)

Extended variant: with order reference

Extended variant: with nickname

Extended variant: with date period

Extended variant: reissue (legacy)

Extended variant: reissue (current)

orderPhysicalPaymentCard object

Minimum request example

{
  "paymentCardId": "card_abc123def456"
}

Request with suspension period

{
  "paymentCardId": "card_abc123def456",
  "dateFrom": "2026-06-08T00:00:00Z",
  "dateTo": "2026-06-15T23:59:59Z"
}

Response

200 OK

A successful response confirms the payment card has been suspended. The response body returns a success status.

{}

Note: A 200 status code confirms the suspension was applied. No additional payload fields are returned beyond the success indication.

Error Codes

Common Mistakes

• Providing a paymentCardId that belongs to a card already permanently closed — suspension only applies to active or previously active cards
• Omitting paymentCardId entirely, which is always required regardless of which request variant is used
• Sending an already-suspended card ID — check current card status before calling this endpoint to avoid redundant requests
• Using an expired Bearer token; tokens have a 10-minute lifetime and must be refreshed via POST /api/auth/refresh before they expire
• Setting dateFrom after dateTo in the date period variant, which will cause a validation error

Related Endpoints

• POST /api/paymentCards/activatePaymentCard — Reactivate a previously suspended payment card
• POST /api/paymentCards/cancelPaymentCard — Permanently cancel a payment card (irreversible)
• POST /api/paymentCards/reissuePaymentCard — Reissue a replacement payment card
• GET /api/paymentCards/getPaymentCard — Retrieve current status and details for a payment card

Example

curl -X POST https://api.banking.netevia.dev/api/paymentCards/suspendPaymentCard \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "paymentCardId": "card_abc123def456"
  }'