1. Home
  2. Point-Of-Sale Software
  3. duplicate visa authorizations

duplicate visa authorizations

I use RMS with Mercury Payment System. After seeing a chargeback on my bank account, I did some research and found that RMS somehow authorized a credit card three times instead of once.

I know this was not the cashier error, because I can see the 3 transactions in the dbo_VisaNetAuthorization table, but the affected credit card only shows up once in dbo_tenderentry. Also, there is ony one transaction in dbo_transaction.

Has anyone else heard of or experienced this? I have instructed my staff to always double check the credit card batch amount under Settle EDC Batch against the day's X reports, because I would assume that if this happens again, it would show up there, but I am not sure.

I am concerned that this will continue to happen, and I won't know until I get more chargebacks, which cost a lot of money.

Reply to
Julie
Loading thread data ...

Julie,

Reply to
aaron kessler

Reply to
Julie

Julie,

Reply to
aaron kessler

Julie,

I had this happen to me this year too, but mine was through PCCharge through Paymentech. It was a nightmare, we quickly switched back to Vital (Visanet) which is the preferred system for RMS. We have never had an issue with Vital....ever and we have been using them since 2003. I will never again be talked into switching away from them.

Also for us RMS was not the cause of the problem, it was a communication error going over the internet to/from Paymentech for authorization. The authorization code was getting lost and the transaction would not complete. When this happens the employee would swipe the card again thus the duplication occurs, RMS gets satisfied and Paymentech gets two duplicate transactions to process.

Hope this helps in your inquiry with Mercury.

Grier

"Julie" wrote:

Reply to
Grier

Julie, Grier,

We have had similar issues & I've been back and forth with RMS Tech Support for about 6 months now. We also use TSYS (nee Vital) and PaymentTech. We thought for a while it was an error during the authorization until most recently, when it happened with a check tender. Currently our prime suspect is a 3rd-party html status bar.

Are you running the POS application as a "limited" or an "admin" user type?

-Dave

"Grier" wrote:

Reply to
davem

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.