Step 2: Choose the OmniToken Format

Document created by lkilligrew on Aug 9, 2016
Version 1Show Document
  • View in full screen mode

At the core of enabling Vantiv’s mobile in-app integration is the generation and use of an OmniToken. OmniTokens offer a shorter “formed-preserved” reference to the cardholder’s credit card number with the actual card data being stored in Vantiv’s secure vault.  The advantages to this method of tokenization is that it allows for easy access to programs and features that were never possible before—including eProtect for eCommerce and Android Pay In-App.

 

For MercuryPay integrations, the OmniToken is used in place of MToken (RecordNo). One additional tag, <TokenType> is used in the transaction request.

 

Choose the OmniToken Format 

OmniTokens generated over the eProtect platform come in several different formats. When using them for MercuryPay, the MOD10+1 formats are preferable as they can be used to distinguish the first 6 and last 4 characters of the card number. We recommend using either of the 2 formats below:

  • Format T: Informative A1. Duplicates the length of the original PAN and preserves the first-six and last-four of the PAN. For example, if the original PAN is 14 characters long, the OmniToken will be 14 characters.
  • Format D: Minimum 16A 1. Length is 16 if the original PAN is 16 characters or less, but can be up to 19 characters if the original PAN is that length. For example, if the original PAN is 14 digits long, the OmniToken will be 16 characters; if the original PAN is 19 characters, the OmniToken will be 19 characters.

 

Next: Step 3: Process transactions through the MercuryPay Platform

Previous: Step 1: Integrate to Android Pay and eProtect

 

Return to Android in-app for MercuryPay

Attachments

    Outcomes