Create a Payment Device Module

The communication between the payment device and Commerce Cloud Endless Aisle requires the elements in the following diagram:

Devices use one of two different ways that the device can interact with the app:

• Get the card number by reading the card and pass it back to the app, without trying to determine whether the card is valid. Verifone interacts with the app in this way; the JavaScript code for Verifone fires payment:credit_card_data.
• Get the card number and tell the payment module whether the payment was approved or declined. Adyen interacts with the device in this way. The JavaScript code for the Adyen module fires either payment:cc_declined or payment:cc_approved.

The payment device module consists of:

• the Appcelerator module, written in Objective C, which communicates directly with the payment device
  Note: If the payment device manufacturer provides a JavaScript API to communicate with the device, you should use that instead of a native Objective-C API.
• a JavaScript wrapper, which communicates with the Objective C module, using the Objective C bridge

  For information on how to create an Appcelerator module and communicate between the JavaScript/Objective-C bridge, look at the Appcelerator iOS Module Develpment Guide.

The entry points required in a payment device module include:

• acceptPayment
• cancelPayment
• cancelServerTransaction
• verifyDeviceConnection
• getNoDeviceConnectionImage
• getNoDeviceConnectionMessage

The exit points are all the events that are fired back to the app code, such as:

• payment:cc_approved
• payment:credt_card_data

Between the entry points and exit points, you write code in the device driver and the JavaScript wrapper.

To create a payment device module, you implement a series of functions that the DSS app calls, starting with the JavaScript function called acceptPayment.

The JavaScript function:

• Begins the process of accepting a new payment.
• Tells the module to start the process of getting the payment information.

  The process runs on a separate thread and the acceptPayment function returns back to the caller while the device is prompting the user for payment.

It's essential to handle all possible cases.