AnsweredAssumed Answered

ExpressResponseMessage: CardNumber Required tripos direct

Question asked by kevin@bottlepos.com on Dec 22, 2019
Latest reply on Dec 27, 2019 by kevin@bottlepos.com

we are getting

ExpressResponseMessage: CardNumber Required

 

error on tripos direct 5.16 using MX915 on all the cards and can't figure out why. The machine and terminal was working fine until the night before and the next morning this started happening. At night I know there is a scheded reboot of MX915 and we also have a computer restart that happens 3 hours after the terminal restart.

 

 

I compared a successful transaction vs unsuccessful and the only diff was this :  

 

 

2019-12-22 12:11:45,189 [10] triPOS INFO - 933ec8b8-1f03-4219-8c20-80df6bbf0dab VeriFoneFormAgentXpiPinPad.cs.GetEncryptedCardDataFromTags: VerifoneFormAgentXpi encrypted card data identified as not encrypted

 

Any help would be greatly appreciated. 

 

 

 

=============================

2019-12-22 12:11:33,304 [STP SmartThreadPool Thread #1] triPOS TRACE - PinPadConnectionPool.cs.TryGetPinPad: Attempting to retrieve PIN pad with laneId:1
2019-12-22 12:11:33,307 [STP SmartThreadPool Thread #1] triPOS TRACE - PinPadConnectionPool.cs.TryGetPinPad: PIN pad with laneId:1 was found?[True]
2019-12-22 12:11:33,314 [STP SmartThreadPool Thread #1] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab LaneContext.cs.Initialize: Creating a LaneContext for lane [1]
2019-12-22 12:11:33,316 [STP SmartThreadPool Thread #1] triPOS INFO - 933ec8b8-1f03-4219-8c20-80df6bbf0dab LaneContext.cs.Initialize: PinPadConfig for lane [1]: BaudRate:57600, ComPort:COM8, Driver:VeriFoneFormAgentXpi, IpAddress:, IpPort:0, TerminalType:PointOfSale, IsUnattended:False
2019-12-22 12:11:33,351 [STP SmartThreadPool Thread #1] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab InitializePipelineOperation.cs.ExecuteAsync: Initializing HostRequest
2019-12-22 12:11:33,353 [STP SmartThreadPool Thread #1] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ObtainCardDataOperation.cs.ExecuteAsync: Obtain card info
2019-12-22 12:11:45,128 [3] triPOS TRACE - VeriFoneXpiPinPad.cs.CheckCxxResponseCode: VeriFoneXPI C31 response is success
2019-12-22 12:11:45,185 [10] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab VeriFoneXpiPinPad.cs.GetEncryptedCardDataAsync: VerifoneXPI E06 encryption type is 05
2019-12-22 12:11:45,187 [10] triPOS INFO - 933ec8b8-1f03-4219-8c20-80df6bbf0dab VeriFoneFormAgentXpiPinPad.cs.GetEncryptedCardDataFromTags: VerifoneFormAgentXpi encrypted card data response has BIN match ID 00
2019-12-22 12:11:45,189 [10] triPOS INFO - 933ec8b8-1f03-4219-8c20-80df6bbf0dab VeriFoneFormAgentXpiPinPad.cs.GetEncryptedCardDataFromTags: VerifoneFormAgentXpi encrypted card data identified as not encrypted
2019-12-22 12:11:46,205 [4] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ProcessCardDataOperation.cs.ExecuteAsync: Pre-process card info
2019-12-22 12:11:46,206 [4] triPOS DEBUG - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ProcessCardDataOperation.cs.ParseCardData: Card data is ContactIccCardData
2019-12-22 12:11:46,208 [4] triPOS DEBUG - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ProcessCardDataOperation.cs.ParseIccCardData: Parsing ContactIccCardData
2019-12-22 12:11:46,210 [4] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ProcessCardDataOperation.cs.ExecuteAsync: Looking up account in standard BIN table.
2019-12-22 12:11:46,212 [4] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab BinTable.cs.DoLookup: Looking up account in BIN table
2019-12-22 12:11:46,213 [4] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab VantivBinManager.cs.FindBin: Searching the BIN table for the given account BIN
2019-12-22 12:11:46,215 [4] triPOS DEBUG - 933ec8b8-1f03-4219-8c20-80df6bbf0dab BinTable.cs.DoLookup: Found account in BIN table. BIN attributes: DebitCard, CheckCard, PinlessBillPay. BIN network: INLK,NYC1,PAVD,VISN
2019-12-22 12:11:46,216 [4] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab EbtTypeOperation.cs.ExecuteAsync: Confirm Ebt card type
2019-12-22 12:11:46,218 [4] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab EbtTypeOperation.cs.ConfirmEbtTypeAsync: Confirming Ebt type
2019-12-22 12:11:46,219 [4] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ConfirmSaleAmountsOperation.cs.ExecuteAsync: Confirm amounts
2019-12-22 12:11:46,221 [4] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ConfirmSaleAmountsOperation.cs.ConfirmAmountsAsync: Confirming amounts
2019-12-22 12:11:46,222 [4] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ConfirmSaleAmountsOperation.cs.ConfirmAmountsAsync: Request Transaction Amount: 253.97
2019-12-22 12:11:48,378 [10] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ConfirmSaleAmountsOperation.cs.ConfirmOriginalTransactionAmountAsync: The original transaction amount was confirmed.
2019-12-22 12:11:48,380 [10] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ConfirmSaleAmountsOperation.cs.ConfirmTipAmountAsync: Configuration does not support tip.
2019-12-22 12:11:48,383 [10] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ConfirmSaleAmountsOperation.cs.ConfirmTotalAmountAsync: The base transaction amount is the same as the total transaction amount.
2019-12-22 12:11:48,385 [10] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab UsdDebitEmvFlow.cs..ctor: Initializing the host hostTransactionRequest for USD Debit EMV
2019-12-22 12:11:48,387 [10] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab EmvTransactionFlow.cs.UserInteractAsync: Initiating user interaction for EMV
2019-12-22 12:11:48,389 [10] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab PreHostProcessingOperation.cs.ExecuteAsync: Pre-process transaction
2019-12-22 12:11:48,390 [10] triPOS TRACE - EmvTransactionFlow.cs.PreHostProcessingAsync: Initiating user interaction for USD EMV
2019-12-22 12:11:55,755 [17] triPOS TRACE - VeriFoneXpiPinPad.cs.CheckCxxResponseCode: VeriFoneXPI C33 response is success
2019-12-22 12:11:55,757 [17] triPOS TRACE - EmvUtility.cs.CheckOfflineResult: CID: ARCQ (80) [Continue online]
2019-12-22 12:11:56,783 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvWholeTagsForCertification: CardRiskManagementDataObjectList1 (8C): 9F 02 06 9F 03 06 9F 1A 02 95 05 5F 2A 02 9A 03 9C 01 9F 37 04
2019-12-22 12:11:56,785 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvWholeTagsForCertification: CardRiskManagementDataObjectList2 (8D): 8A 02 9F 02 06 9F 03 06 9F 1A 02 95 05 5F 2A 02 9A 03 9C 01 9F 37 04
2019-12-22 12:11:56,786 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvWholeTagsForCertification: CardholderVerificationMethodList (8E): 00 00 00 00 00 00 00 00 02 01 00 04 02 05 42 00 1F 00
2019-12-22 12:11:56,788 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvWholeTagsForCertification: CertificationAuthorityPublicKeyIndexCard (8F): MISSING
2019-12-22 12:11:56,789 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvWholeTagsForCertification: IssuerApplicationData (9F10): 06 01 0A 03 A0 20 00
2019-12-22 12:11:56,791 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvWholeTagsForCertification: TerminalVerificationResults (95): 80 00 04 80 00
2019-12-22 12:11:56,793 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvWholeTagsForCertification: TransactionStatusInformation (9B): 68 00
2019-12-22 12:11:56,795 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvBitsForCertification: TSI Byte 1 Bit 8: 0
2019-12-22 12:11:56,796 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvBitsForCertification: TVR Byte 1 Bit 8: 1
2019-12-22 12:11:56,799 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvBitsForCertification: TVR Byte 1 Bit 7: 0
2019-12-22 12:11:56,801 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvBitsForCertification: TVR Byte 4 Bit 8: 1
2019-12-22 12:11:56,803 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvBitsForCertification: CVR Byte 2 bit 4: 0
2019-12-22 12:11:56,804 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvBitsForCertification: CVR Byte 2 bit 3 (Offline PIN Verification performed): 0
2019-12-22 12:11:56,806 [3] triPOS TRACE - EmvCertificationTagsLogger.cs.LogEmvBitsForCertification: CVR Byte 2 bit 2 (Offline PIN Verification did not fail): 0
2019-12-22 12:11:56,808 [3] triPOS INFO - EmvUtility.cs.GetCvmPerformed: CVM: enciphered online PIN (02)
2019-12-22 12:11:56,809 [3] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab EmvTransactionFlow.cs.InitializeSignatureStatus: Initializing whether signature is required
2019-12-22 12:11:56,811 [3] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab NoSignaturePrompt.cs.GetStatus: Signature not required by payment type
2019-12-22 12:11:56,812 [3] triPOS TRACE - EmvUtility.cs.CheckOfflineResult: CID: ARCQ (80) [Continue online]
2019-12-22 12:11:56,814 [3] triPOS TRACE - EmvUtility.cs.CheckOfflineResult: CID: ARCQ (80) [Continue online]
2019-12-22 12:11:56,816 [3] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab PreHostProcessingOperation.cs.ExecuteAsync: Pre-host response is null
2019-12-22 12:11:56,822 [3] triPOS TRACE - StoreAndForwardService.cs.IsHostAvailable: StoreAndForwardService: Host is currently online. Transaction will NOT be stored.
2019-12-22 12:11:56,828 [3] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab HostProcessingOperation.cs.DoHostProcessingAsync: Online processing
2019-12-22 12:11:56,831 [3] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab HostProcessingOperation.cs.DoHostProcessingAsync: Call host
2019-12-22 12:11:57,173 [4] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ExpressHost.cs.ProcessTransactionAsync: Processing transaction using the Express host
2019-12-22 12:11:57,176 [4] triPOS INFO - 00000000-0000-0000-0000-000000000000 Express.cs.SendState: Express state changing from SettingUpRequest to SettingUpRequest in MoveNext
2019-12-22 12:11:57,179 [4] triPOS DEBUG - 933ec8b8-1f03-4219-8c20-80df6bbf0dab Express.cs.SendRequestAsync: Express.cs: Sending message to host url:https://transaction.elementexpress.com/
2019-12-22 12:11:57,183 [4] triPOS INFO - 933ec8b8-1f03-4219-8c20-80df6bbf0dab Express.cs.SendState: Express state changing from SettingUpRequest to WaitingResponse in MoveNext
2019-12-22 12:11:57,367 [7] triPOS INFO - 933ec8b8-1f03-4219-8c20-80df6bbf0dab Express.cs.SendState: Express state changing from WaitingResponse to ParsingResponse in HandleResponse
2019-12-22 12:11:57,369 [7] triPOS INFO - Express.cs.LogHelpfulResponseDetails: -------------- Response Details --------------
2019-12-22 12:11:57,371 [7] triPOS INFO - Express.cs.LogHelpfulResponseDetails: ExpressResponseCode: InvalidData
2019-12-22 12:11:57,372 [7] triPOS INFO - Express.cs.LogHelpfulResponseDetails: ExpressResponseMessage: CardNumber Required
2019-12-22 12:11:57,373 [7] triPOS INFO - Express.cs.LogHelpfulResponseDetails: HostResponseCode:
2019-12-22 12:11:57,377 [7] triPOS INFO - Express.cs.LogHelpfulResponseDetails: HostResponseMessage:
2019-12-22 12:11:57,378 [7] triPOS INFO - Express.cs.LogHelpfulResponseDetails: ProcessorName: VANTIV_PROD
2019-12-22 12:11:57,380 [7] triPOS INFO - Express.cs.LogHelpfulResponseDetails: TransactionId:
2019-12-22 12:11:57,383 [7] triPOS INFO - Express.cs.LogHelpfulResponseDetails: ----------------------------------------------
2019-12-22 12:11:57,385 [7] triPOS INFO - 933ec8b8-1f03-4219-8c20-80df6bbf0dab Express.cs.SendState: Express state changing from ParsingResponse to Done in HandleResponse
2019-12-22 12:11:57,387 [7] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ExpressHost.cs.HandleExpressCompleted: Express response message: CardNumber Required
2019-12-22 12:11:57,389 [7] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ExpressHost.cs.HandleExpressCompleted: Express response code: InvalidData
2019-12-22 12:11:57,390 [7] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab ExpressHost.cs.HandleExpressCompleted: Express host response code: InvalidData
2019-12-22 12:11:57,392 [7] triPOS DEBUG - HostProcessingOperation.cs.HandleHostCompleted: Processor Completed. Processor Response Message:
2019-12-22 12:11:57,394 [7] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab PinPadPostHostProcessingOperation.cs.ExecuteAsync: Post-process
2019-12-22 12:11:57,395 [7] triPOS INFO - 933ec8b8-1f03-4219-8c20-80df6bbf0dab EmvTransactionFlow.cs.PostHostProcessingAsync: Begin EMV post host processing
2019-12-22 12:11:57,397 [7] triPOS TRACE - 933ec8b8-1f03-4219-8c20-80df6bbf0dab EmvTransactionFlow.cs.FinishTransactionAsync: Finalizing transaction

Outcomes