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

This guide contains information for integrating a private label card with your POS application. We use [Synchrony](<https://www.synchrony.com/for-businesses.html>) as our third party vendor. See the :magic-link[Getting Started]{id="getting-started"} section of the main Fusebox guide for authentication and setting up a test account. 

:::notice{title="important"}
The cards and account numbers are specific to each partner. Contact Synchrony for test information that can be linked to your Fusebox account.
::: 

Your implementation must address the following business environment criteria specific to the acceptance of Synchrony private label cards:
- Uniqueness of the available private label programs.
- Acceptance of a private label card as tender.
- Requirements negotiated in the agreement between the end user or merchant, and the entity (financial organization) responsible for issuing the cards and providing the processing services.

## Transaction types

Your integration should be able to support any of the transaction types listed below:
- Authorization (01)
- Sale - Forced purchase (02)
- Prior Auth (07)
- Return (09)
- Transaction Inquiry (22)

:::notice{title="note"}
Forced purchases don't check the consumer's available credit line with Synchrony. If the amount of the authorization and the forced purchase don't match, the forced purchase has no effect on the authorization.
:::

## Prior Authorization/Voice Authorization

Send Prior Auth (07) instead of a new Authorization (01) or Sale (02).

A voice authorization can be obtained (if supported) from Synchrony in the event of a “Switch Down” error response or any condition where the POS doesn't get a response from the host.

:::notice{title="note"}
Synchrony supports both Forced and Voice Authorizations.
:::

## Transaction inquiry

Transaction Inquiry (22) is used to inquire about the status of a transaction.

By tracking our token or unique ID from the original authorization, the transaction inquiry does not require the cardholder’s account number. However, in an error recovery situation, the output response is not returned to the POS. The POS application retains the original transaction details until a successful authorization response is received. Transactions do not communicate to a third party processor and our applications don't need to reach the host for this transaction to function.

:::notice{title="note"}
We require that your application support the Transaction Inquiry transaction type.
:::

## POS application Request Messages

API requests are described below.

**Terms of Payment** 
- Unlike other revolving credit card transactions, the end user or merchant is able to offer various terms on the financing of the purchase. Specific transaction detail information must be presented to ensure that the customer’s account is updated and billed correctly. 

**Expiration Date** 
- A private label card may be issued without an expiration date. In that case, your application must provide one. We require that an expiration date be passed in the input request and recommend using a date no more than 20 years from today.

**Physical Characteristics** 
- Your POS application must take into account and address the following physical characteristic variances:

- Magnetic Stripe Data - Information contained on the magnetic stripe of a private label card varies. Private label cards may contain only Track 1, only Track 2, or both Track 1 and Track 2 data.

- Account Number - Private label card account numbers can vary in length and prefix range. They may or may not:
 - Be validated using the MOD-10 routine.
 - Differ between what is embossed on the card and what is on the magnetic stripe.
 - Have BIN ranges that are defined by the private label processor.
 - Be unique for each private label card program.
 - Overlap with other credit cards.

## Receipt considerations

We recommend that you confirm any additional requirements the end-user, merchant, and private label processor may have relating to in-store and down-payment disclosures.

Private label card transactions

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