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

## Service fees

Converge can associate a service fee with any credit card. Converge can use service fees to charge the transaction amount and service fee amount separately. The payment form and confirmation receipt will list both amounts for the cardholder's records. 

Converge also provides the option to display an acceptance page for terms and conditions. 

**Requirements** 

Service fee transactions obey the following rules: 

- Service fee is enabled. Verify by calling :magic-link[/VirtualMerchantDemo/accountxml.do]{id="api-reference#tag/Terminal-Management"} with transaction type `terminalsetup`. 
- The service fee is processed before the main transaction. 
- The service fee is non-refundable after the main transaction finishes processing. 
- If the service fee transaction declines or fails to process, the main transaction also declines. 
- If the main transaction declines or fails to process, the service fee immediately refunds to the payee's account. 

:::::notice{note}
The default service fees are set up during account creation. Please contact Elavon Software Technical Support if custom amounts are required. 
:::::

The following credit card transactions support service fees: 

- `ccsale` (Credit card sale) 
- `ccauthonly` (Credit card authorization only) 

Service fees are automatically set up for all transactions that meets the general requirements for using service fees with Converge. Complete your integration using the integration guide and Converge will begin applying service fees. 

## Surcharges 

A surcharge is a small fee on a credit card transaction a merchant can charge to cover the cost of processing the transaction using credit cards. 

**Requirements** 

Surcharging is available with the following requirements: 

- Surcharge is enabled. Verify by calling :magic-link[/VirtualMerchantDemo/accountxml.do]{id="api-reference#tag/Terminal-Management"} with transaction type `terminalsetup`. 
- Region set to USA 
- Market segment set to one of the following: 
 - Retail 
 - MOTO 
 - Internet 
 - Service 

### Step 1. Surcharge certification requirements 

If you want to use surcharging with XML API, Elavon has the following requirements to certify your application. 

**Disclose Intent to Surcharge** 

You must properly disclose your intent to surcharge to the cardholder. You must present this disclosure at the point-of-sale for the purchase.

*Point-of-entry*
The first page of your application that references credit card brands your application accepts must include notice that your customer will have surcharges applied to their credit card transactions. This notice must be in Arial font at a minimum of 10 points and must be no smaller or less prominent than the surrounding text.

*Point-of-Transaction*
 You must display disclosure on the checkout page of your application. This notice must be in Arial font at a minimum of 10 points and must be no smaller or less prominent than the surrounding text. 

**Disclosure contents**

The disclosures posted at the points of entry and sale must include the following items in their contents. 

- The exact percentage the transaction will apply as a surcharge. 
- A statement that you (the merchant) are assessing the US Credit Card Surcharge and is only applicable to credit card transactions. 
- A statement that the US credit Card Surcharge amount is not greater than the applicable card acceptance cost for credit card transactions. 

**Transaction cancelation** 

For unattended transactions like eCommerce, MOTO, or card present transactions at automated kiosks, the user must have the opportunity to cancel the transaction after they view the surcharge disclosure form. 

**Surcharge maximum** 

The surcharge amount cannot exceed 3% of the original transaction. 

**Surcharges only apply to credit cards** 

Surcharges can only apply to transactions made using a credit card. 

:::::notice{note}
- Because surcharges only apply to credit card transactions, a best practice is to use the BIN lookup transaction type to confirm that the card a cardholder is using for a transaction is applicable. 
- Surcharge is controlled based on the business location. 
:::::

### Step 2. Implement process flow

To apply a surcharge to a card transaction request made through the XML API, you will need to complete the following sequence.

 1. Perform a `binlookup` to confirm that the card is valid for surcharging.
 2. If the `binlookup` confirms that the card is a credit card, alert your customer that they will be surcharged. This step is not required by the API. However, most card association requirements mandate it.
 3. If your customer accepts, initiate a credit card transaction with surcharging enabled.

::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/converge/converge-surcharge-flow.png" alt="Flowchart explaining how to apply surcharge to a card transaction as explained in the above steps "}

**Example of the requests and responses for a successfully applied surcharge**

Send transaction type `binlookup` in the :magic-link[/processxml.do]{id="api-reference#tag/Process-Transaction-Online"} request. 

```curl
curl -X POST 'https://api.demo.convergepay.com/VirtualMerchantDemo/processxml.do' \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 
'xmldata= 
<txn>
 <ssl_transaction_type>BINLOOKUP</ssl_transaction_type>
 <ssl_account_id>my_account_id</ssl_account_id>
 <ssl_user_id>my_user_id</ssl_user_id>
 <ssl_pin>my_pin</ssl_pin>
 <ssl_vendor_id>my_vendor_id</ssl_vendor_id>
 <ssl_card_number>00********0000</ssl_card_number>
 <ssl_exp_date>MMYY</ssl_exp_date>
</txn>'
```

**Bin look up response**

```XML
<txn>
 <cardNumber>00********0000</cardNumber>
 <debit>N</debit>
 <pinless>N</pinless>
 <hsa>N</hsa>
 <billPaymentSupport>N</billPaymentSupport>
 <businessCard>N</businessCard>
 <cardProductTypeCode/>
 <countryCode>000</countryCode>
 <dbIntchFraudInd>N</dbIntchFraudInd>
 <ecommSupport>N</ecommSupport>
 <internationalSupport>N</internationalSupport>
 <networkRoutingCode>AF</networkRoutingCode>
 <posEligible>Y</posEligible>
 <prepaidSupport>N</prepaidSupport>
 <signatureSupport>N</signatureSupport>
 <fundingSource>C</fundingSource>
 <surchargeAllowed>Y</surchargeAllowed>
 <ssl_amount>100.00</ssl_amount>
 <ssl_credit_surcharge_percent>3</ssl_credit_surcharge_percent>
 <ssl_credit_surcharge_amount>3.00</ssl_credit_surcharge_amount>
 <ssl_total_amount>103.00</ssl_total_amount>
</txn>
```

### Step 3. Submit transaction request

Send a `ccsale` or `ccauthonly` in the :magic-link[/processxml.do]{id="api-reference#tag/Process-Transaction-Online"} request. Converge will apply the surcharge percentage set as part of the settings. The response values will reflect the new amount.

```curl
curl -X POST 'https://api.demo.convergepay.com/VirtualMerchantDemo/processxml.do' \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 
'xmldata= 
 <ssl_transaction_type>ccsale</ssl_transaction_type>
 <ssl_account_id>my_account_id</ssl_account_id>
 <ssl_user_id>my_user_id</ssl_user_id>
 <ssl_pin>my_pin</ssl_pin>
 <ssl_vendor_id>my_vendor_id</ssl_vendor_id>
 <ssl_card_number>00********0000</ssl_card_number>
 <ssl_exp_date>1230</ssl_exp_date>
 <ssl_amount>100.00</ssl_amount>
</txn>'
```

**Sample credit card response**

```XML
<txn>
 <ssl_card_number>00********0000</ssl_card_number>
 <ssl_exp_date>1230</ssl_exp_date>
 <ssl_credit_surcharge_percent>3</ssl_credit_surcharge_percent>
 <ssl_credit_surcharge_amount>3.00</ssl_credit_surcharge_amount>
 <ssl_amount>103.00</ssl_total_amount>
 <ssl_result>0</ssl_result>
 <ssl_result_message>APPROVAL</ssl_result_message>
 <ssl_txn_id>101641221593ACBA6-BAFD-76B7-4948-B3DE68CFD0CC</ssl_txn_id>
 <ssl_approval_code>CMC142</ssl_approval_code>
 <ssl_account_balance>1.00</ssl_account_balance>
 <ssl_txn_time>01/20/2023 01:07:23 PM</ssl_txn_time>
</txn>
```

Fees

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

Overview

API reference

Integration guide

Transaction types

Take a payment

End of day transactions

Additional options

Wallets

Point of sale lending

3D Secure 2

Account update

Batch import

Currency conversion

Export scripts

Level III

Non-Elavon certified device

Shopping cart plugins

Billing and invoicing / Hospitality

Authentication

Invoice lifecycle

Managing invoices

Status and error codes

Elavon domains and IP addresses

Response codes and fields

Error codes

Response codes

Supported DCC currency codes

Supported transaction input fields

Test cards

Release notes