| Volume 8, Issue 1 - Page 3 | Payment Processing News from Shift4 Corporation | November 2005 |
|---|
|
Because it isn't always obvious that you may have a problem hidden deep within a batch, or you don't have duplicates often enough to warrant checking on them each time you submit a batch, the system can be configured to do this for you and alert you to potential problems. This is handled during the Batch Pre-Scan and controlled by the setting in Account Settings . Account Settings can only be accessed by your Account Administrator, remember this is the username 'admin' or 'administrator'. When you log in as this user you will have an Account option in the menu at the top of the screen, under it you can select Account Settings . On this screen you will see a drop down box for Possible Duplicates the choices are: Disable - If you select Disable then $ $ $ ON THE NET will not scan your batch for potential duplicate transactions. If you would normally expect to see a credit card used multiple times in the same batch for multiple transactions, then you might consider using Disable. Silent - In Silent mode, the batch will close and process as normal. Nothing would be presented on the screen to the user closing the batch alerting him/her that there are potential duplicate transactions in that batch. But, behind the scenes $ $ $ ON THE NET will send an e-mail out to all of the individuals on the "Fraud Sentry Notifications" list alerting them to the presence of the potentially duplicated transactions. Verbose - Verbose mode will stop the user during batch settlement and let them know that it has identified a potential duplicate transaction. This is done at the same time that it normally identifies un-verified credits. You can see an example of the screen below. The user is then prompted to enter the password to confirm that they are aware of the potential duplicate transactions, have reviewed the transactions and that they want to submit the batch as it is. This is the default setting. Disallow - With Disallow, there is no ability to close a batch that contains potential duplicate transactions. While this may seem like a good safety measure, it could cause problems for you if you can't submit a batch because the system is alerting on a potential duplicate that really isn't a problem. Again, not all potential duplicate transactions are problems, there are valid reasons that you may have the same card used for more than one sale in a given batch. If you have any additional questions about this feature, or any other uses of $ $ $ ON THE NET, please feel free to call our 24 hour support center where your questions can be immediately answered. |
TOOL HIGHLIGHT $ $ $ ON THE NET Aging Notification $ $ $ ON THE NET has a built in "alarm clock" that will remind you or your staff to settle transactions and prevent those downgrades. We call this system Aging Warning , and it can be set up in the Account Configuration page when you're logged in as the Administrator. TIP : Occasionally auditors will get in the habit of just looking at transactions for a specific day. Yet, there are times when your batch can have transactions from previous days, so we recommend that, when selecting your business date, you choose " All transactions though the selected date " so the system will pick up all of the transactions you've run that haven't been sent to the processor. If you are getting aging warnings and don't see any transactions that haven't been sent to the processor yet, it may be because of the business date selected. Again, please set the business date to the current date and make sure you choose " All transactions though the selected date ". The screenshot below shows which button we recommend using. As always, if you have any questions or concerns, please don't hesitate to send an email to our Account Management team at myaccount@shift4.com .
The Shift4Word is edited by Randy Carr, Director of Marketing for the Shift4 Corporation. She can be reached by email at rcarr@shift4.com or by calling (702) 597-2480, ext. 3419.
|
|
|
|
| Page 1 2 3 | Printer Friendly Version |
