Devices described on this page are available only to merchants on the WorldPay processing platform
PaySimple offers several devices for accepting card present transactions. For offering EMV (dip), swipe, and contactless (ApplePay/GooglePay), PaySimple recommends the Verifone MX 915.
|Verifone MX 915||EMV (dip), swipe, key enter, ApplePay/GooglePay||Robust, reliable platform||Wired ethernet|
|Link 2500||EMV (dip), swipe, key enter, ApplePay/GooglePay||Wireless, mobile||WiFi|
- Connect your device to power and an ethernet connection
- An activation code will appear on the screen
- Call the Activate endpoint with the activation code displayed on the screen. You can also enter a
idle_messagewhich will display on the screen whenever it is not asking for customer card input. The description field is used for your identification of the device only.
- Store the
device_idin the response in your database, along with a description so you can identify it later.
- In your application, create a way for a user to select a particular device or register it with the device running your software.
- From your server, call the Sale endpoint with the selected
device_idand other payment details. If you wish to allow the user to optionally key enter the card, set
- Calling the sale, credit or vault endpoints will "wake up" the device and ask for user input.
- The user can choose to swipe, dip, tap or key-enter.
- When the user completes input, the endpoint will return a JSON response.
Do I need to open up a port in my firewall or make any other changes on my network to support devices?
In most cases, no. Devices keep open an outgoing connection to servers to keep configuration to a minimum.
You can. However, devices must be connected directly to the internet via ethernet or wifi. Connections directly through the device (e.g. Bluetooth) or over mobile networks are not supported at this time. All payment requests are made from the server application.
Yes. Populate the
tip section on the Sale request.
Yes. PaySimple recommends setting your connection timeout on calls to device Sale, Credit and Vault to 6 minutes to allow for user interaction. Using asynchronous non-blocking io is suggested in your API to prevent scalability issues.
The only way to cancel user input once the endpoint has been called is to press the red cancel button on the device.
Updated about 1 year ago