---
title: "Get eligible token requestors"
method: POST
path: "/v1/token-connect"
tags: ["MDES Token Connect [Beta]"]
---

# Get eligible token requestors

`POST /v1/token-connect`

Retrieve information about token requestors that have been enabled for one or more of the issuer's account ranges.

Pismo acts as a proxy for the <a href="https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/" target="_blank">Mastercard Token Connect API</a>

For more information, refer to the [MDES Token Connect](https://developers.pismo.io/pismo-docs/docs/mdes-token-connect) guide.

## Headers

- `access_token` string, required
- `x-tenant` string, required

## Request body

- TokenRequestorRequest
  - `accounts` string[], required — Account ranges to check for eligibility. The starting numbers are numeric strings between 9 and 19 in length. If the starting numbers are less than 19, MDES zero pads the starting numbers to 19 in length. The padded value must exactly match the account range start number enabled for the token requestor.

## Response `200`

Successful response

- TokenRequestorResponse
  - `token_requestors` TokenRequestor[]
    - `token_requestor_id` string, required — Token requestor ID (TRID), a numeric 11-digit value. A token requestor is an entity that initiates the tokenization process. Wallets, merchants, payments service providers (PSPs) are collectively referred to as **token requestors**. Card networks use TRIDs to enforce usage boundaries at the network level, know who is reponsible if fraud occurs, and to prevent tokens from being used elsewhere.
    - `name` string, required — Token requestor legal name
    - `consumer_facing_entity_name` string, required — Consumer facing entity name. Token requestor display name.
    - `token_requestor_type` 'MERCHANT' | 'WALLET', required — Token requestor type * `MERCHANT` - Merchant token requestor. For example - Netflix, Uber, Amazon, and so on. * `WALLET`- Wallet or commerce platform token requestor. For example - Apple Pay, Google Wallet, Samsung Pay, and so on.
    - `enabled_account_ranges` integer[], required — Array of account range start numbers enabled for token requestor. The start numbers are 19 digits in length.
    - `image_asset_id` string — Token requestor image (for instance a logo) asset ID. Call the [Get asset](https://developers.pismo.io/pismo-docs/reference/token_connect_get_asset) endpoint to retrieve the image.
    - `wallet_id` string — Wallet provider ID. Returned if token requestor is a wallet like Google Pay or Samsung Pay.
    - `supported_push_methods` string[] — Web-to-web or app-to-web push methods token requestor supports. Not returned if the token requestor does not participate in the MDES Token Connect program.
    - `supports_multiple_pushed_cards` boolean — Does token requestor support up to 5 push account receipts in a single request? Present if the token requestor participates in MDES Token Connect program.
    - `supported_account_holder_data` string[] — Account holder data elements the token requestor expects to receive from the issuer with a pushed card or account. Only returned if the token requestor participates in MDES Token Connect. If the token requestor participates but doesn't accept account holder data, then an empty array is returned. To ensure forward-compatibility, all API client implementations must be resilient to new data element values being added to responses from MDES. * `NAME` - Account holder first and last name * `ADDRESS` - Account holder billing address * `EMAIL_ADDRESS` - Account holder email address * `MOBILE_PHONE_NUMBER` - Account holder mobile phone number
    - `supports_card_holder_authentication` boolean — Does token requestor support cardholder authentication after the token is activated?
    - `supports_token_connect` boolean — Does token requestor support Token Connect?
    - `available_push_methods` PushMethod[] — Available push methods
      - `type` 'ANDROID' | 'IOS' | 'WEB', required — Push method type * `ANDROID` - Android app intent URI * `IOS` - iOS app intent URI * `WEB` - Browser URL
      - `uri` string, uri, required — URI to open the token requestor's application or website.
    - `support_issuer_initiated_digitization_data` boolean — Does token requestor support Issuer Initiated Digitization Data?

## Other responses

- `400` — Bad request
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/versions/935b62e16de4/schema)