Windows sdk 7.1a verification#

The feature is disabled by default, it can be enabled on the Firmware Config Form. The mPOS device has its own contact card insert and removal detection as shown in the following flow diagrams. The app can prompt for card removal after transaction completed. Contact Card Insert and Removal Detection Later, the batch data should be updated to the server for settlement. The app should store and display the transaction data returned in the batch data. In this step, the device sends back the final transaction result from the EMV card by onReturnTransactionResult and onReturnBatchData callbacks.

This step is handled transparently between the device and EMV card if issue scripts ( Tag 71 and Tag 72) are present in the online processing results. A reversal message will be generated at the completion step to reverse the transaction if necessary. connectivity lost), the app should set the input to null or empty string at sendOnlineProcessResult. The final Tag 8A from processor still need to be sent back to device at onRequestOnlineProcess for the complete EMV processing. If the transaction is a Quick Chip transaction, the device will set Tag 8A to Z3 to allow the user to remove the card while the app is waiting for the online processing result. If online processing is required, the device will trigger onRequestOnlineProcesscallback with the transaction data in TLV structure. A final confirmation is sent to device by calling sendFinalConfirmResult. This gives the user a chance to review the amount, the payment method, etc. The app should prompt the user for a confirmation.

Byte 1ДЄt the end of this step, a final confirmation is required to proceed via onRequestFinalConfirm onRequestFinalConfirm callback. The app should display the instruction for PIN entry on the device.ДЇor SCRP device, the PIN entry will be handled by BBDeviceSPoCController, refer to Software-Based PIN Entry for details.Дepending on the requirement of the EMV card, the app should capture the signature according to the first byte of Tag 9F34 CVM results at onRequestOnlineProcess( Step 10) or onReturnBatchData ( Step 12). If the EMV transaction requires PIN verification, the device will request PIN entry from the user by triggering onRequestPinEntry callback.

Windows sdk 7.1a verification#

There are different cardholder verification methods (CVMs) supported in an EMV transaction. If this step fails, the EMV process stops and returns the transaction result by onReturnTransactionResult callback. This step is only done between the device and EMV card.

In this step, device will read the necessary data from the EMV card. The transaction can be aborted by calling cancelSelectApplication command. The app should prompt the user to select one application and pass the selection to device by calling the selectApplication command. The callback returns an array of Application names sorted by priority. Add ( 'terminalTime', terminalTime ) // Amount Currencењњharacter currencењњharacter = new Currencењњharacter startEmvWithData :] Android/JavaДictionary data = new Dictionary () // Terminal Time String terminalTime = new SimpleDateFormat ( 'yyMMddHHmmss' ). NSMutableDictionary * inputData = // Terminal Time NSDateFormatter * formatter = init ] ] ] forKey : ] // Amount NSArray * currencењњharacter =, ,, nil ] // Check for Swipe, Insert and Tap card forKey : ] // Add other transaction inputs to the inputData dictionary.