# Updated network token

Webhooks provide merchants with real-time notifications when the network token associated with a payment card is updated by Visa or Mastercard. These notifications allow merchants to automatically update their systems based on the events.
Duplicate webhook events can occur. Implement idempotency on your end to avoid processing the same event twice.

Endpoint: POST NetworkTokenUpdated
Version: 1.0.0
Security: merchant, signature

## Security:

  - `merchant` (unknown)
    apiKey in header merchant

  - `signature` (unknown)
    apiKey in header signature

## Header parameters:

  - `merchant` (string, required)

  - `signature` (string, required)

  - `solidgate-event-id` (string, required)
    Unique event identifier.

  - `solidgate-event-created-at` (string, required)
    Event creation time in UTC as <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601</a> with milliseconds.

  - `solidgate-event-type` (string, required)
    Event type, indicating the specific event that occurred.

## Request fields (application/json):

  - `card_id` (string)
    Unique card identifier provided by merchant in the payment request.

  - `tokenization_type` (string)
    Type of tokenization associated with the card, a process that replaces the card's primary account number (PAN) with a unique digital token to ensure secure transactions.
    Enum: "vts", "mdes", "scof"

  - `status` (string)
    Network token status.
    Enum: "INACTIVE", "ACTIVE", "SUSPENDED", "DEACTIVATED", "DELETED"

  - `created_at` (string)
    Network token creation date.

  - `updated_at` (string)
    Date of network token status update.

## Request examples:

  - `Updated network token` (unknown)

## Response 2XX:

  - `2XX` (unknown)
    Return any 2XX status to confirm successful data receipt