> ## Documentation Index > Fetch the complete documentation index at: https://nextgen-docs.enfuce.com/llms.txt > Use this file to discover all available pages before exploring further. # List Eligible Token Requestors > Send a request to this endpoint to return a list of eligible token requestors (Samsung Pay and/order Click to Pay), as available for the specific card program. ## OpenAPI ````yaml json-files/wallet.openapi.json post /v1/wallet/mdestokenconnect/requestors openapi: 3.0.3 info: description: > Wallet API enables getting needed data for tokenization and enablement in programs like Apple Pay and Google Pay. #### Terms used
Term Definition
Customer End customer using financial institution's mobile application
In-app activation Wallet provisioning using financial institution app as authentication method
In-app provisioning Mastercard's term for push provisioning
Push provisioning VISA's term for pushing card details from within mobile application. This term will be used in this document
Wallet provider Such as Apple Pay, Google Pay or Samsung Pay
It's called in two cases: - *Push provisioning* - this is usually done within issuers own application and card holder does not need to enter any information. Then the different endpoints for push provisioning must be used. - *In-app activation* - activating a card by manually adding information, then endpoint for generate activation data must be used after authentication of end customer is completed. ![ Provisioning example ](https://enfuce-public-resources.s3.eu-central-1.amazonaws.com/public/wallet_push_prov.svg) In above case the difference between push provisioning and in-app activation is which endpoint that is called in step 3. Note that diagram above is a simplification of full flow in order to explain it from a developer point of view. version: '1' title: Wallet operations contact: name: Enfuce Financial Services url: https://enfuce.com email: info@enfuce.com x-logo: url: https://developer.enfuce.com/images/enfuce.svg altText: Enfuce logo servers: - url: https://api.{{tenant}}.ext-uat1-sandbox.mycore.enfuce.com/issuer description: UAT Sandbox - url: https://api.{{tenant}}.eu.live.prod.mycore.enfuce.com/issuer description: Production security: - bearerAuth: [] tags: - name: Push Provision - name: Activate token - name: Get tokens paths: /v1/wallet/mdestokenconnect/requestors: post: tags: - Eligible Token Requestors summary: | List Eligible Token Requestors description: > Send a request to this endpoint to return a list of eligible token requestors (Samsung Pay and/order Click to Pay), as available for the specific card program. operationId: getEligibleTokenRequestors parameters: - $ref: '#/components/parameters/x-audit-user' requestBody: required: false content: application/json: schema: $ref: '#/components/schemas/EligibleTokenRequestorsRequest' responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/EligibleTokenRequestorsResponse' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '500': $ref: '#/components/responses/InternalServerError' components: parameters: x-audit-user: in: header name: x-audit-user required: false description: Optional audit user header schema: type: string schemas: EligibleTokenRequestorsRequest: type: object properties: cardIds: type: array description: List of card IDs to filter the eligible token requestors. items: type: string format: uuid example: 20218aae-b15e-406c-9e9f-23735cd86a48 availablePushMethods: type: array description: > List of push methods supported by the token requestors — filters the token requestors that support at least one the methods sent in the request. Possible values are: * "ANDROID": The URI is an Android app intent. * "IOS": The URI is an iOS app intent. * "WEB": The URI is a browser URL. items: description: > The push method type corresponding to the URI supported by the token requestor. The array is absent if the token requestor does not support MDES Token Connect. Possible values are: * "ANDROID": The URI is an Android app intent. * "IOS": The URI is an iOS app intent. * "WEB": The URI is a browser URL. type: string enum: - ANDROID - IOS - WEB example: WEB EligibleTokenRequestorsResponse: type: object properties: tokenRequestors: type: array description: List of eligible Token Requestors. items: type: object properties: tokenRequestorId: type: string description: Unique identifier of the token requestor. example: '50123456789' name: type: string description: The legal name of the token requestor. example: Sunrise Ave. Ltd consumerFacingEntityName: type: string description: >- The name of the token requestor to be displayed to the account holder. example: Happy Sunrise Online tokenRequestorType: type: string enum: - MERCHANT - WALLET description: | The type of the token requestor. * MERCHANT: The Token Requestor is a merchant. * WALLET: The Token Requestor is a digital wallet or an ecommerce platform. example: MERCHANT walletId: type: string description: > The identifier of the digital wallet provider. Returned only when the token is provided to a digital wallet provider. example: '123' enabledAccountRanges: type: array minItems: 1 description: > Array of account range start numbers enabled for the token requestor. The start numbers will be 19 digits in length. items: type: integer format: int64 example: 5412346789000000000 programIds: type: array minItems: 1 description: > Array of programIds that are supported for the Token Requestor. Show the appropriate token requestors for the cards by matching the programIds. items: type: string format: uuid example: - 67fb672b-9148-4a80-8ccf-761e8bd308cb - f96584be-d56f-4ca1-9bfd-b708f6a32d25 supportsMultiplePushedCards: type: boolean description: > Indicates whether the token requestor supports addition of multiple cards in a single request. When supported, a maximum of 5 cards might be sent to the token requestor in a single request. example: true supportedAccountHolderData: type: array description: > Account holder's data that the token requestor accepts from the issuer for a specific card or an account. Possible values are: * `NAME`: The first name and last name of the account holder. * `ADDRESS`: The billing address for the account holder. * `EMAIL_ADDRESS`: The email address for the account holder. * `MOBILE_PHONE_NUMBER`: The mobile phone number for the account holder. items: type: string example: ADDRESS supportsCardHolderAuthentication: type: boolean description: > Indicates whether the token requestor supports cardholder authentication, after the token is activated. Possible values are: * `TRUE`: Post Tokenization Cardholder Authentication (Consent Service) is supported. * `FALSE`: Post Tokenization Cardholder Authentication (Consent Service) is not supported. example: true availablePushMethods: type: array description: | List of push methods supported by the token requestor. __Conditional.__ Required if the push operation was successful. Not present otherwise. items: $ref: '#/components/schemas/PushMethod' supportIssuerInitiatedDigitizationData: type: boolean description: > Indicates whether the token requestor supports issuer initiated digitisation (push provisioning). Possible values are: - `TRUE`: Supports issuer initiated digitisation. - `FALSE`: Does not support issuer initiated. example: false writeOnly: true mediaContents: type: array description: >- Contains all contents of the asset, including all variations. When the asset corresponds to a token requestor's logo, the logo is provided both in .svg as well as in .png format. items: type: object required: - type - data description: >- The content of the media. When the asset corresponds to a token requestor's logo, the content is a square image. properties: type: type: string description: > What type of media this is. __Max Length:__ 32. Specified as a MIME type, which will be one of the following supported types: * "application/pdf": for images (must be a vector PDF image) * "image/png": includes alpha channel * "image/svg+xml": image in SVG format * "text/plain" * "text/html" example: image/png data: type: string description: > The data for this item of media. Base64-encoded data, where the decoded data is in the format as specified in ‘type'. example: >- iVBORw0KGgoAAAANSUhEUgAAAXcAAAF3CAIAAADRopypAAAABGdBTUEAANbY1E9YMgAAAAlwSFlzAAAASAAAAEgARslrPgAAGtNJREFUeNrt3W9oW height: type: string format: int32 description: > For non-SVG image assets, the height of the image. Specified in pixels. __Max Length:__ 6. example: '192' width: type: string format: int32 description: > For non-SVG image assets, the width of the image. Specified in pixels. __Max Length:__ 6. example: '192' PushMethod: type: object required: - type - uri properties: type: type: string description: > The push method type corresponding to the URI supported by the Token Requestor. The array is absent if the Token Requestor does not support MDES Token Connect. __Max Length:__ 32 Possible values are: * "ANDROID": The URI is an Android app intent. * "IOS": The URI is an iOS app intent. * "WEB": The URI is a browser URL. enum: - ANDROID - IOS - WEB example: WEB uri: type: string description: > The token requestor's application or website URI. | _Note_: Refer to the Issuer Interface Implementation Guide for the detail of how to send the data to the Token Requestor. __Max Length:__ 128 example: http://www.tokenrequestor1.com/pushtoken ErrorResponse: type: object properties: type: description: The problem type. type: string title: description: The reason phrase of HttpStatus. type: string status: description: HTTP problem status. type: number detail: description: The problem detail. type: string instance: description: The request path. type: string id: description: Unique error identifier. type: string format: uuid timestamp: description: Date-time when error occurred. type: string format: date-time responses: Unauthorized: description: Unauthorized Forbidden: description: Forbidden content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' example: type: about:blank title: Forbidden status: 403 detail: Access Denied instance: /v1/cards id: 5cc541cb-f456-4331-b537-d2380fca0403 timestamp: '2026-02-24T12:34:56Z' InternalServerError: description: Internal server error content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' example: type: about:blank title: Internal Server Error status: 500 detail: Unexpected error occurred. instance: /v1/cards id: 5cc541cb-f456-4331-b537-d2380fca0500 timestamp: '2026-02-24T12:34:56Z' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ````