4/27/2020
------------ Release Update 20.04.27 DB Version 178 ----------------

Tender Accounts

• Added an option to require a security code to balance card tenders. (1466)
• There is a corresponding option that controls of the security code should be printed when printing the balance.

When enabled:
• The user must enter a security code when selling the balance card.
• The security code will be saved and can be found under Tender Accounts find.
• The adjustment feature of tender accounts allows this security code to be updated.

• The purpose of the security code is similar to the CVV2 number on a credit card. Having the code indicates the card is present and the account number was not made up.
• The security code is required when adding the tender as a customer order tender.
• Manually entering the account number in POS requires the security code.
• When prompted for a security code is must be entered. If the code does not match the code on file the tender is rejected. The user must reenter the tender.

• A security code is not required when scanning a balance card.
• When looking up the tender account at POS via Tender Account find, it is assumed that the customer is present and validated by the cashier. Therefore the security code is not required.

4/6/2020

Tender Accounts

• The method of updating tender accounts and the balance has been updated to prevent concurrency errors.
• A concurrency error could cause a tender account to not be updated properly.

1/22/2020

SBT

• Document for 832 and 852 enum was duplicated. Changed 852.

1/14/2020

POS

• Voiding a sale by entering or scanning the SaleID did not validate the sale date properly. This allowed sales from a previous day to be voided. (1122)

General

• Updated how [i]merchant checks if SQL commands can be run.
• This was needed to accommodate SQL command line tools 2019.