Our Technology

 
 
Authentication Technology

Using 'MSL Wallet' is as easy as 1, 2, 3 and can be used for all sensitive and non-sensitive transactions.

To protect sensitive infomation, 'MSL Wallet' uses Authentication instead of Verification. Please see the details below about Authentication VS Verification.



  • Consumer scans/enters MSL Code, displayed by Merchants, with or without finger print authentication to receive a single-use random number. The random number can be fully generated by MSL Wallet or partically filled by the Consumer with their PIN.
  • Consumer hands over the random number to the Merchant or MSL Wallet electronically sends it to the Merchant.
  • Merchant submits the request to process the transaction.
    • Note:
    • Merchant can use Credit Card terminals, Point of Sales systems, MySingleLink Virtual Terminals, Web Sites, Customer Help Centers etc.
 
MySingleLink has developed many applications using Authentication method based on US Patents* issued to MySingleLink and Pending Patents for impeccable security. Authenrication method replaces vulnerable Verification method in protecting secured resources such as Credit/Debit Card, Bank Account, User Account, Lockers, Merchandise etc.

To know more about MySinglLink applications, pleast select all or individual application under the drop down menu "Products & Services".

*8,505,079 - 8,533,802 - 8,566,957 - 8,695,071 - 8,713,656 - 8,800,014 - 9,112,847 - 9,584,499.
 
Authentication VS Verification:

MySingleLink has developed many applications using Authentication method which replaces vulnerable Verification method in protecting secured resources such as Credit/Debit Card, Bank Account, User Account, Lockers, Merchandise etc.

Consumers need to save their sensitive information such as Credit/Debit Card, Bank Account, User Account, Lockers etc., in a only once and can be used with any Merchant, without the Merchants getting any sensitive information.

Once a sensitive information such as Credit/Debit Card, Bank Account, User Account, Lockers etc., is saved successfully in a PCI compliant gateway, the same sensitive information cannot be used by any other Consumer. However, Consumers can authorize other mobile devices use the sensitive information.

Since, Authentication does not accept and does not transmit any sensitive information, Consumers can use any network including unsecured public networks for any transaction, except when secured resources information are added or edited.

Since, MySingleLink does not save any sensitive information, hackers do not have any incentive to hack MySingleLink.

Since Authentication is hack free, Merchants can use 'Bring Your Own Device' (BYOD) method along with Lockers to accept orders eliminating counters, kiosks.

Since sensitive Credit/Debit Card information is never handled by Merchants and never transmitted, Merchants can reduce PCI Compliance scope drastically.

All the applications developed by MySingleLink are available for Merchants thru our Virtual Terminals 'https://vt.mysinglelink.com' and thru our mobile apps 'MSL Wallet' and 'MSL POS'. The mobile apps are available for free for iPhone, iPad and Android devices.

For custom development, Application Programming Interface (API) and Software Development Kit (SDK) provided by MySingleLink are available for Developers.

For additional information on our APIs and SDKs, please contact us at (210) 494 5465 and/or info@mysinglelink.com or click here.
 

Authentication

Verification

   
Here is how it works:
While holding a finger on the finger print reader, Consumer Scans a QR Code knwon as 'MSL Code' that is specific for a Merchant, specific for a transaction and specific for an amount (in case of sales transaction) displayed by merchants. In response, Merchants would Scan or receive thru an API or thru a SDK a Code known as 'Single Use Digital Signature' (SUDS) from Consumers. SUDS would be valid only for a short period of time. The transaction will be executed only, if authentication is successful.

Here is how it works:
Consumers hand over sensitive information such as Credit/Debit card number, Bank account number, user id, password, email, mobile number to Merchants and/or associates. Merchants would transmit the sensitive information over internet using a hardware that may be vulnerable for hacking. Consumers may be using the same sensitive information with many other Merchants.
Authentication Authenticates the rightful owner of any secured resource that can be used only by a specific merchant, for a specific transaction, for a specific amount (if transaction involves payment) and can authenticcate only for a brief time.

Verification method relies on user id and password attached to secured resources, does not verify the rightful owner of any secured resource, and not specific for any merchant, for any transaction, for any amount and always valid as along as the secured resource is available.

Authentication method is impeccable, because it does not rely on user id or password and hackers cannot use phishing or impersonization or malware or any other technique to gain access to secured resources thru stolen user id and password.

Verificcation method is vulnerable, because it solely relies on user id and/or password and hackers can use phishing or impersonization or malware or other techniques to gain access to secured resources thru stolen user id and password.

Authentication method is independent and does not make other Merchants, using the same secured resources, vulnerable.

Verification method can use the same user id and password with any number of Merchants, becasue it is impossible for Consumers to use unique user id and password with each Merchant. So, a single hack can affect all Merchants. A few examples of major hacking, occurred in the last 12 months, are Marriott, T-Mobile, Quora, Google Orbitz, Facebook and Equifax. All of them relied on Verification method to protect secured resources.

Log-In example without user id and password:

Log-In example with user id and password:



Flow diagram may change from application to application, but following is a general flow diagram for one of the Payment applications using a gateway.