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

The Credit Card message format is for whole track, Track I or Track II magnetic stripe read credit card data, or key-entered credit card data available for all supported market segments. Magnetic stripe data cannot be sent in the Mail Order/Telephone Order, eCommerce environments, or for recurring transactions.

## Card Data

You must pass one of the following fields:

- Track data in  `ssl_track_data` for swiped transactions.

- The encrypted track data for swiped or Contactless transactions:

    - All Track data in the `ssl_enc_track_data` field captured from the Ingenico device (3DES DUKPT encryption). (Refer to the :magic-link[Encryption]{id="encryption"} section for more information.)

- The card number in the `ssl_card_number` for hand keyed transactions.

- The token in the `ssl_token` from a previously tokenized card number, the expiration date and AVS data is not needed if token is stored in Card Manager.

## Contactless

Indicates that the track data was extracted from a Contactless device when consumers wave or tap their cards or phones (Example: ApplePay), the integrated application must pass the Contactless Indicator in the `ssl_pos_mode` of 03 (proximity capable). Those values default to swiped when track data is sent alone.

## Address Verification Service (AVS)

An integrated application should pass the Address Verification Service (AVS) data on hand key transactions to qualify for better rates by using the Address Verification Service (AVS). AVS captures ZIP codes and the cardholder‘s billing address. 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 to decide whether or not to complete the transaction. Refer to the :magic-link[AVS Response Codes]{id="avs-codes"} section for complete list of AVS Response Codes.

## Card Verification Value (CVV)

An integrated application should pass the Card Verification Value (CVV) on hand key transactions for fraud protection. The CVV field can be set as optional or required based on the merchant’s 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 :magic-link[CVV2/CVC2 Response Codes]{id="cvv2-cvc2-codes"} section for complete list of CVV2/CVC2 Response Codes.

If the CVV value is set to required:

- A valid CVV value must be passed along with a CVV indicator of present (1) at the time of the authorization.

- If a CVV value isn't passed, Converge will default the indicator to present if no indicator is passed and a CVV value is present.

If the CVV value is set to optional:

- A CVV value along with the appropriate CVV indicator may be passed to indicate if the CVV is present, bypassed, illegible or not present.

- The Converge application will set the indicator to present (1) if the CVV value is passed or Bypassed (0) if the CVV value is not passed at the time of the authorization.

## Recurring

You can set up set up recurring or installment payments in the system for all market segments. There are a few things to keep in mind when setting up a recurring or installment payment:

- Recurring transactions will run indefinitely, unless suspended by the user.

- Installment transactions will run until the number of installments specified is reached.

- No track, Track I, or Track II magnetic stripe reads are allowed when setting up recurring payments for credit cards.

- CVV data cannot be passed, as it should not be stored in the system.

## Tip Processing

You can pass tips on *Service* market segment at the time of the authorization Cashier-based processing or after authorization Server-based processing. Optionally a server ID and shift ID can be passed as well.

On the initial transaction, the tip amount must be sent along with the transaction amount. The authorization amount is now the total amount, which is recalculated using the authorization amount originally sent and the new tip provided. The settlement amount will reflect the new authorized amount.

- Authorization Amount = Amount + Tip Amount

- Settlement Amount = Authorization Amount  

After the initial transaction, the tip amount must be sent without the transaction amount. The authorization amount will not change. However, the total amount is recalculated using the original authorized amount and the new tip provided. The settlement amount will reflect the new total amount.

- Settlement Amount = Authorization Amount + Tip Amount

- The tip amount can be sent in the merchant or the cardholder currency  

EMV-based transactions handle tips differently. Refer to the :magic-link[EMV Credit/Debit Card Transactions]{id="emv-card"} sections for more information.

## Doing Business As (DBA)

The Dynamic Doing Business As (DBA) provides merchants 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) configured in the terminal 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.

## Travel Data

Converge supports the ability to capture and send travel information regarding departure and completion dates. The travel information dates are sent to the Merchant Airline Risk Monitoring System (MARMS). MARMS is a tool used to monitor risk associated with merchants that collect or accept payments for future services or bookings made well in advance of the actual date of use. Both dates must be sent together and cannot be in past.


Credit Card Transactions Overview

Alliance Offers

Data as a Service

Invitation to Apply

Accounts

Alicia Regan AZ Testing

alicia testing

Bank Holidays

Credit Card Activation

Credit Card Application Status

Credit Card Qualified Offers

Credit Card Transactions

Rewards Accelerator

Rewards Automatic Redemption

Rewards Redemption Accounts

Account Transfers

Checkout JS

CheckoutJs

commerce-sdk

Converge

Converge 2

disputes-management

eboarding

eBoarding EU

Elavon Cloud Payments Interface

Elavon Payment Gateway

Fraud Services

fusebox

Hosted Payment Page

Leads

Leads-not-in-use

Leads Referral

Lightbox payment modal

New Product

Opayo

Opayo Pi

Opayo Retail Cloud

Opayo Server

Simplify

XML API

Automation testing - Tharun

Card as a Service API

Core Banking API

Money Movement API

Reference API

Account Validation

ACH Originations prad

Avvance Connect

Avvance Express

Avvance Flex

Card as a Service

Card Controls

Check Payables

Corporate Account Information

Corporate Credit Cards

Custody

Data Toolbox

Disbursements via Zelle

Flexible Capital Platform

Foreign Exchange

Incoming Webhooks

PaySmart

Payee Choice

Positive Pay

Receivables

RTP® - Real-Time Payments

U.S. Bank Flexible Capital Platform

Virtual Account Reporting

Virtual Card Payments

Wire Drawdowns

Wire Transfers

Converge Overview

Getting Started

Transaction Types

Sale - ccsale

Auth only - ccauthonly

Auth Only Increment - ccauthonly

Verification - ccverify

Balance inquiry - ccbalinquiry

Return - ccreturn

Void - ccvoid

Completion - cccomplete

Delete - ccdelete

Update tip - ccupdatetip

Signature - ccsignature

Add recurring - ccaddrecurring

Update recurring - ccupdaterecurring

Delete recurring - ccdeleterecurring

Submit recurring payment - ccrecurringsale

Add installment - ccaddinstall

Update installment - ccupdateinstall

Delete installment - ccdeleteinstall

Submit installment payment - ccinstallsale

Credit card force - ccforce

Credit Card Credit - cccredit

Merchant Hosted Card On File

Debit Card Transactions

Debit Card Transactions Overview

Purchase - dbpurchase

Return - dbreturn

Auth Only - dbauthonly

Auth only Increment - dbauthonly

Complete - dbcomplete

Reverse - dbreverse

Debit - dbvoid

Delete - dbdelete

Inquiry - dbbainquiry

PINless bill pay - pldbillpay

Pinless debit purchase - pldpurchase

BIN Lookup - binlookup

Straight Send

Cash Tender Transactions

Cash Tender Transactions Overview

Sale - cashsale

Credit - cashcredit

EMV Credit/Debit Card Transactions

EMV card transactions overview

Sale - emvchipsale

Auth Only - emvchipauthonly

Swipe sale - emvswipesale

Swipe auth only - emvswipeauthonly

Card update - emvchipupdatetxn

Reversal - emvreverse

Key exchange - emvkeyexchange

Legacy key exchange - caddbkeyexchange

Interac Refunds

Return - emvchipreturn

EMV DCC check - emvdcccheck

EBT Transactions

EBT transactions overview

Food stamp benefits

Purchase - fspurchase

Return - fsreturn

Inquiry - fsbainquiry

Force purchase - fsforcepurchase

Force return - fsforcereturn

Cash benefits

Purchase - cbpurchase

Inquiry - cbbainquiry

Gift Card Transactions

Gift Card Transactions Overview

Activation - egcactivation

Sale or Redemption - egcsale

Refund - egccardrefund

Replenishment or Reload - egcreload

Balance inquiry - egcbalinquiry

Credit - egccredit

Generate token - egcgettoken

Card Manager Transactions

Card Manager Transactions Overview

Token query - ccquerytoken

Token update - ccupdatetoken

Generate token - ccgettoken

Token delete - ccdeletetoken

Merchant Managed Card Tokens

End of Day Transactions

End of Day Transactions Overview

Transaction email - txnemail

Transaction query - txnquery

Total or Summary - total

Settle - settle

Settlement query - stlquery

Recurring Query - recurringquery

Batch Import Transactions

Batch Import Transactions Overview

Batch Import Transaction Query - bitxnquery

Batch import - ccimport

Batch Import File Format

Information batch import - cctokenimport