Digitization includes all the subprocesses before the token will be successfully provisioned onto the device on to a merchant. Subprocesses include the generation, issuing, assurance and provisioning of the token. Complete digitization process is built around the Token Service Provider systems like Visa Token Service or Mastercard Digital Enablement Service. Token Service Provider serve to be the central part of the digitization eco-system that generate, issues, store and de-tokenize tokens and unite together all involved parties as payment systems, third-party wallets or merchants who act as a Token Requesters and Issuers who make the final decision on the token provisioning.
The Mea Token Platform helps issuers and issuer processors to handle the provisioning process with one or more schemes using a single interface.
Generation and Issuing
Token generation and issuing is the responsibility of the token service provider. This process includes at least the creation of payment tokens, assigment of expiration date, link to the specific card PAN and issuing to the specific token requestor.
Assurance and Provisioning
Issuer is involved in the provisioning process to make assurance that the selected card can be provisioned on to a specific third-party wallet or to a merchant and if additional identity and verification of cardholder is required then it is also maintained by the issuer.
Issuers control the provisioning by the means of assurance process that include verification of token authentication request and optional additional identification and verification of the cardholder. Assurance is a generic term while each token service provider represent it differently. Technical implementation of issuer assurance in MTP I-TSP Pre-Digitization API are Authorize Service and Request Activation Methods requests. 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 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 is a standard process within the digitization of the card and enables contactless payments in third-party wallet. This process is handled by a third-party wallet and requires the consumer to enter the card details for the provisioning initiation.
Depending on the context and materials, Push provisioning can be referred to 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.
Issuers, while approving the token authentication request, must review if this request is initiated from the issuer mobile app and then do not request additional identification and verification of the consumer.
Therefore it is considered that push provisioning passes through without the additional verification(green flow), there still may be the use cases when token service providers or third-party wallets report on the suspicious behaviour pattern. In such cases, issuers must review the recommendations and when requesting additional identification and verification of the consumer then the option with the issuer mobile app must be excluded from the set of available activation methods.