VisionCore How To
Home Search Support Forum Knowledge Base Print

TranSentry and Credit Card Tokenization

TranSentry (formerly MercuryShield), is a credit card processing module that sends and receives Credit Card transaction information. TranSentry only passes back non – sensitive transaction data including a Token reference number or the Record No which may be stored or discarded for recurring transactions. With Tokenization, companies can safely store a token (in place of the actual credit card information) which can be used to lookup the customer’s actual credit card information on Mercury’s secure servers.

 

1.Mercury Shield on the Company Preference is renamed to TranSentry.

TranSentry_Token1

 

2.In the Add-On Preferences, preference to enable (or disable) the tokenization is also added together with the options where users can select Token Frequency, One Time or Recurring.

TranSentry_Token2

 

One Time  - is good for “general merchandise”-like business where customers would need to show or say their credit card number every time they do their purchase. This type of company normally doesn’t need to know or track the credit card of their customers.

 

Recurring - is something we see for companies who have memberships, subscriptions, rental or repeat sales for the same set of customers. VisionCore can use a stored token to re-process the same credit card each time they transact with the same customers without asking for their credit card information again.

 

Info Take note that if a company will be processing some using One Time and some using Recurring, that company should select Recurring.

 

3.On the Enter Credit Card Amount screen, a new field was added called Account Number. This will display the stored token along with the last 4 digits of their credit card which can be reused to process a credit card.

TranSentry_Token3

 

4.If Tokenization is used in the Enter Credit Card Amount screen, the system will charge the CC amount using the token id stored in the database without showing the TranSentry screen. It will process the charge behind the scene using the token id.

 

5.When the Token Frequency is set to Recurring, the system will still store the token id generated when doing the credit card in the transaction table.

 

Example:

1.SI-10168 was charged with VISA worth $5. The token id generated this time is If99M5Lw5qhadDxorfzdzUOX9TK0XZjgIxAFEAAjEAAG9Q==. This means that the payment for SI-10168 will hold this token id and will be stored on a new record in Customer Token table.  The user will never actually see this token but we wanted to explain how the entire process works.

TranSentry_Token4

 

2.SI-10169 was charged with $2.00 using the token id from the first invoice. The token id generated this time is YFvlmec+9UElQS6Sg+WwNQViLYtcXwjnIxAFEAAjEAAG+Q== which means that the payment for SI-10169 will hold this token id. After this invoice is created, the token id for the first invoice that is stored in the Customer Token table will be replaced / updated with the token generated from the second invoice.

TranSentry_Token5

 

Info Note that POS transaction will still be using One Time frequency. There is a walk-in customer in POS that does not really need a recurring token.

 

6.All recurring Credit Card details will be displayed on the Customer form > Detail tab.

 

TranSentry_Token6

 

Additional Information:

1.All credit card transactions are voided using the token stored in the transaction level. If a token does not exist anywhere in the system and tokenization, the void will likely fail.

Example:

A credit card transaction is charged using One Time.

TranSentry_Token7

 

If the user changed the frequency to Recurring, the system uses the One Time token to void the credit transaction.

TranSentry_Token8

 

2.On the reverse scenario wherein the credit card transaction is posted as Recurring and the frequency has been changed to One Time, the credit card transaction is voided using the Recurring and the token stored in the transaction.

 

Example:

A credit card transaction is charged using Recurring.

TranSentry_Token9

 

If the user changed the frequency to One Time, the system uses the Recurring token to void the credit transaction.

TranSentry_Token10

 

3.Transactions posted with tokenization can be voided when the tokenization is still enabled. The system does not allow users to void a credit card transaction when the tokenization is disabled but the transaction was posted with tokenization enabled. The only way the user should be able to return the credit card amount to the customer is to do a return transaction.

Example:

A credit card transaction is charged with tokenization enabled.

TranSentry_Token11

 

If a user disables the tokenization, voiding of credit card will fail.

TranSentry_Token12

 

4.On the reverse scenario where user enables the tokenization and they attempt to void a transaction that is created from where the tokenization does not yet exist, voiding will fail.  Users can do a return transaction to avoid this error.

 

Example:

A credit card transaction is charged with tokenization disabled.

TranSentry_Token13

 

If a user enables the tokenization, voiding of credit card will fail.

TranSentry_Token14

 


Reference: Project 1183