User Tools

Site Tools


faq:mercury_tokenization

This is an old revision of the document!


Mercury Tokenization

System Five Version 6.0.1.118 supports Mercury Tokenization along with US EMV and End-to-End Encryption.

What is Tokenization

Tokenization is where instead of storing a credit card number, a token is stored. Further transactions such as void, pre-auth capture, refund and sale can be performed by using only the token. The token can only be used on a single merchant account. If you have multiple merchant accounts a token from one department can not be used in another department. The token is not an encrypted credit card number. Tokenization means that card numbers are never stored on your system. Paired with End-To-End Encryption and EMV it provides the highest level of security for your customers.

Tokenization can be used with

  • Card not present transactions, ingenico 6xxx pin pads, MSR card swipes (dsiClientX). This method is still prone to skimming or hacking the MSR Device or computer.
  • Card present US PIN Pads vx810, Equinox L5300, mx915 (dsiPDCX). This method is still prone to skimming or hacking the MSR Device unless end-to-end encryption is utilized.
  • vx805 PIN Pads with End-to-to Encryption (dsiPDCX)
  • EMV PIN Pads vx805 (dsiEMVX)

Tokenization is not available with Canadian EMV vx810 pin pads (dsiEMVClientX).

Setup

To use Mercury Tokenization (MToken) you must contact Mercury Payments to have then enable Tokenization on your Merchant account, and you must turn on Tokenization in System Five, Payment Processing, Credit Cards, Use Tokenization.

In the toolbox, there is a routine to convert currently stored cards to tokens. This routine will blank out all current stored cards and replace them with tokens.

If you are currently not storing cards on file, switch over is easy.

faq/mercury_tokenization.1445970146.txt.gz · Last modified: 2015/10/27 11:22 (9 years ago) by craig