FIXED: Credit Card Transaction: When using tokenization, users are now less likely to receive a "Padding is invalid and cannot be removed" error when entering credit cards. If this build does not completely fix the problem, there are potential workarounds to fix this error once it has occurred. FIXED: Transaction Entry: MasterCard BIN-2 credit cards will no longer receive a "Card Issue Detected" prompt.
FIXED: FirstData: Level three data will now be properly sent to the processor. NOTE: A "Commodity_Code" (exact name) UDF may need set up on the sales line to properly send this value, and this value can be populated in various ways. UOfMs must conform to the Payeezy codes, but we provide an override to default a value.
ADDED: FirstData: Setting: Default UofM Override - If the GP UofMs do not comply with the FirsData codes, this setting can be set to send a UofM code outlined here. ADDED: FirstData: Setting: Default Value When Values are Blank - By default, we will send "NA" for any required fields for level three data. This setting can be used to send a different default value.
FIXED: Authorize.Net processor transactions do not properly restrict data length. FIXED: Making changes to a transaction may cause the amount to be reset when Force Zero Dollar Authorizations is enabled.
ADDED: Credit Card Transaction Entry Security - Force Zero Dollar Auths: This security forces the amount field to be $0 for new authorizations. ADDED: Version Control - Users will not be able to use a version of CardControl other than the version that is listed in the database. Users are notified of version differences upon log in. If a user logs in with a version of CardControl that is not listed in the database, the user may update the database version only if they have 'Update Database' permissions in Security. Users without the 'Update Database' permission will be prompted to get the correct version of CardControl. ADDED: MSMQ Communication between SalesPad GP and CardControl ADDED: MSMQ Communication between Additions and CardControl ADDED: MSMQ Communication between ERP and CardControl ADDED: eBizCharge processor
FIXED: If an inactivity time out executes while the customer search confirmation dialogue is open, an error will no longer occur. FIXED: Transaction Entry: Amount field now allows for greater values. FIXED: Login issue for GP2010 users. FIXED: Adjusted information sent with eBizCharge request FIXED: Fixed a bug where card numbers would be used when a stored token already exists with Authorize.Net FIXED: Credit Card Transaction Entry Screen: If a token exists for a card, the user is now prevented from processing that card without using the token. FIXED: After a failed transaction, it was possible for line item information to not be populated correctly. FIXED: Masked AMEX cards show the last 4 digits now instead of the last 5. This may cause duplicate entries of previously saved American Express cards. FIXED: Credit Card Transaction Entry: Vantiv(Previously LitleOnline) now accepts quotations, apostrophes, less than, greater than, and ampersand characters in all appropriate fields.
UPDATED: Processor Setup - LitleOnline is now Vantiv, FirstData E4 is now PayEezy. UPDATED: Settings: Fixed grammar errors within descriptions. UPDATED: CardControl now has the ability to adjust choose columns on all grids.
REMOVED: 'Zip Code' setting on eBizCharge. REMOVED: AssureBuy is no longer an available processor.