Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - SteveH

Pages: [1]
1
ezPower / Program Hang
« on: September 24, 2013, 05:36:41 AM »
We have had a number of ezpower program hangs recently. One just happened a few minutes ago right after running a credit card (Mercury). It appeared that the credit card transaction finished fine, printed the receipt, but ended with the screen going completely white - same background when bringing up the Sales Window and the pop-up box (Open Sales Window) is asking for a password though there was no pop-up box. Looking at the task manager, the ezpower program is running, no cpu usage, but not way to access anything in it either. I ended up ending the ezpower task and restarted it. The last transaction seems to have completed.

I know that isn't much to go on but do you have any ideas? We are running Version 13.480.

2
ezPower / Partial Credit Approval
« on: August 20, 2013, 07:46:29 AM »
A customer wants to pay with a credit card and for whatever reason, the authorization ends up being a partial approval. What do you do? Example: Charge goes in for $50. Credit is approved for $25. The customer has no money or another credit card to finish the sale. How can you close the sale? You can't void it because it isn't finished. The register is basically hung on this transaction!

Is there a way to disable a partial approvals? This is the root cause of the problem.

One of our cashiers ran into this the other day and ended up deleting the items in the sale (not sure how this is legal either since one of the items was partially paid for). Then rang up a new customer with a new item for cash and the original sale item was obliterated but the partial credit card charge was still in there. This all happened in a single register receipt number. The End of Day recorded the correct amount for cash sales (i.e. picked up the second item sold for cash) but was over by the partial credit card amount for credit card charges.

We use Mercury for CC processing and had to call them to get this straightened out - voiding the partial charge.

3
ezPower / Moving to a different register
« on: June 24, 2013, 05:13:09 AM »
Is there a way to move a cashier and cash drawer to a different register and transfer all the transactions with it? I'd like to be able to move a cashier around and still have the z-out accurate at the end of the day.

4
ezPower / Credit Card Processing
« on: January 30, 2013, 11:16:15 AM »
We've been using ezPower POS for years and love it. We've had the Credit Card processing enabled all along as well, first with PCCharge, then Mercury following the V13 upgrade. Today an email was sent around advertising ChargeItPro with ezPower. Could someone summarize what Credit Card options are available with ezPower today? My version current has configuration settings for:
  • Merchant Warehouse
  • Mercury
  • CIP - which I'll assume is ChargeItPro

Is ChargeItPro simply another option or is Mercury being phased out?

5
ezPower / Transaction zeroed out
« on: September 25, 2012, 04:23:19 PM »
I had a strange problem today. We have two cash registers running ezpower. One was over by $10 at the end of the day and it appeared to be because one transaction showed up as zero. I had the receipt with the receipt number and all looked well there ($10 charge, $20 given, $10 in change). But the receipt record when we reconciled the drawer showed zero (no charges).

Interesting also was the time stamp on the record in the sales window. The receipt showed 4:28pm while the record in the sales window showed 4:45pm and a different cashier (who was on the other cash register).

So what could cause this? I'm guessing that the other cashier somehow voided the sale. Would that update the time stamp on the sale and change the cashier name?

6
ezPower / Mercury Response Timeout
« on: May 30, 2011, 05:34:04 AM »
I think you must expose in ezPower the value for the Mercury Response Timeout. The default is 300 seconds which for us is way too long. It can handle values from 60-3900 seconds. We used to be able to get away with 120 seconds. It used to be exposed for the PCCharge interface.

7
ezPower / Mercury Processing Issue
« on: April 19, 2011, 07:22:39 AM »
We had a rather serious issue with a CC charge over the weekend. We made a hand keyed transaction which resulted in a pop-up window indicating an error "Error processing card: *AP" with a press ok button. My cashier pressed ok and tried the card again. A similar error was reported. The transaction did not appear to complete so we told the customer it was declined again and asked for a different card. The new card went through fine, receipts printed, and we were done. All of this happened in the context of the same POS transaction.

I then decided to go onto Mercury's site to see if I could tell what the AP* error meant and found that the first charge was voided, the second was processed, and so was the third. So we charged this customer twice - all on the same transaction. Again, the invoice number recorded for all three transactions was the same!

I spoke with Mercury about what was going on. They said that it appeared that the first transaction was accepted, the second one was processed as a duplicate (which results in automatically voiding the first transaction), and the third being on a different card went through as well.

Why did the first transaction appear on our end to be declined (*AP error). What is that and why would it result in a transaction going through but not registering as such with ezPower? The only card related details involved were that the woman said it was a new card but she had just used it successfully elsewhere. In the first attempt, we entered the billing zip code but did not enter it in the next two. Mercury claimed that the AVS passed with the zip we entered on the first attempt.


Pages: [1]