KashierDevelopersKashier Developers

List saved card tokens

curl -X GET "https://test-api.kashier.io/v3/payment/tokenization/tokens?page=1&limit=20"
{  "message": "success",  "data": [    {      "cardHolderName": "Hegab",      "token": "a559ecc6-11a2-431a-b40c-c10df4e7a9df",      "agreementId": "65d4717c2b2c17002469e463",      "customerReference": "12345",      "agreementType": "UNSCHEDULED",      "agreementExpiry": "N/A",      "cardNumber": "5123********2346"    },    {      "cardHolderName": "TEST",      "token": "c34faed2-b1e3-4ebf-99ab-992ef2f70d61",      "agreementId": "66043d39ec69ad0024b9c012",      "customerReference": "123456",      "agreementType": "RECURRING",      "agreementExpiry": "2024-11-14T15:47:29.448Z",      "cardNumber": "5078********5581"    }  ],  "pagination": {    "total": 2,    "limit": 20,    "page": 1,    "pages": 1  }}

Lists every card token saved on your merchant account, with the agreement each one was saved under.

This is the account-wide view, and it is a different endpoint from the customer-scoped GET /v3/cards/customer read on the checkout host: this one lives on the dashboard host and authenticates with your secret key in Authorization, with no Kashier-Hash. Reach for it to audit or reconcile what you hold on file; reach for the customer read when you are rendering someone's saved cards at checkout.

Card numbers come back masked. There is no way to retrieve a full PAN from Kashier.

Authorization

secretKey
Authorization<token>

Merchant secret key used to identify the merchant, obtained from Kashier's dashboard. Pass the raw secret key value in the Authorization header (NOT a "Bearer" token).

In: header

Query Parameters

page?integer

Current page number.

limit?integer

Number of tokens per page.

sortType?integer

Sort direction — -1 newest first, 1 oldest first.

Value in

  • 1
  • -1

Response Body

application/json

application/json

application/json

application/json

application/json

GET
/v3/payment/tokenization/tokens