dsiEMVAndroid™

dsiEMVAndroid is an Android library that provides applications with the ability to process an EMV (chip card) electronic payment. More Specifically, dsiEMVAndroid is an Android .aar library that is compatible with most Android devices with an minimum API level of 23. dsiEMVAndroid is designed to communicate exclusively to Datacap’s NETePay Hosted™ platform, and doesn’t require an in-store NETePay application. Communication to NETePay Hosted uses the Android device’s IP stack, and all messages are encrypted for secure transmission over open networks (such as the Internet).

The dsiEMVAndroid control uses XML formatted requests and responses for transaction processing requests. For help getting started with dsiEMVAndroid, see Datacap’s dsiEMVAndroid Demo app on GitHub, or contact Datacap Integration Support.







dsiEMVAndroid is a library that is compiled directly into the POS application and runs on an Android device. Once the app calls into the dsiEMVAndroid control to start a transaction, dsiEMVAndroid takes over the payment flow: it connects directly to the paired EMV secure device over Bluetooth LE, USB, or IP, prompts the customer for payment, and captures and encrypts cardholder data at the device itself. dsiEMVAndroid then builds an XML-formatted request and sends it as an outgoing HTTPS request over the Android device's own IP stack directly to Datacap's NETePay Hosted™ platform. From there, the request is routed to a backend processor for authorization, and the response flows back through dsiEMVAndroid to the POS application.

dsiEMVAndroid supports two development models: On-padOn-pad and Off-padOff-pad. On-pad apps run directly on the Android payment device (e.g. a PAX or Ingenico Android terminal), sharing screen time with the device's own retail application (PXRetailer or UXR) to display card entry, PIN, and signature prompts, and communicating with it over a local loopback IP address. Off-pad apps run on a separate Android device, such as a phone or tablet, and dsiEMVAndroid communicates with an external, paired EMV secure device over Bluetooth LE, USB, or IP instead.









The EMV PIN pads supported by dsiEMVAndroid can be determined by performing the GetDevicesInfo method available in dsiEMVAndroid. See Functions ListSee GetDevicesInfo for details.