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.

This example illustrates the fields that need to be printed on electronic point-of-sale terminal receipts:


::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/fusebox/receipt1.png"   alt="example of printed receipt fields"}


:::notice{title="note"}
Receipt examples and fields are for general illustrative purposes. Your Third Party Processor may have requirements and rules that will require changes or additions to your receipts. Please follow your Third Party Processor’s receipt guidelines. 
::: 

## Receipt Fields

**Receipt Sample Number 1**
  - API Field Number = NA
  - Field Name = Merchant DBA Name
  - Description and Notes
    Required. The merchant’s Doing Business As (DBA) name must be printed. 
    - **Note:** This should match the DBA name provided to the TPP and in some cases is part of the merchant information in the Fusebox Site ID.

**Receipt Sample Number 2**
  - API Field Number = NA
  - Field Name = Merchant City, State, and ZIP Code (Province and Postal Code for non-US merchants)
  - Description and Notes
    - Required. Should match the merchant city, state, and ZIP code provided to the TPP and in some cases is part of the merchant information in the Fusebox Site ID.

**Receipt Sample Number 3**
  - API Field Number = NA
  - Field Name = Merchant Phone Number
  - Description and Notes
    - Required. The number a cardholder would use to call the merchant directly for questions about the transaction. Although not specifically required, this is STRONGLY recommended, to avoid the customer calling their issuing bank for inquiries. This number should match the phone number provided to the TPP and in some cases is part of the merchant information in the Fusebox Site ID.

**Receipt Sample Number 4**
  - API Field Number = 32
  - Field Name = Authorization Date
  - Description and Notes
    - Required. Date the customer made the purchase. Format is MMDDYY.

**Receipt Sample Number 5**
  - API Field Number = 33
  - Field Name = Authorization Time
  - Description and Notes
    - Required. Time the customer made the purchase. Format is HHMMSS.

**Receipt Sample Number 6**
  - API Field Number = 7
  - Field Name = Reference Number
  - Description and Notes
    - Unique number assigned by your application to this transaction. Although it is not mandatory that this field be printed, for audit and reconciliation purposes, Elavon recommends that this information be printed on the receipt. 

**Receipt Sample Number 7**
  - API Field Number = 3
  - Field Name = Account Number Masked
  - Description and Notes
    - Required. Card associations require that the account number be masked except the last 4 digits. For online debit transactions, only the last four digits of the account number should be displayed. Visa USA requires masking all except the last four digits of the cardholder’s account number on the copy of the transaction receipt.

**Receipt Sample Number 8**
  - API Field Number = 4
  - Field Name = Expiration Date Masked
  - Description and Notes
    - The common standard is not to print the expiration date. Visa USA requires masking of the cardholder’s entire expiration date on the copy of the transaction receipt.

**Receipt Sample Number 9**
  - API Field Number = 1001
  - Field Name = Payment Type Identifier
  - Description and Notes
    - Required. Provided in the Output Response. Use either the two-character Card Type (Field 1000) or the Card Name (Field 1001).

**Receipt Sample Number 10**
  - API Field Number = N/A
  - Field Name = Description of Goods and Services
  - Description and Notes
    - Description of purchased items. All items will be listed with a price for each, item number, and subtotal of all items together.

**Receipt Sample Number 11**
  - API Field Number = 2
  - Field Name = Amount
  - Description and Notes
    - Required. Final amount of the transaction.

**Receipt Sample Number (Not Shown)**
  - API Field Number = 632
  - Field Name = Account Balance 
  - Description and Notes
    - Required on Declines, optional on other transaction types. In the event of a pre-paid gift card, a decline may occur if partial authorizations are not supported. In this case, the remaining balance should be printed on the receipt for the cardholder reference. The account balance may be printed any time it has been returned to the POS application. 
    - **Conditional statement**: If there is a partial auth and remaining balance, this field must be displayed.

**Receipt Sample Number 12**
  - API Field Number = 6
  - Field Name = Approval Code (Authorization No.)
  - Description and Notes
    - Required. Approval code assigned to this transaction. 
    - **Not required** if the transaction is Visa Easy Payment Service (VEPS)

**Receipt Sample Number 13**
  - API Field Number = N/A
  - Field Name = Tran ID
  - Description and Notes
    - Some TPPs (mostly On-line Debit and Host Capture) require a STAN or Tran ID to be presented on receipts. Refer to the Debit Addendum, Gift Card Addendum or specific Third Party Processor Interface to confirm specific data field to be printed on receipts.

**Receipt Sample Number 14**
  - API Field Number = N/A
  - Field Name = Cardholder Signature
  - Description and Notes
    - Required. If a receipt is used detailing the goods or services received, the customer or cardholder must sign the receipt as an agreement for the transaction. The merchant must obtain the customer’s signature during the transaction. Cardholder signature is not needed if the PIN is an acceptable substitute for cardholder signature, or at self-service terminals.

**Receipt Sample Number 14a**
  - API Field Number = N/A
  - Field Name = Disclosure Statement
  - Description and Notes
    - Required. As part of the signature requirement, a disclosure statement (statement regarding the cardholder’s agreement to pay amount on receipt) must be printed on the receipt. The card associations dictate the content of the disclosure statement. The statement that appears should be configurable by card type.

**Receipt Sample Number 15**
  - API Field Number = N/A
  - Field Name = Refund Policy Disclosure
  - Description and Notes
    - Suggested. Statement regarding the merchant’s refund policy. Required to be approximately 0.25 inches high and near the cardholder signature area.

**Receipt Sample Number 16**
  - API Field Number = N/A
  - Field Name = Legend
  - Description and Notes
    - Required. Refers to the distribution of the copies. The top copy, or the copy that the customer actually signs, must stay with the merchant. For example, *Merchant’s copy*, *Cardholder’s copy*

 **Receipt Sample Number Not Shown**
  - API Field Number = 17
  - Field Name = Cashback Amount
  - Description and Notes
    - Required. If the transaction has cashback, the amount in API field 17 it must be printed on the receipt.

**Receipt Sample Number Not Shown**
  - API Field Number = 1002
  - Field Name = Cardholder Name
  - Description and Notes
    - Optional. If available, the cardholder name can be printed so the transaction processors can identify who purchased the goods or services. Cardholder information can only be provided if track 1 is read and passed to the Elavon Gateway application.

**Receipt Sample Number Not Shown**
  - API Field Number = 43
  - Field Name = Unique Trace Audit Number
  - Description and Notes
    Conditional. Unique number assigned to transaction by the processor. 
    - **Note** This field is only used with Host Capture Processing (PIN Debit, Credit, Gift, Check), and may vary by Third Party Processor Interface.


  







Receipts

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)

Transaction Inquiry (22)

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