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

Force sale is the ability to process a transaction using the voice authorization number provided by the creditor.

Occasionally, a card transaction will not automatically process and will prompt the merchant to call the creditor for a voice authorization.

## Code samples

### CWS 

#### Request

| Property | Description |
| --- | --- |
| parameters JSONObject required | All relevant parameters for Force sale processing. |
| forceTransaction boolean optional | Force sale indicator Indicates whether to force sale the transaction. Valid values:<ul><li>True</li><li>False</li></ul>*Note:* You will need to supply a voice referral. |


#### Example

##### Request

```json
{
 "method" : "startPaymentTransaction",
 "requestId" : "2101936245",
 "targetType" : "paymentGatewayConverge",
 "version" : "1.0",
 "parameters" : {
 "paymentGatewayId" : "4c45c792-0513-4218-8b6d-c5ff7039a22e",
 "transactionType" : "SALE",
 "tenderType" : "CARD",
 .....
 "forceTransaction" : true
 .....
 }
}
```

After receiving the request for voice referral, issue this request.

```json
{
 "method" : "continuePaymentTransaction",
 "requestId" : "2101936247",
 "targetType" : "paymentGatewayConverge",
 "version" : "1.0",
 "parameters" : {
 "VoiceReferral" : "321zxc",
 "paymentGatewayId" : "4c45c792-0513-4218-8b6d-c5ff7039a22e",
 "chanId" : "eb5fcc9f-07db-40a6-9711-6c2bda9a26b9"
 }
}
```

##### Response

```json
{
 "requestId" : "2101936246",
 "statusDetails" : "REQUEST_ACCEPTED",
 "data" : {
 "paymentGatewayCommand" : {
 "completed" : false,
 "eventQueue" : [ ],
 "chanId" : "eb5fcc9f-07db-40a6-9711-6c2bda9a26b9",
 "requiredInformation" : [ "VoiceReferral" ]
 }
 }
}
```

### Java 

```java
ECLCardTenderInterface cardTenderInterface= account.getTransactionProcessor().createCardTender();
cardTenderInterface.requiresVoiceReferral();
account.getTransactionProcessor().processTransaction(transaction, cardTenderInterface, transactionListener);
```
During the transaction, you will get a callback from `shouldProvideInformation` and you can check the `tenderRequires` parameter to verify that a referral code is needed. Provide the referral code to Commerce SDK and then call `continueTransaction`. 

This code takes place inside the `shouldProvideInformation` callback.

```java
if (tenderRequires.getRequiresVoiceReferral() != ECLVoiceReferralRequirement.NOT_REQUIRED)
{ 
 // give your voice referral code to CSDK
 ((ECLCardTenderInterface)tender.setVoiceReferralHandledAndApproved("321"); 
}
// ask CSDK to continue with the transaction
account.getTransactionProcessor().continueProcessingTransaction(transaction, tender, transactionListener);
```

### Objective-C 

Using the same code from the Sale transaction with a card tender, the only addition we need to do before processing the transaction is:

```objc
[tender setRequiresVoiceApproval];
```

Once you have set the `setRequiresVoiceApproval` on the card tender, `ECLTransactionProcessingDelegate::shouldProvideInformation` will be called with `requiresVoiceApproval` set on the `tenderRequirements`. You can then show some UI for the merchant to enter the voice approval code and do the following:

```objc
[tender setVoiceReferralHandledAndApproved:approvalCode];
[transactionProcessor continueTransaction:transaction using:tender delegate:delegate];
```

### C\# 

```c#
PaymentArgs bea = new PaymentArgs();
...
bea.forced = true;
...
m_CWS.StartPaymentTransaction(bea, MyNotifyCWSEvent, MyPaymentComplete);
```

#### Request

Respond to VoiceReferral

```c#
Dictionary<string, string> info = new Dictionary<string, string>();
info["VoiceReferral"] = theVoiceReferral;

PaymentTransactionResults tr = m_CWS.ContinuePaymentTransaction(m_PaymentGatewayId, chanId, info, MyNotifyCWSEvent);
```

#### Response

```c#
public void MyPaymentComplete(PaymentResults ber)
 {
 String[] req = ber.getRequiredInformation();
 if (null != req) /* expect "VoiceReferrel" */
```

Force sale

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

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