---
title: "GET /setup-method/{setupMethodId}"
method: GET
path: "/setup-method/{setupMethodId}"
---

# GET /setup-method/{setupMethodId}

`GET /setup-method/{setupMethodId}`

Get details of a setup method

## Path parameters

- `setupMethodId` string, required

## Response `200`

Setup Method details retrieved successfully

- GetSetupMethodResponse
  - `setupMethodId` string — Unique identifier of the setup method
  - `customerId` string — The unique identifier for the customer, generated via the [create-customer API](/api-reference/customers/create-customer)
  - `currency` string — Three letter abbreviation of the currency
  - `paymentMethods` string[] — List of payment methods enabled for setup. 💡 If a selected payment method is unavailable, the system will automatically fallback to card payments to ensure a smooth checkout experience.
  - `storeFrontId` string — The unique identifier for your storefront
  - `callbackUrl` string — The URL we will callback to once the setup is complete
  - `metadata` object — A collection of key-value pairs that were provided when the object was created
  - `status` 'CREATED' | 'SUCCESS' | 'FAILED' — The status of the setup method
  - `pmId` string — Unique identifier of the payment method if setup is completed
  - `intentId` string — Unique identifier of the successful payment intent created while setting up the payment method token. Present only when `amount` is passed during setup creation.
  - `receiptId` string — Your identifier for the order. Present only when provided during setup method creation.

## Other responses

- `400` — Invalid request

---

[API](https://skmtc.net/xpaycheckout/apis/xpay-api-store.md) · [All operations](https://skmtc.net/xpaycheckout/apis/xpay-api-store/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/xpaycheckout/xpay-api-store/versions/6329a7c694bc/schema)