quackers
New member
I've got 18 swipers installed thus far across SS, Vac's and now 1 automatic. While testing the unitec retrofit kit with swiper we uncovered a large gap in functionality. I'm hoping somebody already found this and figured out a resolution as I spoke to Tom at Cryptopay and the answer does not make me happy. The ACW swiper you get with the auto cashier retrofit kits it is programmed to attempt the pre-auth for 13 seconds. If it doesn't get a pre-auth one would think that it should "decline" AND NOT START THE WASH. We found it operates almost in the exact same manner it would when your internet is down. Basically the swiper approves the card, starts the wash and the customer gets the wash for FREEEEEEEE. The real kicker is Cryptopay reporting does not post the "declines" back so we can see how many cards were actually declined therefore you have no way of knowing you are giving away free washes. To test this out I used a normal debit card which works fine. Then I used that fake test card sent with the worldpay materials which has mag strips but I never actually called and activated that card with worldpay. The swiper "approved" the card as a valid card and then let the wash start. I called Cryptopay and had Tom log into our site to check what happened at the swiper head and he could see the regular debit card transactions were fine, approved but the fake card did show a "decline". What this means is anyone who pulls up to your automatic who has a valid card with a number and a expiration date the swiper will basically approve and allow the customer to wash. Currently unitech has the option to "require pre-auth" which keeps this from happening. The system actually has to reach your processor and get an approval pre-auth on the card before Unitech will start the wash. If you look in the "expanded" configuration section of your ACW swiper in the configuration of your site on the Cryptopay website you'll see a setting there online for "require approval" but it's grayed out and you can't change that setting. When I asked Tom at Cryptopay about turning that on the answer was this is for vending and the code is not done yet. Also, he confirmed they don't post the "decline" transactions back anywhere that US, the customer, could identify the volume of bad cards we've approved and given away free washes for on out automatics.
This is a problem anytime your internet is down of course too for any swipers in SS, Vac or Auto and is touted as one of the "GREAT" benefits of Cryptopay in that you can keep processing CC’s while your internet is down up to 80 transactions per swiper head. That is fantastic if NONE of your customers are ever over their debit card limit or are using a maxed out CC for every card that is actually bad it never gets declined until the internet is back up and the swipers try to "process" those transactions fully with the processor (First Data originally and now Worldpay). When the bad transactions are declined there is ZERO RECORD of this that we are able to identify how many free washes were given out.
IMHO this is a massive functionality gap that needs to be closed quickly. Test your equipment and if you can sneak free washes through like we can then call Cryptopay and complain until they get the code completely done for pre-auth required. Each operator needs the option to turn it on or off based on their situation. I for one would prefer the customer get declined anytime their card is not fully approved, whether that means it took too long to get to the processor and timed out or whether that means the internet is down, in either case I DO NOT want to start the equipment and give away a free wash. I sure as heck don’t want my automatic auto cashier to start the wash without a full pre-auth approval either. The customer can use cash in these scenarios the same way they always have.
This is a problem anytime your internet is down of course too for any swipers in SS, Vac or Auto and is touted as one of the "GREAT" benefits of Cryptopay in that you can keep processing CC’s while your internet is down up to 80 transactions per swiper head. That is fantastic if NONE of your customers are ever over their debit card limit or are using a maxed out CC for every card that is actually bad it never gets declined until the internet is back up and the swipers try to "process" those transactions fully with the processor (First Data originally and now Worldpay). When the bad transactions are declined there is ZERO RECORD of this that we are able to identify how many free washes were given out.
IMHO this is a massive functionality gap that needs to be closed quickly. Test your equipment and if you can sneak free washes through like we can then call Cryptopay and complain until they get the code completely done for pre-auth required. Each operator needs the option to turn it on or off based on their situation. I for one would prefer the customer get declined anytime their card is not fully approved, whether that means it took too long to get to the processor and timed out or whether that means the internet is down, in either case I DO NOT want to start the equipment and give away a free wash. I sure as heck don’t want my automatic auto cashier to start the wash without a full pre-auth approval either. The customer can use cash in these scenarios the same way they always have.
