> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xpaycheckout.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment Method Token Deleted

> This event is triggered when a payment method token is deleted.

<ResponseExample>
  ```json theme={null}
  {
    "eventId": "whe_fooD944t4VUKkaDT",
    "eventType": "payment_method_token.deleted",
    "eventTime": 1729608043615,
    "pmId": "pmt_ftoeKIYGC3f43frT",
    "customerId": "cus_Tfd3Jq1tZxPjYVhRQW2r3",
    "paymentMethod": "CARD",
    "metadata": {
      "orderId": "12345",
      "customerNote": "Setup for recurring payments"
    }
  }
  ```
</ResponseExample>

<ResponseField name="eventId" type="string">
  A unique identifier for this specific event. This ensures that each event can
  be tracked and processed individually.
</ResponseField>

<ResponseField name="eventType" type="string">
  Describes the type of event. In this case, it signifies that a payment method token has been deleted.
</ResponseField>

<ResponseField name="eventTime" type="integer">
  The timestamp when the event was generated, typically in milliseconds since
  the Unix epoch (January 1, 1970). This value can be used to track when the
  event occurred.
</ResponseField>

<ResponseField name="pmId" type="string">
  A unique identifier for the specific payment method token that was deleted.
</ResponseField>

<ResponseField name="customerId" type="string">
  The unique identifier of the customer associated with this payment method token.
</ResponseField>

<ResponseField name="paymentMethod" type="string">
  The type of payment method that was deleted.
</ResponseField>

<ResponseField name="metadata" type="object">
  A collection of key-value pairs that were provided as `metadata` when the token was first created. These `metadata` values are echoed back in the response, allowing you to store and retrieve custom information such as context-specific attributes, references, or tags.
</ResponseField>