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

Elavon calls the API Fields 1000, 1003, 1004, 1009, 1010, 1022, 1023, 1024 and 1036 “the Final 9.” The messages returned in these fields indicate the success or failure of the transaction.

 ## Field and description definition

 
|API Field/Field name|Description|
|----|------|
| 1000 - Card Type | Two character abbreviation of the card type. **Valid values for credit card transactions** - AX - American Express - MC - Master Card - VI - Visa - DI - Discover - DC - Diner's Club - JC - Japanese Credit Bureau **Valid values for other tender types** - DB - Debit - EB - Electronic Benefit Transfer - CK - Check - SF - Synchrony Financial Private Label Cards - GV - Givex Gift Cards - VL - Valulink Gift Cards - VC - Valutec Gift Cards - SV - Stored Value Gift Cards|
|1003 - Elavon Gateway Response Code|Code (up to 4 characters) that allows the POS application to determine the result of the transaction. See examples :magic-link[below]{id=#example-fusebox-responses-for-field-1003}.|
|1004 - Host Response Message | This message is the TPP or host (or system external to the Elavon Gateway) mapped to the value returned in API field 1009 to provide a verbose response.|
|1009 - Host Response Code | This code is the TPP or host code passed back to the Elavon Gateway application.|
|1010 - Elavon Gateway Response Message | The verbose description of the Elavon Gateway response code from an internal table.|
| 1022 - Card Issuer Response Code| Code returned from the card brand issuer that indicates the reason a transaction was unsuccessful and what further actions may be taken. * If this field is returned, the POS must evaluate API field 1000 to determine the card type and display the card type and card issuer response code to the end user. * Merchants must then follow the rules and guidelines for that response code established by the card brand.|
| 1023 - Card Issuer Response Text| A brief text description explaining the transaction status based on the corresponding Issuer Response Code returned in field 1022. * Merchants must take the appropriate action in accordance with card brands' rules and guidelines.|
| 1024 - Merchant Advice Code| Code returned from the authorization host that indicates the reason a transaction was unsuccessful and what further actions may be taken. * If this field is returned, the POS must evaluate API field 1000 to determine the card type and display the card type and card issuer response code to the end user. * Merchants must then follow the rules and guidelines for that response code established by the card brand.|
| 1036 - Merchant Advice Response Text| A brief text description explaining the transaction status based on the corresponding Merchant Advice Code returned in field 1024. * Merchants must take the appropriate action in accordance with card brand’s rules and guidelines.|


 ## Example Fusebox responses for field 1003 and field 1010

|Field 1003 value| Field 1010 text|Description|
|----|----|----|
|0 or 0000| Successful and Approved| The communication was successful, and any file updates required by this processor were completed successfully. Any value not equal to “0” or “0000” indicates an unsuccessful transaction.|
|0004| COMMUNICATIONS FAILURE| Need official description here.| 
|0005|DUPLICATE ERROR| Need official description here. |
|0007|NO MATCHING RECORDS|If the failure response code does not begin with a ‘-‘ sign, it indicates a system error.) |
|0049|INVALID EXPIRATION DATE FIELD #0004|Indicates expired card.|
|60 or 0060|Successful but Not Approved| The communication was successful, but the Host response did not match the processor's template of an approved or successful transaction. This transaction response likely indicates a “DECLINE” or some other “USER INTERVENTION REQUIRED” response. It is recommended that you don’t retry this transaction again.|

 


:::notice{title="note"}
- If your application provides AVS and CVV2 or CVC2 or CID information as part of the input request, your application should include the appropriate logic to allow the merchant to approve or decline the transaction based on the result code(s). 
- Fusebox has an optional service that can be certified with the POS and activated where AVS and CVV2 or CVC2 or CID values are validated and declined to the POS appropriately.
::: 



 

 ## Third Party Processor responses

 

 When field 1003 = 0060, the transaction was not approved online by the TPP. Often the reason or possible recommended action is provided by the host.

 
|Response text| Description|
 |	----	|	---	|
|	 CALL_AUTH_CENTER_REFERRAL	|	 Contact the third party processor voice authorization center for an approval code. 	|
|	 DECLINED_BY_ISSUER	|	 The card’s issuer declined the transaction. 	|
|	 DUPLICATE_TRANSACTION	|	 The transaction is a duplicate of a previously approved transaction at the host. 	|
|	 EXPIRED_CARD	|	 The expiration date of the card has passed. 	|
|	 FORMAT_ERROR	|	 The transaction does not meet the requirements of the TPP’s message specification or data element format.	|
|	 INSUFFICENT_FUNDS	|	 The card holder has insufficient funds for this transaction.	|
|	 INVALID AMOUNT	|	 The amount of the transaction was invalid.	|
|	 INVALID ACCOUNT	|	 The account number was invalid.	|
|	 INVALID_CVV2_VALUE	|	 The CVV2 value in API field 0050 is incorrect or invalid.	|
|	 INVALID_PIN	|	 The PIN value is incorrect or invalid.	|
|	 INVALID_PROCESSOR_TERM	|	 The terminal number for the merchant was not valid at the processor host.	|
|	 INVALID_TRANS_CODE	|	 The transaction code was invalid.	|
|	 PARTIAL_APPROVAL	|	 The transaction was only approved for a partial amount, check API field 0002 of the response to validate the amount approved.	|
|	 PICK_UP_CARD	|	 The card is to be picked up by the merchant.	|
|	 PIN_RETRIES_EXCEEDED	|	 The number of PIN entry attempts has been exceeded.	|
|	 PLEASE_RETRY	|	 The transaction may be attempted to be authorized again. 	|
|	 PROCESSOR_ERROR	|	 This is a general third party processor error for unspecified reasons. 	|
|	 SERVICE_NOT_ALLOWED	|	 The card is not permitted to be used for this transaction.	|
|	 TRANS_NOT_ALLOWED	|	 The transaction is not permitted for this merchant or cardholder.	|


 

### Sample MasterCard decline
1003 - TERM_RESP_CODE - 0060
1010 - TERM_RESP_TEXT - DECLINED 79
1009 - HOST_RESP_CODE - ND
1004 - HOST_RESP_TEXT - DECLINED 79
1022 - ISSUER_RESPONSE_CODE - 93
1023 - ISSUER_RESPONSE_TEXT - CALL ISSUER
1024 - MERCH_ADVICE_CODE - 02
1036 - MERCH_ADVICE_TEXT - CANNOT APPROVE NOW, TRY AGAIN LATER


### Sample Visa decline
1003 - TERM_RESP_CODE - 0060
1010 - TERM_RESP_TEXT - DECLINED: NSF
1009 - HOST_RESP_CODE - ND
1004 - HOST_RESP_TEXT - DECLINED: NSF
1022 - ISSUER_RESPONSE_CODE - 51
1023 - ISSUER_RESPONSE_TEXT - INSUFFICIENT $$
1024 - MERCH_ADVICE_CODE - 02
1036 - MERCH_ADVICE_TEXT - ISSUER CANNOT APPROVE AT THIS TIME

Message detail

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

Fusebox overview

Getting started

Transaction flow

Transaction sequencing

API message format

Reconciliation

Settlements

Transaction types

Authorization Only (01)

Sale Transaction (02)

Prior-Authorized Sale (07)

Return (09)

Void Sale (11)

Batch Close (13)

Batch Create and Inquiry (14)

Void Return (17)

Transaction Inquiry (22)

Token Request (37)

Full Authorization Reversal (61)

Heartbeat (73)

Incremental Authorization (75)

Partial Authorization Reversal (76)

Concepts

Tokenization

Tokenization introduction

Tokenization API fields

Tokenization scenarios

Example transactions

Error scenarios

Retail

Retail scenarios

Retail API fields

Retail examples

Lodging

Lodging transactions

Lodging API fields

Lodging examples

Credential on file transactions

Best practices

Software conversions

Restaurant

Restaurant transactions

Restaurant API fields

Restaurant examples

Restaurant credential on file transactions

Restaurant receipts

MOTO and eCommerce

eCommerce transactions

MOTO and eCommerce API fields

Ecommerce examples

Direct marketing examples

eCommerce credential on file transactions

EMV transactions

Implementation considerations

Certification

EMV API fields

EMV Public Cap Keys, parameters, and reports

Sample files

EMV receipts

EMV integration samples

API-based settlement

Settlement transactions

API-based settlement fields

API-based settlement examples

Check payment

Check transactions

Check API fields

Check payment examples

DCC transactions

DCC transaction flows

DCC API fields

DCC examples

DCC receipt requirements

DCC certification process

Gift and stored value cards

Gift and stored value card transactions