Skip to main content


Digitization includes all the subprocesses before the token will be successfully provisioned onto the device or to a merchant. Subprocesses include the generation, issuing, assurance and provisioning of the token. Token Service Providers (TSP) systems like Visa Token Service (VTS) or Mastercard Digital Enablement Service (MDES) play the central role in the digitization eco-system. It is their responsibility to generate, issue, store and de-tokenize tokens. It is also the Tokens Service Providers that connect the Token Requestors (Wallets/Merchants) with the Issuer. The Mea Token Platform (MTP) helps Issuers and Issuer processors to establish this connection with the Token Service Providers. The Mea Token Platforms enables the Issuers to handle the digitization process with one or more schemes using a single interface.

Digitization Overview

Generation and Issuing

Token generation and issuing is the responsibility of the token service provider. This process includes at least the creation of payment token, assignment of expiration date, link to the specific card PAN and issuing to the specific token requestor.

Assurance and Provisioning

Both MeaWallet and Issuer are involved in the provisioning process to make assurance that the selected card can be provisioned on to a specific third-party wallet or merchant and if additional identity and verification of cardholder is required. MeaWallet creates and maintains the rule engine that will determine the provision decision of the token. The issuer meanwhile is responsible for providing MeaWallet/scheme with updated card holder information and forwarding messages and codes that are needed to complete digitization.

MeaWallet relies on the Issuer to do a security check at the start of the provisioning process. Subsequent responsibility for provisioning decisions is taken care of by MeaWallet. The issuer’s responsibility is to forward information sent by MeaWallet/TSP, support different alternatives for cardholder verification and provide MeaWallet/TSP with cardholder information when required. Assurance is a generic term while each token service provider represents it differently. Technical implementation of issuer assurance in MTP I-TSP Pre-Digitization OBO API is Check Card Eligibility. For the process familiarity with the specifications of token service providers this guide will base on the provisioning terminology and as described in sections below. Term assurance will be omitted and not referred to later in this guide with the focus to the provisioning term as a more generic one outlining the assurance as a sub-processes.

Manual Provisioning

Manual provisioning is a standard process within the digitization of the card and enables contactless payments in third-party wallets. This process is handled by a third-party wallet and requires the consumer to enter the card details for the provisioning initiation.

Push Provisioning

Depending on the context and materials, Push provisioning can be referred to by the different terms as In-App Provisioning or Issuer-initiated provisioning.

This enables card provisioning from the issuer mobile app directly to the wallet. No additional consumer identification and verification is required because it is considered that the user is already securely authenticated into the issuer mobile app. Important to note that Push provisioning is mandatory by several third-party wallets. Push provisioning is not part of the I-TSP OBO product. However, MeaWallet provides Push Provisioning through the on-behalf service Mea Push Provisioning. Issuers will receive a MPP SDK that will be embedded in their mobile app. Refer to the Push Provisioning section in the mea development portal.