Toggling visibility of 'All payment types' button on terminal checkout screen

Questions
1

One of our customers recently reported the use of the ‘All payment types’ button at the top of the terminal checkout screen to bypass payment. Is it possible to limit access to this screen or simply toggle the individual payment options?

Some additional background: their terminal hardware is unattended and intended to take card payments only. However, the All payment types button provides access to a ‘Cash’ option and screen, on which the user can simply enter the tender amount, bypassing the need to actually pay for their order.

I found another forum post asking if the ‘unattended’ workflow is supported by the terminals, but it has no replies.

3

Hey @zmcnulty! Just to clarify, are you referring to using the Terminal in standalone POS mode, or is it paired via Terminal API?

If you’re pairing via Terminal API, can you share an example of the CreateTerminalCheckout request you’re making?

4

Hi @josh-square !

The terminal is paired via the terminal API.

Our CreateTerminalCheckout request includes the following TerminalCheckout object, in addition to an idempotency key:


                var checkout = new TerminalCheckout

                {

                    ReferenceId = invoiceNo,

                    OrderId = createdOrder.Id,

                    AmountMoney = createdOrder.TotalMoney,

                    DeviceOptions = deviceOptions,

                    Note = squareNoteNotes.ToString(),

                    PaymentType = CheckoutOptionsPaymentType.CardPresent,

                    PaymentOptions = paymentOptions

                };

The deviceOptions object only includes the required deviceId property.

I personally expected some of the configurability re: the All Payment Types button I asked about above from within the deviceOptions or paymentOptions properties, but didn’t see anything.

Thanks for you reply!

5

Are there any further updates?

6

I believe this might be related to a previously fixed bug. If you update your Terminal to the latest version, does the issue persist?