# Shows checkout details

Endpoint: GET /checkout/{id}
Version: 2.0
Security: accountId, apiKey

## Path parameters:

  - `id` (string, required)
    Resource Identification

## Response 200 fields (application/json):

  - `status` (string)
    Enum: "failed", "success"

  - `message` (array)

  - `checkout` (object)

  - `checkout.id` (string)

  - `payment` (object)

  - `payment.methods` (array)
    Enum: "mb", "cc", "mbw", "dd", "vi", "ap", "gp", "sw"

  - `payment.type` (any)
    Enum: "single", "frequent", "subscription"

  - `payment.expiration_time` (string)

  - `payment.currency` (string)

  - `payment.key` (string)

  - `payment.max_value` (integer)

  - `payment.min_value` (integer)

  - `payment.unlimited_payments` (boolean)

  - `payment.frequency` (string)

  - `payment.max_captures` (integer)

  - `payment.start_time` (string)

  - `payment.failover` (boolean)

  - `payment.capture_now` (boolean)

  - `payment.retries` (integer)

  - `payment.notification` (object)
    Notification settings for payment methods.

  - `payment.notification.customer_method_instructions_email` (boolean)
    Specifies whether an email containing the payment instructions (e.g., Multibanco reference or Virtual IBAN details) should be sent to the customer's email address when the selected payment method is Multibanco or Virtual IBAN.
    Example: true

  - `value` (number)

## Response 401 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 403 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 404 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 429 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 500 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.