Elavon downloads and stores cookies on your device when you visit our website. We use these cookies to better understand and improve your browsing experience by identifying most visited pages, personalising content, and measuring site performance.

Essential cookies enable core functionality such as page navigation and access to secure areas. The website cannot function properly without these cookies; they can only be disabled by changing your browser preferences.

These are cookies that support site functionality that is visible or advantageous to you or your experience of the site, they enable websites to remember choices and provide a more personalized experience.   Functional cookies help to provide services that you request, such as language preference or layout.

Performance cookies help us to improve our website by collecting and reporting information on its usage (for example, which of our pages are most frequently visited).

These cookies and similar technologies gather information about your browsing habits. They remember that you've visited a website and share this information with other organisations, such as advertisers and platforms on which we advertise. They do this in order to provide you with ads that are more relevant to you and your interests. Although these cookies and similar technologies can track your visits to other websites, they don't usually know who you are. Without these cookies, online advertisements you encounter will be less relevant to you and your interests.

Cookie Settings

U.S. Bank Europe DAC. Registered in Ireland – Number 418442..  Registered Office: Block F1, Cherrywood Business Park, Dublin 18, D18 W2X7, Ireland.
U.S. Bank Europe DAC, trading as Elavon Merchant Services, is regulated by the Central Bank of Ireland.
 
U.S. Bank Europe DAC. Registered in Ireland with Companies Registration Office. The liability of the member is limited. United Kingdom branch registered in England and Wales under the number BR022122.
U.S. Bank Europe DAC, trading as Elavon Merchant Services, is a credit institution authorised and regulated by the Central Bank of Ireland.  Authorised by the Prudential Regulation Authority.  Subject to regulation by the Financial Conduct Authority and limited regulation by the Prudential Regulation Authority.  Details about the extent of our regulation by the Prudential Regulation Authority are available from us on request.

Most popular solutions

Additional solutions

Fusebox integration & options

Optional platform features

Documentation

North America

Europe

Regions

## Pairing a Moby/5500 card reader 

For mobile application use (iOS and Android), the Moby/5500 can be used over a Bluetooth connection. In order to pair the Moby/5500 to the mobile device, you need to use the existing `findDevices` API to find the reader first, and then setup a pairing listener for that device. When you call 'connectAndInitialize` on that device, you will see a pairing dialog displayed by iOS and Android. The user should click pair and then press the power/bluetooth button on the Moby/5500. This will display a sequence of LED lights on the Moby/5500. The same sequence will be returned back to the application via the pairing listener. The application can then display the sequence for the user to confirm. Once confirmed, the pairing process will be completed.

### Overview of pairing steps

1. Call `findDevices` API using the commerce account.
2. When device search returns with Moby/5500, call `selectDevice` API to set it as the active device.
3. Setup the LED pairing listener on the card reader interface returned from `selectDevice`.
4. Call `connectAndInitialize` API.
5. iOS/Android displays dialog to pair; user accepts.
 
::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/commerce-sdk/ios_pairing_request.png" alt="iOS Pairing Request" max-width="250" max-height="250"}
 
::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/commerce-sdk/android_pairing_request.png" alt="Android Pairing Request" max-width="250" max-height="250"}

6. User presses bluetooth button on the Moby/5500.
 
::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/commerce-sdk/bluetooth_button.png" alt="Moby/5500 Bluetooth Button" max-width="250" max-height="250"}

7. Moby/5500 displays sequence of LED lights.
 
::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/commerce-sdk/led_light.png" alt="Moby/5500 LED Lights" max-width="250" max-height="250"}

8. The LED sequence is sent to the pairing listener.
9. App displays the sequence to the user. Per PCI compliance, the app is required to display the sequence so the user can confirm it.
 
::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/commerce-sdk/moby5500_led_conf.png" alt="Moby/5500 LED Confirmation" max-width="250" max-height="250"}

10. User confirms the sequence. Bluetooth pairing is now established.

## Troubleshooting guidelines for users 

Pairing process fails

- **iOS** - User has to go into iOS Bluetooth settings and forget the temporarily paired reader before re-starting pairing process.
- **Android** - User can start pairing process again without any further steps to be done.

Reader is not initiating LED sequence

- Make sure user clicks button on Moby/5500 within 30 seconds of accepting the pairing dialog displayed by iOS/Android.


### Java (Android) - simplified flow

Refer to the sample application source code for more information.

```java
// get a hold of the cardreaders interface
ECLDevicesInterface<ECLCardReaderInterface> cardReadersInterface = eclAccountInterface.getCardReaders();
// kick off a device search and setup a listener to receive callbacks from the search
cardReadersInterface.findDevices(new ECLFindDevicesListener() {
 // implementation of device search done callback
 public void devicesSearchDone(List<ECLFindDevicesSearchResult> deviceSearchResults) {
 ...
 if (deviceSearchResults.size() > 0) {
 ECLFindDevicesSearchResult result = deviceSearchResults.get(0);
 // set this card reader as the active device
 ECLCardReaderInterface cardReaderInterface = cardReadersInterface.selectDevice(result.getName(), result.getConnectionTypes());
 ...
 // add connection listener to receive connect and disconnect callbacks
 cardReaderInterface.addConnectionListener( new CardReaderListenerAdapter(...));
 
 if (result.getName().contains("MOB55")) {
 cardReaderInterface.addDevicePairingListener(new ECLDeviceLedPairingListener() {
 // the implementation of one of the pairing delegate callbacks
 // User has to press the power button on Moby/5500 to display the pairing sequence before this method gets called
 public void deviceLedPairingSequence(ECLDeviceInterface eclDeviceInterface, List ledSequence,
 ECLLedDevicePairingConfirmationInterface eclLedDevicePairingConfirmationInterface) {
 // display the sequence using com.roam.roamreaderunifiedapi.view.PairingLedView
 // see LedPairingDialog of sample app for details
 
 ...
 // if user confirms the sequence
 eclLedDevicePairingConfirmationInterface.confirm();
 }
 ...
 }
 }
 
 ...
 // connect and initialize the device. if an update is necessary, perform the update.
 cardReaderInterface.connectAndInitialize(true);
 }
 }
 ...
}
```

### Objective-C - simplified flow

Refer to the sample application source code for more information.

```objc
// get a hold of card readers implementation of the devices protocol from the account and call findDevices
[[_account cardReaders] findDevices:self forceToDisconnect:true timeoutInSeconds:30];
 
// in this case we made the current class receive the findDevices callbacks (note the reference to "self" above)
...
 
// the implementation of one of the findDevices callbacks
+ (void)devicesSearchDone:(id<ECLDevicesProtocol>)devices searchResults:(NSArray<ECLFindDevicesSearchResult *> *)deviceSearchResults {
 ...
 if ([searchResults count] > 0) {
 // make this device the "active" device
 ECLFindDevicesSearchResult *reader = deviceSearchResults[0];
 id<ECLDeviceProtocol> selectedDevice = [devices selectDevice:reader.name withConnectionTypes:reader.connectionTypes];
 id<ECLCardReaderProtocol> selectedCardReader = (id<ECLCardReaderProtocol>)selectedDevice;
 
 // register this class to receive connection related callbacks
 [selectedCardReader addConnectionDelegate:self];
 
 // register the pairing delegate - required for Moby/5500 pairing.
 [selectedCardReader addDevicePairingDelegate:self];
 
 [selectedCardReader connectAndInitialize:YES];
 ...
 
// the implementation of one of the pairing delegate callbacks
// User has to press the power button on Moby/5500 to display the pairing sequence before this method gets called
+ (void)devicePairingLedSequence:(NSArray *)ledSequence confirmationProtocol:(id<ECLLedDevicePairingConfirmationProtocol>)confirmationProtocol {
 // display the sequence using LedPairingView from RUA_MFI framework
 // see LedPairingViewController of sample app for details
 
 // if user confirms the sequence
 [confirmationProtocol confirm];
}
```

## Moby/5500 firmware update

When connecting to the Moby/5500 device for the first time, it may go through a firmware update if it is not already up-to-date. When the update is complete, the Moby/5500 will shutdown if it was running on battery power, in which case it will need to be manually rebooted by the user. If the Moby/5500 was not running on battery power (e.g. plugged into a power source), then it will reboot automatically after the shutdown.

CSDK will notify the integrating POS system via an API callback when the firmware update is complete so that the user can be notified to manually reboot the Moby/5500, if needed.

### Java (Android)

```java
// callback method in ECLCardReaderListener
@Override
public void cardReaderShouldManuallyReboot(ECLCardReaderInterface cardReader, boolean didUpdate)
{
 if (didUpdate)
 {
 AlertDialog.Builder builder = new AlertDialog.Builder(MainActivity.this);
 builder.setTitle("Manual Reboot")
 .setMessage("Card reader updated. Manual reboot may be required to complete the update.")
 .setCancelable(false)
 .setPositiveButton("OK", (dialog, id) -> dialog.dismiss());
 builder.show();
 }
}
```

### Objective-C (iOS)

```objc
// callback method in ECLCardReaderDelegate
- (void)cardReaderShouldManuallyReboot:(id<ECLCardReaderProtocol>)cardReader didUpdate:(BOOL)didUpdate {
 if (didUpdate) {
 NSString *title = @"Manual Reboot";
 NSString *message = @"Card reader updated. Manual reboot may be required to complete the update";
 UIAlertController *alert = [UIAlertController alertControllerWithTitle:title message:message preferredStyle:UIAlertControllerStyleAlert];
 UIAlertAction *ok = [UIAlertAction actionWithTitle:@"OK" style:UIAlertActionStyleDefault handler:nil];
 [alert addAction:ok];
 dispatch_async(dispatch_get_main_queue(), ^{
 [self presentViewController:alert animated:YES completion:nil];
 });
 }
}
```

Moby/5500

Alliance Offers

Data as a Service

Invitation to Apply

Accounts

Bank Holidays

Card Activation

Card Controls

Challenge-Widget

Commercial Credit Cards

Commercial Statements

Credit Card Account Details

Credit Card Accounts Overview

Credit Card Alerts

Credit Card Application Status

Credit Card APRs

Credit Card Balance Transfers

Credit Card Disputes

Credit Card Payments

Credit Card Qualified Offers

Credit Card Statements

Credit Card Transactions

Data Sharing for Marketing Purposes

Digital Wallets

Make a Payment - Coming Soon

Rewards Accelerator

Rewards Automatic Redemption

Rewards: Balance Summary

Rewards: Dashboard

Rewards Redemption Accounts

Rewards Redemptions

Rewards Transactions: Earned and Redeemed

Travel Notifications

User Profile

3DSecure2

Avvance

CheckoutJs

Commerce SDK

Converge

Disputes Management

Dynamic Currency Conversion

eBoarding

Elavon Cloud Payments Interface

Elavon Payment Gateway

Fusebox

Hosted Payment Page

In Person Payments on Opayo

Leads

Lightbox payment modal

Online Payments on Opayo

Opayo

Opayo Direct

Opayo Forms

Opayo Reporting API

Opayo Server

Opayo Shared API

Payment Method Gateway

Payments Core 365

Simplify

viaconex

XML API

Card as a Service API

Core Banking API

Money Movement API

Reference API

Access Online Transactions

Account Transfers

Account Validation

ACH Originations

Bank Information

Card as a Service

Check Payables

Corporate Account Information

Corporate Account Information 3LO

Corporate Credit Cards

Corporate Onboarding

Corporate Statements

Custody

Data Toolbox

Data Toolbox - Accounts

Data Toolbox - Documents

Data Toolbox - Transactions

Debit Card Phone Number Lookup

Disbursements via Zelle®

U.S. Bank Flexible Capital Platform

Freight Payment Customer Profiles

Freight Payment Transactions

Incoming Webhooks

Instant Payments

Investment Accounting

PaySmart

Payee Choice

Payee Token+

Personal Loans

Positive Pay

Push to Card

Receivables

RTP® - Real-Time Payments

Tokenized Payments

Treasury Builder

U.S. Bank FBO Account

Virtual Account Reporting

Virtual Card Payments

Voyager Accounts

Voyager Cards

Voyager Drivers

Voyager Transactions

Voyager Vehicles

Wire Transfers

Elavon Commerce SDK Overview

Integration Methods

Commerce Web Services

Java (Windows)

Java (Android)

Objective-C (iOS)

System

Get Environment Information

Get Converge Account Information

Validate BMS Credentials

Payment Terminals

Payment Terminals Overview

Ingenico

iCMP

iPP320

iSC250

Lane/3000

Lane/3600

Lane/5000

Link/2500

RP457c

Self/4000

Card Reader Connection

Device Connection Criteria

Card Reader Configuration

Get Card Reader Information

24-Hour Reboot

On-Demand

Get Device Status

Reset Card Reader

Reboot Card Reader

Encrypted Card Read

Cancel Card Read

Prompt PIN Entry

Capture Card Data

Get Customer Input

Phone Number

Volume Control

Set Shutdown Timeout

Signature Capture

Set Time Zone on Card Reader

TMS Update Check Time Window

SSL Certificate Update Process for Card Reader

Printers

Printers Overview

Get Printer Information

Print Receipts

On Demand Print Receipt

Transaction Types

Transactions Overview

Sale

Auth Only

Auth Only Increment

Convert Auth Only to Sale

Auth Only Reversal

Void

Linked Refund

Stand Alone Refund

Debit Balance Inquiry

Post Auth Tip Adjust

Continue Transaction

Cancel Transaction

Transaction Lookup

Processing Options

Processing Options Overview

Address Verification Service

Force Sale

Gratuity

Manual Card Data Entry

Merchant Transaction Reference

Partial Approval

Token Request

Pay with Token

Retrieve CVM Signature

Invoice Number

Lane Number