Versions Compared

Version Old Version 2 New Version 3
Changes made by

Danielle Chamberlain

Ernie Veniegas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: removed text about service not being available

...

Section


Column
width60%

Introduction

Info

The AMS portion of the account updater will run even if you are not using the service from Shift 4.  In this case the house cleaning aspects of the feature will function per usual, meaning expired tokens will be removed, and contacts booked in those cases.

 


At the time of writing this document Shift 4 is In January 2020, Shift 4 announced they were actively on-boarding new accounts, having previously reported in July of 2019 that they were in early beta with their credit card updater service with no current ETA on completion and roll out. (07/2019)

This service promises to reduce decline rates and labor costs for staff to contact customers to collect updated payment information.

Cards can be updated due to expiration date changes, or entirely new card numbers in the case of fraud where the card is replaced.

Please see below for details on the update process and what to expect.

Table of Contents

Table of Contents
excludeTable of Contents|Introduction


Column
width40%


Panel
titleArticles Referenced in this Article


Outgoing links
spacesDOC,HDHDZ,AMSU,GS
labels-cct,-zzz



Panel
titleArticles that Reference this Article


 
Incoming links
spacesDOC,HDHDZ,AMSU,GS


 Panel
titleCentral Table References

 Outgoing links
spacesDOC
labelscct,zzz
 
 




Tokens, their role in card updater
...
In this case, the Shift 4 response has supplied updated card information.  AMS stores this information and makes records a contact to the customer's profile. 

In the example below, we can see that this was the primary card on file, and the expiration date was updated.
The following Shift4 credit card token was found to be the customer's primary payment card and has been updated. 

Prior Token Info: Visa ending in ....6635
Token: 6635rnzvw6vexwp6    
Expiration Date: 02/21 

New Token Info: Visa ending in ....6635
Token: 6635wyq8qsv3t0rb    
Expiration Date: 02/23
...

In the example below, we can see the customer card number was updated.
The following Shift4 credit card token was found to be the customer's primary payment card and has been updated. 

Prior Token Info: MasterCard ending in ....7428
Token: 7428vpwbx99e5vjk    
Expiration Date: 05/19 

New Token Info: MasterCard ending in ....0570
Token: 0570dyw0t0vexjdm    
Expiration Date: 05/22
...

Case 3: The token is invalid/expired.
...
If Shift 4 responds that the token is invalid or expired, the card will be removed from the customer's account and a contact booked. 

In the example below, the card updater service returned that the token was invalid.  Looking more deeply into the customer's purchase history, we find that the customer used the card several months before in November.  So then, why was this token expired?  It has not been two years.  As it turns out when the card was used in November the expiration date was December of that same year.  When the updater service at Shift 4 ran the card was found to be expired, no new, updated expiration date was found, resulting in the token being invalidated.  The result in AMS is the card being removed and a contact being booked.
The following Shift4 token for the customer's Mastercard ending in ....7958 has been removed because it was invalid/expired.
79582gsg7k4dvpqg    
This was the customer's primary payment card. New payment information should be obtained from the customer prior to next purchase.
...

Auditing The Updater
Since the updater books contacts as a result of its work, we can use the customer contact screen in AMS to audit the weekly update runs.  This menu option is PSCUM.MCC, you may search for MCC or start the menu directly via the AMS Command Line
...