Skip to main content
Enfuce, as a payment processing platform, has developed an integration with the MDES (Mastercard Digital Enablement Service) Token Connect; this enables your cardholders to enrol Mastercard branded cards to specific token requestors. The MDES Token Connect API endpoints enable direct card enrolment in digital wallets and with merchants through issuer-provided channels, such as mobile or web applications.
  • MDES Token Connect currently supports only Samsung Pay and Click to Pay.
  • In addition to enrolment of cards from the issuer provided channels, the cardholders can also add their cards to token requestors from digital wallets or specific merchants. For more information, see Pull Provisioning.

​
How the Integration Functions — Use Cases

We support the push provisioning method. Here is typical workflow that explains how the push provisioning method functions:

​
Push Provisioning

  1. The cardholder logs in to the issuer provided channel.
  2. The cardholder selects a card.
  3. Send a request to the List Eligible Token Requestors endpoint and include the cardId.
Enfuce processes the request and returns the eligible token requestors.
  1. The cardholder selects a token requestor from the list returned – if the specific token requestor allows, they can enrol a maximum of 5 cards in a single request.
  2. Send a request to the Push Cards to Token Requestors endpoint.
The card(s) is tokenised and added to the token requestor.
  1. You might redirect the customer to the specific URI returned in the response availablePushMethods.uri.
Once the tokenisation process is complete, the cardholder is redirected to the issuer provided channel.
We also support another method — pull provisioning. To know more about pull provisioning works, click Pull Provisioning.
  1. The cardholder logs in to a digital wallet/merchant application.
  2. The digital wallet/merchant application sends a request to Mastercard — getEligibleIssuerList endpoint.
    3. Mastercard returns a response, including the list of eligible issuers.
  3. The cardholder selects an issuer.
  4. The digital wallet/merchant application redirects the cardholder to the issuer’s application, including the following in the request:
    • tokenrequestorId (e.g. Samsung Pay ID)
    • tokenRequestorSessionId
    • Token Requestor App Callback URL (e.g. Samsung Pay URL)
  5. The cardholder selects a card – if the specific token requestor allows, they can enrol a maximum of 5 cards in a single request.
  6. Sends a request to the Push Cards to Token Requestors endpoint, including the following parameters:
    • tokenrequestorId (e.g. Samsung Pay ID) — forwarded the value as received from the digital wallet/merchant
    • callbackURL (Token Requestor App Callback URL)
    • tokenRequestorSessionId
    The card is tokenised and added to the digital wallet/merchant.
  7. You might redirect the customer to the digital wallet and/or the merchant, where the cardholder can check whether the card is successfully added or not.

Push Cards to Token Requestors

List Eligible Token Requestors