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

## USB on the go (OTG) requirements 

- RP457c firmware must be 8.55 or later.
- Android device must support USB OTG connectivity.
- USB OTG adapter must be used to connect using USB.

:::::notice{note}

- USB OTG connecter cannot be used to establish bluetooth pairing. Only audio connection can be used to establish a trusted bluetooth connection.
- RP457c will not charge over the USB OTG connecter or audio connection.
:::::

## Pairing a ROAM RP457c card reader 

If you are using a ROAM RP457c reader, in addition to the audio connection, you can also pair the reader to your device over a Bluetooth connection. In order to do this, you must first connect over the audio connection. While you have this connection maintained, you will be able to pair over bluetooth using the card reader interface provided to you when you first made the audio connection. Once you pair the ROAM reader over bluetooth, you can unplug the reader from the audio jack and the next connection that you make will be over bluetooth.

:::::notice{note}

Pairing can only occur when connected via audio jack. USB On the Go connections do not support pairing.
:::::


### Java 

When pairing to Android devices, you will first connect the RP457c via audio jack. Once the audio connection completes, you may pair the RP457c via Bluetooth by using the `findPairableDevices` call to search for any pairable devices, followed by the pair command to actually complete the pairing process. When you attempt to pair the device, you will get a system prompt from Android for you to confirm a passkey to pair the RP457c. Select **Ok** from this prompt to complete the pairing process. Once you have succesfully paired your RP457c device, you can connect via Bluetooth without having to use the audio connection going forward. If a paired RP457c device is plugged into the Android device, the audio connection will be used instead of Bluetooth.

#### Code sample - Simplified flow

Refer to the sample application source code for more information.

```java
account.getCardReaders().findPairableDevices(new ECLDevicesSearchingListener()
{
 @Override
 public void uponSearchingDevice(ECLConnectionMethod eclConnectionMethod)
 {
 }

 @Override
 public void devicesSearchFound(String name, ECLDeviceConnectionType eclDeviceConnectionType)
 {
 }

 @Override
 public void devicesSearchDone(final List<ECLDeviceSearchResult> list)
 {
 handler.post(new Runnable()
 {
 @Override
 public void run()
 {
 if (list.size() > 0)
 {
 List<String> deviceNames = new ArrayList<>();
 for (ECLDeviceSearchResult result : list)
 {
 deviceNames.add(result.getName());
 }

 // For simplified flow, just use first pairable search result found
 ECLDeviceSearchResult searchResult = list.get(0);
 ECLDeviceInterface deviceInterface = account.getCardReaders()
 .setDeviceToUse(searchResult.getName(), searchResult.getConnectionTypes());

 if (deviceInterface != null)
 {
 deviceInterface.pair(new ECLDevicePairingListener()
 {
 @Override
 public void devicePairingSucceeded(ECLDeviceInterface device)
 {
 if (device instanceof ECLCardReaderInterface)
 {
 showMessage(((ECLCardReaderInterface) device).getName() 
 + " Paired Succesfully");
 }
 else
 {
 showMessage("Paired!");
 }
 }

 @Override
 public void devicePairingFailed(ECLDeviceInterface device, final ECCError error)
 {
 showMessage("Failed to pair: " + error.getDebugDescription());
 }

 @Override
 public void devicePairingProgress(ECLDeviceInterface device, 
 final ECLTransactionProgress progress)
 {
 handler.post(new Runnable()
 {
 @Override
 public void run()
 {
 displayMessageInProgressView(
 "device pairing Progress: " + progress.toString(), false);
 }
 });
 }
 });
 }
 }
 else
 {
 showMessage("No card readers to pair");
 }
 }
 });
 }
}, 30);
```

### Objective-C 

When pairing to iOS devices, you will have to follow slightly different steps from Android devices. After you call the pair fuction on the card reader, you need to exit your application and go to the iOS settings of your device. Under the bluetooth settings, you would click on the ROAM device that you want to pair. At this point, Commerce SDK will call one of the delegate methods of the pair function - `devicePairingPasscode:(NSString *)passcode`, which contains the passcode that iOS will ask you to match. One way to display this passcode to the user would be to use a `UILocalNotification` sent by your application when the user clicks on the ROAM device they want to pair. You can see the example code below.

Once the user confirms that the passcode is correct, the iOS device should display *Connected*  in the BT settings. At this point the user can go back to the application, unplug the ROAM reader from the audio jack, and connect over bluetooth.

:::::notice{note}

In order for your application to communicate to the ROAM reader over audio and bluetooth, you need to set several properties in your Xcode project. Refer to **Step 8** of *Set Up the Xcode Project to Use Commerce SDK* on the *Objective-C (iOS)* page to see which properties need to be set.
:::::

#### Code sample - Simplified flow

Refer to the sample application source code for more information.

```objc
// get the card reader instance that currently holds an audio connection
// you will have this if you connected over the transactional API or via findDevices
id<ECLCardReaderProtocol> cardReader = [[_account cardReaders] selectedDevice];
// call the pair function
[cardReader pair:self];
// in this case we made the current class receive the pair callbacks (note the reference to "self" above)
...
// the implementation of the pair callback
+ (void)devicePairingSucceeded {
 dispatch_async(dispatch_get_main_queue(), ^{
 [self addStatusString:@"Reader paired\n"];
 });
}

+ (void)devicePairingFailed {
 dispatch_async(dispatch_get_main_queue(), ^{
 [self addStatusString:@"Reader pairing failed\n"];
 });
}

+ (void)devicePairingNotSupported {
 dispatch_async(dispatch_get_main_queue(), ^{
 [self addStatusString:@"Reader pairing not supported\n"];
 });
}

// this will get called when the user clicks on the roam device they want to pair in the iOS bluetooth settings
// iOS will display a passcode which should be the same as the one returned here
+ (void)devicePairingPasscode:(NSString *)passcode {
 dispatch_async(dispatch_get_main_queue(), ^{
 // send a notification to the user so they know the passcode matches the one displayed by iOS in the BT settings
 UILocalNotification *notification = [[UILocalNotification alloc] init];
 notification.alertBody = passcode;
 [[UIApplication sharedApplication] presentLocalNotificationNow:notification];
 });
}

```

RP457c

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

Moby/5500

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