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

# Setup Method Checkout Opened

> This event is triggered when a setup method's checkout page is opened by a customer.

<ResponseExample>
  ```json theme={null}
  {
    "eventId": "whe_fooD944t4VUKkaDT",
    "eventType": "setup_method.checkout_opened",
    "eventTime": 1729608043615,
    "setupMethodId": "sm_sK8d3Jq1tZxPjYVhRQW2rf",
    "receiptId": "order123",
    "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 setup method'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="setupMethodId" type="string">
  A unique identifier for the specific setup method whose checkout page was opened.
</ResponseField>

<ResponseField name="receiptId" type="string">
  Your identifier for the order. Present only when provided during setup method creation.
</ResponseField>

<ResponseField name="metadata" type="object">
  A collection of key-value pairs that were provided when the setup method 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.
</ResponseField>