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

## Transaction types

Gift and stored value card transactions have an immediate effect on the card's available balance. For example, a Return transaction (Type 09) is used to activate a new gift card and also increase the balance on the card. The following examples show how transaction types are used for processing gift cards.

**Transaction Qualifier (Field 0115)** 
-   A Transaction Qualifier is required to identify the transactions as gift and stored value transactions. Every transaction must contain the appropriate value of (050) in the Transaction Qualifier field.

### Trans Type 01 (Authorization)
- **Authorization Only** - Used when the authorized amount and the final transaction amount are different: It places a lock on the entire account until the Prior Auth (Type 07) transaction is run with the final amount.

### Trans Type 02 (Sale)
- **Redemption / Partial Redemption**
  - Decreases the value on the stored value account. 
  - Amount applied must compare the amount being authorized with the actual amount authorized. 
  - The card issuer can authorize an amount equal to the balance remaining on the card. 
  - This amount may be less than the purchase amount (the original requested authorization amount) and your application must be able to accept an additional form of payment. 
  - This scenario is referred to as Partial Redemption. 
- **Redemption (Cash Back, Cash Out / Unload)** - Used to unload the total remaining balance of the card. Depending on the program, it may or may not include returning cash back to the cardholder. 
- **Tip** - Used for tip reporting, if applicable.  

### Trans Type 07 (Prior-Auth Sale)
- **IVR Authorized Redemption** - Used when an Interactive Voice Response (IVR) system is used to secure approval on a redemption request. 
- **Prior Auth / Unlock** - Used with an Authorization Only (Type 01) to settle the approved amount or to unlock the authorized amount. 

### Trans Type 09 (Return)
- **Card Activation** - Activates a card that has been loaded with a pre-set value.  
- **Issue Card** - Loads the requested value and activates the blank card.  
- **Reload / Recharge** - Used to add additional amount to an existing card when a value is granted by the merchant or purchased by the cardholder.  
- **Return** - Used to add value to an existing card when merchandise is returned.  

### Trans Type 11 (Void Sale)
**Void Redemption** - Used to reverse a previously submitted Redemption request. 


### Trans Type 17 (Void Return)
- **Void Activation / Deactivate** - Reverses a submitted Activation request.  
- **Void Card Issue** - Reverses a submitted Issue Card Request. 
- **Void Reload, Recharge** - Reverses a Reload / Recharge (Type 09) action.  
- **Void Return** - Reverses a Return Transaction (Type 09). 

### Trans Type 24 (Balance Inquiry) 
- Used to obtain the current account balance or open-to-buy amount for a pre-paid gift card or stored value card. 
- This transaction is not captured in the batch file.
**Note:** Pre-paid gift cards are not supported by all TPPS. If the TPP does not support this transaction type, a TRANSACTION NOT SUPPORTED error may be returned from the application.



## Implementation Considerations

Your POS application must adhere to the following criteria specific to the acceptance of gift and stored value cards:
- Gift certificates offered and accepted as tender.
- Gift certificates issued for refunds.
- Gift certificates offered as a promotion.
- Negotiated agreement or program with electronic gift and stored value card processor.



### Gift Card Account Numbers 

**Variables**
- Can vary in length and prefix range.
- May or may not be created using the modular 10-digit routine.
- May or may not have the same value embossed on the card as is contained on the magnetic stripe.
- May or may not be created with an expiration date.

:::notice{title="note"}
If a card number is  entered manually, you must provide an Expiration Date (Field 0004). If the gift card does not include an expiration date, Elavon recommends that your application provide a date that is no more than 20 years from the current date.
::: 


### Amounts

Multiple dollar amounts can be requested and received with gift and stored value transactions. Gift and stored value transaction requests can contain a transaction amount, cash back amount, and possibly even a tip amount.

Response messages received from the processor may contain the transaction amount (which may be different from the amount sent in the authorization request) and the remaining balance on the gift and stored value card. The POS application is responsible for sending these amounts in a transaction request, and recognizing them in the response.

### Cash Back

Based on the gift and stored value card program or processor, you may be required to support a cash back amount on a gift and stored value card transaction. Typically, the cash back is used as an option to fully redeem a gift and stored value card.

The POS application can be configured to set a maximum cash back amount. This typically requires that a gift card’s remaining balance be below a certain amount before it can be redeemed for cash.

### Distribution

Gift and stored value service providers offer two ways for stored value cards to be distributed:
- **Pre-loaded Cards:** These cards are pre-loaded with set values. When a card is purchased, an Activation transaction is performed.
- **Blank Cards:** Blank cards have no associated value. When a card is purchased, an Issue Card transaction is performed to load the card with the customer's paid amount.

### Terminal ID

Your integration must be able to set a specific value for the Terminal ID for each payment type supported by your POS application.
Every transaction must send the respective value in Field 0109.

### Processor Limitations

Many gift and stored value programs are run by processors whose host only supports the issuance, acceptance, and processing of gift and stored value programs for end users and merchants. It is important to have knowledge of, and understand, any processor limitations before moving forward with your development effort.

Once the processor is known, ensure that Elavon has a TPP interface available and that the transaction codes supported complement the implementation and the gift and stored value program.

Gift and stored value card implementation

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