Payment Card Reissue

This endpoint reissues an existing payment card, generating a replacement card with a new expiration date. You can optionally carry over the original card number and PIN to the reissued card, and configure whether the card is activated immediately upon creation. Use this endpoint when a card is lost, damaged, or approaching expiration and needs to be replaced.

Deprecated: This endpoint is marked as deprecated. Check the latest API reference for the recommended replacement endpoint.

Endpoint

POST /api/paymentCards/reissuePaymentCard

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's payment card has been lost, damaged, or is expiring and a replacement card must be issued. This is applicable for both physical and virtual card types managed on the Netevia platform. If you need to preserve the existing card number (for continuity of recurring payments), set copyNumber to true.

Request Body

{
  "paymentCardId": "card_a1b2c3d4e5f6g7h8",
  "expirationDate": "2028-06-30T00:00:00Z",
  "activateOnCreate": true,
  "copyNumber": false,
  "copyPin": false
}

Response

200 OK

The response wraps the reissued card details along with a mutation result indicating any errors.

paymentCard object:

mutationResult object:

errors[] object (within paymentCard or mutationResult):

{
  "paymentCard": {
    "id": "card_z9y8x7w6v5u4t3s2",
    "last4": "XXXX",
    "bin": "411111",
    "status": "ACTIVE",
    "formFactor": "PHYSICAL",
    "network": "VISA",
    "expirationDate": "2028-06-30T00:00:00Z",
    "subProfileId": null,
    "name": "Jane Smith",
    "errors": null
  },
  "mutationResult": {
    "errors": null
  }
}

Error Codes

Common Mistakes

• Omitting expirationDate — this field is required; the request will fail with a 400 error if not provided.
• Providing a paymentCardId that belongs to a card not associated with the authenticated partner's customers, resulting in a 403 or 404 response.
• Supplying expirationDate in a non-ISO 8601 format (e.g., MM/YYYY instead of 2028-06-30T00:00:00Z), which causes a 400 validation error.
• Setting copyNumber: true without confirming that the original card's network and BIN support number portability for reissued cards.
• Expecting the original card to remain active after reissue — verify card lifecycle behavior and cancel or close the original card as needed.

Related Endpoints

• POST /api/paymentCards/createPaymentCard — Create a new payment card for a customer
• POST /api/paymentCards/activatePaymentCard — Activate a payment card that was created in an inactive state
• POST /api/paymentCards/cancelPaymentCard — Cancel or close an existing payment card
• GET /api/paymentCards/getPaymentCard — Retrieve details of a specific payment card

Example

curl -X POST https://api.banking.netevia.dev/api/paymentCards/reissuePaymentCard \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "paymentCardId": "card_a1b2c3d4e5f6g7h8",
    "expirationDate": "2028-06-30T00:00:00Z",
    "activateOnCreate": true,
    "copyNumber": false,
    "copyPin": false
  }'