This guide will be removed on April 29, 2022. Please use our new, easier-to-use Toast technical documentation site. All updated content is on the new site.

Money 2.48

This section provides information about changes that affect the way a restaurant receives payments.

Improvements

The following notes provide information about new and improved functionality.

Updated appearance and message for the Remove Card screen

In the Toast POS app, the appearance and messaging of the Remove Card screen used during the payment workflow has been updated along with the remove card animation.

Not Today button has been relabeled to No Tip

In the refactored payment workflows that were released to some Toast customers, the button label to choose not to leave a tip has been changed from Not Today to No Tip.

Fixes

The following notes provide information about fixed problems.

Guest-facing display crashes related to hardware issues have been fixed

Previously, a hardware problem with the guest-facing display (for example, loose or disconnected cables) could cause the payment workflow to crash during EMV transactions (if the card is not removed from the reader promptly) or during any credit card payment for which only a partial authorization is received. This crash has been fixed.

Crash associated with choosing Custom Tip during payment has been fixed

Previously, choosing the Custom Tip option during the payment workflow would crash if the Android device were set to certain non-English languages (those that use commas as the decimal separator in numbers, like "$1,50"). This has been fixed.

Crash associated with leaving the Toast POS device on the final screen of the payment workflow has been fixed

Previously, a crash could occur if the Toast POS device was left on the final screen of the payment workflow for many hours (often overnight). Passcoding back in the next day would trigger the crash. This has been fixed.

Loyalty program and tipping configurations no longer cause Toast POS app crash during credit card transactions

A problem existed with the way the Toast platform stores Toast loyalty program and tipping configuration settings. This problem caused the POS app to crash while taking credit card payments. The problem has been fixed.

POS app screen timeout coinciding with an incomplete payment workflow no longer causes POS app crash

A problem that caused the Toast POS app to crash when a payment was left incomplete until the POS app screen timeout occurred has been fixed. Now, the POS app will automatically complete an incomplete payment when the configurable screen timeout period for the POS device elapses. The way that the POS app completes the payment depends on the stage of the payment workflow that the app was in when the guest and restaurant employee left it. The way that the POS app handles incomplete payments has not changed, except in the way that incomplete payments are affected by the POS app screen timeout. The following list describes how the POS app handles an incomplete payment workflow in common situations.

  • Before the payment method is presented (for example, on the Swipe card to pay screen). The payment is abandoned.

  • After a payment card swipe or dip but before the payment method has been fully validated. For example, the employee needs manager approval to take the payment. The payment is abandoned.

  • After the payment method has been fully validated but before the payment has been submitted for processing (for example, on the tipping screen). The payment is submitted with default parameters for all optional guest choices (for example, the payment will not include a tip even if the restaurant location has configured a default tip). The restaurant receives payment funds.

  • After the payment has been submitted for processing (for example, on the receipt options screen). The financial aspects of the payment complete normally. The rest of the workflow does not occur (for example, no receipt and no rewards signup). The restaurant receives payment funds.

Resolved occasional errors caused by using the same credit card for consecutive transactions

Previously, when you used the same credit card to pay for consecutive transactions, a confirmation dialog displayed and persisted even after you removed the credit card without processing a charge. Attempts to dismiss or interact with this dialog sometimes led to app crashes. With this release, when you remove the credit card that is being used for the second time without processing a charge, the confirmation dialog is automatically dismissed.