| Volume 78, Issue 1 - Page 2 | Payment Processing News from Shift4 Corporation | November 2005 |
|---|
|
The Token spans the lifetime of the transaction, even into history, so it provides all the same support for tips, tabs and incremental authorizations. Basically, the Token is stored on the POS system and when an incremental authorization is required on the card the Token is sent to Shift4. The Token represents a specific credit card transaction and card data that is stored in Shift4's data center. When the Token is sent through, Shift4 translates that Token into the card data and sends it to the processor. The processor sends back the authorization code; Shift4 turns it back into a Token and sends that along with the approval code to the merchants.The authorization goes through and again no credit card data is stored on the system. That means that the merchant doesn't need the card number or data past the initial request, so there is absolutely no reason to store this potentially dangerous information. The entire liability to protect the card data is now on the gateway, where it should be. Implementing Tokenization is truly a small change with big results. Adding on Shift4 Tokenization requires a small change on the POS and PMS side. You need to add an addendum asking for this block and, of course, you need to store the Token. But even this part is easy. The Token can be stored in the now empty card number field, which is already setup to receive this type of data. Also, because the Token includes the last four digits of the credit card number, all of your system reports will still be fully functional. From a merchant's point of view, the implementation is seamless. In fact, it can be implemented even when there are pending sales or open tickets remaining. Best of all, the solution is available today and at no additional cost. To find out more about Tokenization, please contact sales@shift4.com . CREDIT CARD 101 American Express CAPN |
As a processor for American Express, Shift4 has already engaged American Express regarding the required changes and has a project plan in place. We should have the changes completed no later than 1st Quarter 2006. For your merchants who accept American Express and utilize $ $ $ ON THE NET, no change is required by you or them. The update will be seamless and complete. For any customers you have going direct or through another gateway, you will want to contact American Express about the changes and new specifications so that you can reprogram your system directly. NEW FEATURE Stop Those Duplicates Now in the View Options menu merchants can turn on the Duplicates Only view. This will display all transactions in the batch containing the same card number.
With this view, it is easy to identify a potential problem. We can see one instance, the $200.34 transaction, which definitely appears to have been duplicated and needs to be corrected. The other case, however, could represent a consumer making two separate transactions on the same day for different product/services. Just because the card was used more than once doesn't mean it is a duplicate. The merchant will need to know whether these additional charges to that card are valid or not. When they are done reviewing their duplicate transactions, they simply go back to the View Options and turn off this selection so they can see the full batch again and submit it for settlement. |
|
|
|
| Page 1 2 3 | Printer Friendly Version |
Acceptance and Processing Network (CAPN) specifications. Basically, what the letter addresses is that American Express is in the process of altering their authorization and settlement specifications. The letter states that if a system is not compliant with the CAPN specs by October 31, 2006 than there will be an out-of-compliance fee of 25 cents added per transaction. 