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

Establish an adequate http timeout value to prepare for delays or connection issues. Elavon recommends setting the timeout value to 60 – 120 seconds.

## Step 1. Request format
In XML API, you must include system fields marked as required. Required fields are determined by the transaction type :magic-link[`ssl_transaction_type`]{id="transaction-types"}. If you receive any errors while testing, refer to the :magic-link[Error codes]{id="error-codes"} page for more details.

XML supports content type application/x-www-form-urlencoded where the XML-formatted request is assigned to a single value. 

| Key | Value |
|--------------------|---------------------------------------|
| xmldata | ```<txn><ssl_merchant_id>my_merchant_id</ssl_merchant_id><ssl_user_id>my_user_id</ssl_user_id><ssl_pin>my_pin</ssl_pin></txn> ``` |

**Example format**
```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>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_txn_id>******</ssl_txn_id>
</txn>'
```
## Step 2. Encoding
XML has a special set of characters that cannot be used in normal XML strings. Special characters must be XML encoded to avoid problems. 

For example, this XML string is invalid: `<ssl_company>A & B Company</ssl_company>`

And this XML string is valid: `<ssl_company>A & B Company</ssl_company>`

The following special characters should be XML encoded: 

- Control characters (values 0x01 to 0x1f, and 0x7f) 
- 8-bit ASCII values (values > 0x7f) 
- Any of the following characters: 
 - ' ' (space character) 
 - '"' (double quote) 
 - '#' (hash or pound) 
 - '<' (less than) 
 - '>' (greater than) 
 - '\' (back slash) 
 - '^' (circumflex) 
 - '`' (backquote) 
 - '{' (left squiggly bracket or brace) 
 - '|' (vertical bar) 
 - '}' (right squiggly bracket or brace) 

## Step 3. Build your payment page
**Best Practices**
- Your credentials must be kept secure. Elavon strongly recommends passing and storing Converge credentials through server-side code instead of client-side code. 
- Always submit data to Converge through Hyper Text Transfer Protocol Secure (HTTPS) using the POST method. 
- Request parameters should be included in the body of the message. Do not put request parameters in the request url.

### Processing rates, fraud and chargebacks
There are several options to lower credit card processing rates and minimize fraud/chargebacks while building your payment page.

**Address Verification Service (AVS)**

To qualify for better rates, you should pass `ssl_avs_address` and `ssl_avs_zip` in the :magic-link[/processxml.do]{id="api-reference#tag/Process-Transaction-Online"} request. AVS information is compared to the cardholder‘s ZIP code and address that the card issuer has on file. Address and ZIP code mismatches help the merchant decide whether to complete the transaction. Refer to the AVS Response Codes section for complete list of :magic-link[AVS Response Codes.]{id="response-codes#avs-response-codes"} 

**Card Verification Value (CVV)** 

For fraud protection, you should pass `ssl_cvv2cvc2` and `ssl_cvv2cvc2_indicator` in the :magic-link[/processxml.do]{id="api-reference#tag/Process-Transaction-Online"} request. The CVV field can be set as optional or required based on business needs. When CVV data is passed, it is compared to the cardholder‘s CVV data that the card issuer has on file, a CVV Response Code is then returned. Refer to the CVV2/CVC2 Response Codes section for complete list of :magic-link[CVV2/CVC2 Response Codes.]{id="response-codes#cvv2cvc2"} 

If the CVV value is set to required: 

- A valid CVV value must be passed along with `ssl_cvv2cvc2_indicator = 1` 
- If a CVV indicator isn't passed but a CVV value is, Converge will default to the CVV indicator to `ssl_cvv2cvc2_indicator = 1`

If the CVV value is set to optional: 

- A CVV value along with the appropriate `ssl_cvv2cvc2_indicator` may be passed to indicate if the CVV is present, bypassed, illegible or not present. 
- The Converge application will set the indicator to `ssl_cvv2cvc2_indicator = 1` if the CVV value is passed or Bypassed (0) if the CVV value is not passed at the time of the authorization. 

**Doing Business As (DBA)**

Dynamic Doing Business As (DBA) provides merchants with the ability to control the descriptor on their customer's credit card statements. It allows the merchant to specify, on a per-transaction basis, wording that may be more recognizable or more service-specific to the customer than their usual business name, preventing chargebacks. As an example, if the merchant sells magazine subscriptions for multiple publications, they may prefer to include the name of the publication in the authorization: MANYMAG*BAKERS MONTHLY or MANYMAG*CAR DIGEST. 

DBA is up to 25 characters constructed in the following format: 

- Constant/prefix (3, 7, or 12 fixed alphanumeric value) with asterisks (*) delimiter. 
- DBA name passed by the application. The maximum allowable length of the DBA Name variable provided by the merchant can be 12, 17, or 21 based on the length setup for the constant. 

With DBA, you can include the `ssl_dynamic_dba` parameter in the :magic-link[/processxml.do]{id="api-reference#tag/Process-Transaction-Online"} request of the following transactions: 

- Credit Card Sale 
- Credit Card Authorization Only 
- Credit Card Add Recurring 
- Credit Card Add Installment 
- Credit Card Generate Token 

#### **Manage Fraud**
Log in to the [Converge demo environment](https://demo.convergepay.com/converge-webapp/#!/login) to review your configuration options.

#### Fraud prevention rules
- Go to **Settings > Fraud Prevention Rules** to see our standard options. See ["Fraud rules for eCommerce Converge customers"](https://support.convergepay.com/s/article/Fraud-Rules-for-eCommerce-Converge-Customers) for more details.
- To set up customized rules, go to **Settings > Fraud Prevention Rules > Custom Rules.** See [Custom fraud rules](https://support.convergepay.com/s/article/Add-Custom-Rules) for additional information. Set up a duplicate check rule in the terminal to prevent processing the same transaction more than one time.

#### HTTP Referrers
- Go to **Settings > System Setup Support** to configure HTTP referrers on terminals to only accept transactions from a pre-approved list of websites. 

#### 3D Secure
Protect from exposure to fraud and prevent unauthorized transactions using :magic-link[3D Secure]{id="3d-secure-2"}. 3D Secure shifts liability for chargebacks for fraudulent transactions from merchants onto the card issuer.

Build payment page

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

Fees

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