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.

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

Elavon Financial Services DAC. Registered in Ireland – Number 418442.
Registered Office: Block F1, Cherrywood Business Park, Dublin 18, D18 W2X7, Ireland.
Elavon Financial Services DAC, trading as Elavon Merchant Services, is regulated by the Central Bank of Ireland.
 
Elavon Financial Services 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.
Elavon Financial Services 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.

POS can call this to check that BMS Credentials (bmsUsername and bmsPassword) are valid.


## Code Samples

### CWS 

#### Request

```json
{
 "method" : "validateBmsCredentials",
 "requestId" : "7571358",
 "targetType" : "paymentGatewayConverge",
 "version" : "1.0",
 "parameters" : {
 "paymentGatewayId" : "6f95a650-b56f-4b45-88d6-b2f53d55e4f6"
 }
}
```

#### Response - credentials are valid

```json
{
 "requestId" : "7571358",
 "statusDetails" : "REQUEST_ACCEPTED",
 "data" : {
 "paymentGatewayCommand" : {
 "completed" : true,
 "eventQueue" : [ ],
 "paymentTransactionData" : {
 "result" : "SUCCESS"
 },
 "warnings" : [ ]
 }
 }
}
```

#### Response - credentials are invalid 

```json
{
 "requestId" : "7571361",
 "statusDetails" : "REQUEST_ACCEPTED",
 "data" : {
 "paymentGatewayCommand" : {
 "completed" : true,
 "eventQueue" : [ ],
 "paymentTransactionData" : {
 "result" : "FAILED",
 "errors" : [ "ECLCommerceError ECLAccountInvalidCredentials" ]
 },
 "warnings" : [ ]
 }
 }
}
```

### Java

Create an instance of *com.elavon.commerce.ECLAccountValidationListener*, as shown below.

```java
// The following code is copied from MainActivity.java in the sample application code.
// The code displays results on UI.
 
ECLAccountValidationListener delegate = new ECLAccountValidationListener()
{
 @Override
 public void accountDidValidate(ECLAccountInterface eclAccountInterface)
 {
 displayMessageInProgressView("validate BMS Credentials - succeeded", false);
 }
 
 @Override
 public void accountDidFailToValidate(ECLAccountInterface eclAccountInterface, ECCError eccError)
 {
 displayErrorInProgressView("validate BMS Credentials - failed", eccError);
 }
};
```

Then pass the instance to method `validateBmsCredentials` on interface `com.elavon.commerce.ECLAccountInterface`. CSDK internally validates the combination of bmsUsername and bmsPassword provided by the POS.

If the BMS cannot validate the credentials, *ECLCommerceError.Codes.ECLAccountInvalidCredentials* will be returned in *ECLAccountValidationListener.accountDidFailToValidate*.

```java
TransactionSavedState.INSTANCE.account.validateBmsCredentials(delegate);
```

### Objective-C

Create a class implementing the ECLAccountValidationDelegate protocol and implement the methods accountDidValidate and accountDidFailToValidate, as shown below.

```objc
@interface ValidateBmsCredentialsDelegate : NSObject<ECLAccountValidationDelegate>
 
@property MainViewController *mainViewController;
 
@end
 
@implementation ValidateBmsCredentialsDelegate
 
- (void)accountDidValidate:(id<ECLAccountValidationDelegate>)delegate {
 [_mainViewController addStatusString:@"BMS credentials validated\n"];
}
 
- (void)accountDidFailToValidate:(id<ECLAccountValidationDelegate>)delegate error:(NSError *)error {
 [_mainViewController addStatusString:[NSString stringWithFormat:@"BMS credentials failed to be validated: %@\n", [error debugDescription]]];
}
 
@end
```

Then, pass an instance of the delegate to the method *validateBmsCredentials* of protocol *ECLAccountProtocol*. CSDK internally validates the combination of bmsUsername and bmsPassword provided by the POS.

If the BMS cannot validate the credentials, an ECLError with code *ECLAccountInvalidCredentials* will be returned in accountDidFailToValidate.

```objc
// inside MainViewController implementation
 
id<ECLAccountValidationDelegate> delegate = [[ValidateBmsCredentialsDelegate alloc] initWithMainViewController:self];
[_account validateBmsCredentials:delegate];
```

### C\#

```c#
// Asynchronous
StartValidateBmsCredentials(String paymentGatewayId, NotifyCWSEvent ne, PaymentTransactionComplete ptc) 
 
// Synchronous
PaymentTransactionResults results = m_CWS.ValidateBmsCredentials(String paymentGatewayId);
MyValidateBmsCredentialsComplete(results, results.Warnings);
 
// Do something with the response
public void MyValidateBmsCredentialsComplete(PaymentTransactionResults paymentResults, String[] warnings)
{
 lock (myPaymentCompleteLock)
 {
 Log("----------- Validate BMS Credentials Complete ------------");
```

Validate BMS Credentials

Alliance Offers

Data as a Service

Invitation to Apply

Accounts

Bank Holidays

Card Activation

Card Controls

Commercial Credit Cards

Credit Card Account Details

Credit Card Accounts Overview

Credit Card Alerts

Credit Card Application Status

Credit Card APRs

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 Redemption Coming Soon

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

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

Access Online Transactions

Account Transfers

Account Validation

ACH Originations

Bank Information

Card as a Service

Card as a Service API

Check Payables

Core Banking API

Corporate Account Information

Corporate Credit Cards

Corporate Onboarding

Corporate Statements

Custody

Data Toolbox

Data Toolbox - Accounts

Data Toolbox - Documents

Data Toolbox - Transactions

Disbursements via Zelle

U.S. Bank Flexible Capital Platform

Freight Payment Customer Profiles

Freight Payment Transactions

Instant payments

Investment Accounting

Money Movement API

PaySmart

Payee Choice

Payee Token+

Personal Loans

Positive Pay

Push to Card

Receivables

Reference API

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

Getting Started

Integration Methods

Commerce Web Services

Java (Windows)

Java (Android)

Objective-C (iOS)

System

Get Environment Information

Get Converge Account Information

Payment Terminals

Payment Terminals Overview

Ingenico

iCMP

iPP320

iSC250

Lane 3000

Lane 5000

Link 2500

Moby 5500

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

OAR-PS2000 Data

Healthcare

Dynamic currency conversion

Credit Surcharge

Credit Surcharge Overview

Surcharge Property Retrieval

Token Transaction for Surcharge

Transaction Outcome Field for Surcharge

Transaction Search Result for Surcharge

Surcharge In-App

Service Fee

Service Fee Overview

Service Fee Property Retrieval

Token Transaction for Service Fee

Transaction Outcome Field for Service Fee

Transaction Search Result for Service Fee

Service Fee In-App