question

Paul.Ryan avatar image
Paul.Ryan asked ·

Cashback Semi Intergration

Hi David,


We are integrating our POS software into the Clover via the .net SDK and the USB Pay Display and would like to be able to allow the cashier to select the cashback amount for a sale.

At present the Clover ask the customer to insert the card, then asks if they would like cashback and how much, we would like to move that to our POS to allow the cashier to select the option if possible, as they may not have enough cash in the till to honor the cashback. On our current payment solution we do this programically by blocking out cashback options that are over a set value (e.g. not allowing £50 cashback if the till only has £40)

I know we can disable cashback for a sale with SaleRequest.DisableCashback but this is an all or nothing option.

We have also tried intercepting the CASHBACK_CONFIRM & CASHBACK_SELECT messages in the OnDeviceActivityStart() callback with the aim to use InvokeInputOption() to remotly press the button, but the InputOptions only list Cancel as an avilable option and not the 6 cashback options, also as this is a non-blocking callback the customer could select the cashback option before the cashier.


Is their away of picking up the cashback prompts selection?, or any future updates that will improve this ?


Thanks


Paul






semi-integrations
10 |2000 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

David Marginian avatar image
David Marginian answered ·

This is by design. If we allowed what you are asking for a "bad" cashier could select a cash back amount and pocket the money without the customer ever knowing. That is why you cannot invoke the input options on the cashback screen.

If the merchant has standards on how much cash they keep they can configure the cashback options on their device via the Setup app -> Payments -> Cash back options.

I have created an issue for our Remote Pay SDKs to also allow for the customization of the cashback options (similarly to how we handle tip suggestions, but I don't expect it will be a priority).


Share
10 |2000 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Paul.Ryan avatar image
Paul.Ryan answered ·

Hi David


Thanks for the above

From my own experience, EPOS I would be expecting the cashiers to ask the Question to the customer would you like cashback Yes or No. Plus cashier would know if they had enough cash in the Till before selecting the amount off cash to give the customer.


Paul.


1 comment Share
10 |2000 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

I understand what you are saying but there is no need to alter Clover's payment flow (cashback questions are displayed on the customer facing device) to meet that requirement, it can be determined pre-payment (with the changes to the SDK that I am proposing). Does the cashier have any money available for cashback, yes or no? If no, then they select an option in your POS to disable cash back for that transaction. If they do AND IF our SDKs allowed for the cashback options to be customized then the POS could prompt the merchant for the cashback options and pass it along in the payment request as well.

0 Likes 0 · ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community