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.

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

Elavon Financial Services DAC. Registered in Ireland – Number 418442.
Registered Office: Block F1, Cherrywood Business Park, Dublin 18, D18 W2X7, Ireland.
Elavon Financial Services DAC, trading as Elavon Merchant Services, is regulated by the Central Bank of Ireland.
 
Elavon Financial Services 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.
Elavon Financial Services 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.

Transaction Inquiry (Type 22) performs the following functions:

- Transaction status inquiry in the Elavon Gateway application database.
- Sent after a POS timeout when an error prevents your POS application from receiving or processing the Output Response data from the Elavon Gateway or a communication failure occurs.
- The POS must be able to determine if transaction response is the expected response in the transaction lifecycle (is the amount correct), because the Elavon Gateway application only returns the current state of the last transaction approved.
- By tracking the Elavon token or unique ID, from the original authorization, the Transaction Inquiry does not require the cardholder account number. However, in an error recovery situation, the output response is not returned to the POS application. The POS application Simplify retains the original transaction details until a successful authorization response is received.
- Whenever a transaction status is uncertain, you can run Transaction Inquiry Type 22 to determine whether the transaction exists in the Elavon Gateway application database.
- Transaction does not communicate to a third party processor.
- Transaction type 22 functions without the need for Elavon Gateway applications to reach the host.

Transaction Inquiry searches the Active (Main) database for:

- Reference Number (Field 7).
- Token (Unique ID) or Account Number (Field 3).
- Transaction Amount (Field 2). In the event of a partial authorization request, the amount may differ in the completed transaction.
- If API Field 647=1 in the input request indicates a partial authorization, the system will allow the requested amount.
- Elavon Gateway Terminal ID (Field 109) is provided in the Input Request.
- Original Output Response is returned, if the record is found.
- If the transaction is not found, the transaction can be resubmitted by the POS application for processing.

:::::notice{note}
Elavon Gateway requires that your application support the Transaction Inquiry transaction type.
:::::


The value pair format below is an example of an inquiry on a credit card sale transaction.

**Request**
|API Field/Value|Description|
|---|---|
|1,22,|Transaction Type|
|2,2,50|Transaction Amount|
|3,4012XXXXXXXX1865|Credit Card Number, Token or Unique ID. Token or Unique ID or Account Number can be passed|
|4,1220|Credit Card Expiration Date|
|7,00013455|Reference Number|
|25,030120|Business Date|
|52,0|Transponder and Proximity Indicator|
|60,00000001|Unique Device ID|
|109,TERM1|Terminal ID|
|110,105|Cashier ID|
|115,010|Transaction Qualifier|
|647,0|Partial Authorization Acceptance|
|1008,ID:|Requests Token or Unique ID in Input Request. Masked Account Number in Output Response|
|1105,DOCID:12345678901|Global User Defined Field|
|5002,123456|Device Serial Number|
|8002,LOC1|Location Name|
|8006,CHAIN|Chain Code|

**Response**
|API Field/Value|Description|
|---|---|
|0001,07|Transaction Type|
|0002,2,50|Transaction Amount|
|0003,ID:7234561234561865|Credit Card Number, Token or Unique ID. Token or unique ID or account number can be passed|
|0004,1220|Credit Card Expiration Date|
|0006,000018|Approval Code|
|0007,00013455|Reference Number|
|0009,0010|Host Batch Number|
|0025,030120|Business Date|
|0030,1|Online Indicator|
|0032,030120|Authorization Transaction Date|
|0033,083518|Authorization Transaction Time|
|0034,E|Authorization Characteristics Indicator|
|0035,0100|Validation Code|
|0036,001234567810100|Transaction Identifier|
|0037,5|Authorizer|
|0038,00|Reason Code|
|0040,M|CVV2 or CVC2 or CID Response|
|0043,101910|System Trace Audit Number|
|52,0|Transponder and Proximity Indicator|
|60,00000001|Unique Device ID|
|0070,1111ABC|Customer Code|
|0071,1|Tax1 Indicator|
|0072,1.00|Tax Amount 1|
|0109,TERM1|Terminal ID|
|0110,105|Cashier ID|
|0115,010|Transaction Qualifier|
|0126,0|Track Indicator|
|0128,2.50|Original Authorization Amount|
|0130,2.50|Total Authorized Amount|
|0131,|Total Incremental Authorizations Sent|
|Industry Data|The proper industry data would be supplied and the example is left|
|0632,10.00|Account Balance|
|0700,135020|Billing ZIP Code|
|0701,333 GENESEE STREET|Billing Street Address|
|1000,VI|Card Type|
|1000,VISA|Card Name|
|1004,AP|Final Four Host Response Message|
|1005,7993241|Merchant Number|
|1008,401288******1865|Requests token or Unique ID in Input Request. Masked Account Number In Output Response|
|1009,000|Host Response Code|
|1020,A|AVS Response Code|
|1105,DOCID:12345678901|Global User Defined Field|
|5002,123456|Device Serial Number|
|7007,12345678901234567|Fusebox Transaction Identifier|
|8002,LOC1|Location Name|
|8006,CHAIN|Chain Code|


Transaction Inquiry (22)

Alliance Offers

Data as a Service

Invitation to Apply

Accounts

Bank Holidays

Card Activation

Card Controls

Commercial Credit Cards

Credit Card Account Details

Credit Card Accounts Overview

Credit Card Alerts

Credit Card Application Status

Credit Card APRs

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 Redemption Coming Soon

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

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

Access Online Transactions

Account Transfers

Account Validation

ACH Originations

Bank Information

Card as a Service

Card as a Service API

Check Payables

Core Banking API

Corporate Account Information

Corporate Credit Cards

Corporate Onboarding

Corporate Statements

Custody

Data Toolbox

Data Toolbox - Accounts

Data Toolbox - Documents

Data Toolbox - Transactions

Disbursements via Zelle

U.S. Bank Flexible Capital Platform

Freight Payment Customer Profiles

Freight Payment Transactions

Instant payments

Investment Accounting

Money Movement API

PaySmart

Payee Choice

Payee Token+

Personal Loans

Positive Pay

Push to Card

Receivables

Reference API

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

Settlements

Reconciliation

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)

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 API 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

Gift and Stored Value Card API Fields

Gift and Stored Value Card Examples

Online Debit Transactions

Online Debit API Fields

Online Debit Examples

Private Label Cards

Private Label Transactions

Private Label API Fields

Private Label Examples

Health Savings Account Cards

HSA Support

Fusebox and Simplify HSA Card Support

HSA Card API Fields

Puerto Rico

E4 Support

API Fields

EBT Transactions

IVU Transactions

Receipt Example