---
title: "GET /customer/{customerId}/payment-method-tokens"
method: GET
path: "/customer/{customerId}/payment-method-tokens"
---

# GET /customer/{customerId}/payment-method-tokens

`GET /customer/{customerId}/payment-method-tokens`

Retrieve a list of payment method tokens for a customer created within a specific time range, with support for filtering and pagination. This endpoint allows you to track and analyse all payment method tokens for a customer. It's useful for building dashboards, reconciling payment methods, or reviewing saved payment methods programmatically.

## Path parameters

- `customerId` string, required

## Query parameters

- `startTime` integer
- `endTime` integer
- `limit` integer
- `offset` string
- `status` string

## Response `200`

- GetPaymentMethodTokensForCustomerResponse — Response containing a list of payment method tokens for a customer
  - `data` GetPaymentMethodTokenResponse[], required — List of payment method tokens, could be empty if no payment method tokens are found for the customer
    - `paymentMethodId` string, required — Unique identifier of the payment method
    - `paymentMethod` string, required — Type of payment method
    - `customerId` string, required — The unique identifier for the customer, generated via the [create-customer API](/api-reference/customers/create-customer)
    - `status` 'LIVE' | 'DELETED', required — Status of the payment method token. Please refer to payment method token [status](/products/setup-method/overview#payment-method-token-lifecycle) for more details.
    - `createdAt` integer, required — Epoch timestamp in milliseconds of when the payment method token was created
  - `metadata` object, required
    - `offset` string — Pagination cursor for fetching the next page of results. Use this exact string as the `offset` parameter in your next API request. When this field is missing or null, you've reached the end of the results. For detailed pagination implementation guide, see [Pagination Guide](/developer-resources/pagination).

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