Yeah after configuring it a couple of times I figured out what it does, but there is so much it can do, you sometimes just don’t know where to start.
Also I used the Fast Cash Payment button that automatically created the fast cash button for me. In the Fast Cash rule though, it has a ‘Execute Automation Command’ in actions which is linked to ‘ACM Close Settled Ticket’. Should I keep this as is or remove it?
From the configuration task?
Either adapt that or remove and start fresh, up to you.
I think If I did it fresh it would make me understand on how a few things work. However I think also if I can learn to adapt, then I can save time? In this case, I’m trying to adapt it. Lets see how it goes haha. Thanks @JTRTech
Alright I tried to implement that number pad with the fast cash button, but it still seems to be just closing it rather than opening the number pad?
You haven’t put the constraint on the fast payment rule to trigger it on the button press.
Look at another rule like the print bill automation command rule and yourll see what I mean.
Looks good.
Is the rule from the configuration task still there?
That is the rule from the configuration task. I just removed the extra action that was there. However after putting that constraint. I press the button and it still just immediately prints and closes ticket without number pad. Weird
Its not weird at all 
numberpad is empty…
Have you turned of the keypad?
Unless you type something in the keypad {:NUMBERPAD} == ’ ’ so it is firing the {TICKET TOTAL} action
Hahaha Oops, I just realised I was supposed to press something on the keypad before it actually fires it just like you said. its 5am in the morning, my brain is fried haha. thanks man
Just noticed, you might want to change {TICKET TOTAL} to {REMAINING TOTAL} or {BALANCE} for the tendered amount in the nuberpad = ‘’ actions
But thats another thing
First thing to check is rule mapping but if config task should be done already.
Also you didnt need to duplicate the payment processed rules as they will fire on any payment processed matching those constraints.
I checked the rule mapping it was all correct. I removed the payment process and added those two extra rules for credit card and it would still not work. I definitely think I did something wrong somewhere but can’t seem to find it, coz I removed all the actions and rules relating to fast credit card payment, ran the config task for credit card to add it, ran it again to remove it, ran it one more time to add it, and didn’t alter anything, but fast credit card button would not do anything even if I just pressed it and did not put any input in the number pad.
So I decided to scratch it and just leave credit card to settle screen.
Also I notice one thing, when u insert something in the number pad lower than the balance amount and apply it, the balance changes which is good, but the number pad doesn’t clear off anything that was there ready for another input. The only time it clears is when the input is higher than the balance amount in which case it just shows the change screen and starts a new ticket.
You would have to manually clear it in order to insert another input
You can automate this, add the set numberpad action to your rule, and set it without a value
Add this action as the last one in the rule and it will remove any numbers on the input field on the pos screen. I had the same issue and this worked a treat 
Hi QMcKay,
Thank you for your help working now
