> ## 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.

# Checkout Opened

> This event is triggered when a payment intent's checkout page is opened by a customer.

<ResponseExample>
  ```json theme={null}
  {
    "eventId": "whe_fooD944t4VUKkaDT",
    "eventType": "intent.checkout_opened",
    "eventTime": 1729608043615,
    "intentId": "in_fooBOwYsaK50AEfK",
    "receiptId": "recp_123311",
    "metadata": { 
      "orderId": "12345",
      "customerNote": "Deliver after 5 PM" 
    }
  }
  ```
</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
  intent's checkout page has been opened.
</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="intentId" type="string">
  A unique identifier for the specific payment intent whose checkout page was
  opened.
</ResponseField>

<ResponseField name="receiptId" type="string">
  Your identifier of the order.
</ResponseField>

<ResponseField name="metadata" type="object">
  A collection of key-value pairs that were provided when the object was
  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. This can be useful for correlating records in your system
  or attaching meaningful context to transactions.
</ResponseField>