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

MasterCard specific certification requirements include:


::page-heading-list{min-level=2 max-level=2 }


## Payment facilitator

Customers who are identified as a payment facilitator need to migrate to the Elavon E4 host in order to pass the following dynamic fields:

- Merchant passes API fields 7015 – 7051 to a payment facilitator, who in turn is responsible for passing these fields to Elavon.
- Sale transaction in which the final dollar amount is known at the time of authorization (amount will not change) the following values are used:
    - F is Final Amount
    - P is passed on an authorization (type 01) if the final dollar amount may change between the authorization and Prior Authorization transactions

:::::notice{important}
Dynamic Payment Facilitator (PF) fields are only required where multiple sub-merchants funnel transactions through a single MID. Not industry specific and can apply to retail, eCommerce or MOTO transactions.
:::::


The following content identifies API fields 7015 – 7051.

**7015 (Dynamic DBA)**
- Description: Merchant is able to dynamically change: "Doing Business As” name on each transaction submitted to the host for authorization.
- Size: 1 - 25 
- Data Type: A/N
  
**7016 (Dynamic Street Address)**
- Description: Merchant is able to dynamically change Street Address on each transaction submitted to the host for authorization.
- Size: 1 - 30
- Data Type: A/N

**7017 (Dynamic City)**
- Description: Merchant is able to dynamically change Street Address on each transaction submitted to the host for authorization.
- Size: 2
- Data Type: A/N  

**7018 (Dynamic State)**
- Description: Merchant is able to dynamically change State on each transaction submitted to the host for authorization.
- Size: 2
- Data Type: A/N
    
**7019 (Dynamic Postal Code)**
- Description: Merchant is able to dynamically change Postal Code on each transaction submitted to the host for authorization.
- Size: 1 - 9
- Data Type: A/N

**7020 (Dynamic Postal Code)**
- Description:  Merchant is able to dynamically change Country Code on each transaction submitted to the host for authorization.
- Size: 1 - 9 
- Data Type: A/N

**7021 (Dynamic Phone Number)**
- Description: Merchant is able to dynamically change Merchant Phone Number on each transaction submitted to the host for authorization.  
- Size: 1 - 20 
- Data Type: N
       
**7022 (Dynamic Sub-Merchant ID)**
- Description: Merchant is able to dynamically change to dynamically change the Sub-Merchant ID on each transaction submitted to the host for authorization.
- Size: 1 - 15
- Data Type: N
    
**7023 (Dynamic Email Address)**
- Description: Merchant is able to dynamically change email address on each transaction submitted to the host for authorization.
- Size: 1 - 70
- Data Type: A/N 

**7024 (Dynamic MCC)**
- Description: Merchant is able to dynamically change MCC on each transaction submitted to the host for authorization.
- Size: 4 
- Type: N

**7025 (Dynamic Tax ID)** 
- Description: Merchant is able to dynamically change Tax ID on each transaction submitted to the host for authorization.
- Size: 1 - 14
- Data Type: A/N 

**7051 (Dynamic Auth Type Indicator)**
- Description: Required for Payment Facilitator Merchants.
- Type of Authorization Transaction Valid Values:
  - F = Final Amount - amount is not expected to change for settlement
  - P = Pre-Authorization / Estimated Amount - amount may change between auth and settlement
  - The amount referenced is the total transaction amount provided in API field 2
- Size: 1
- Data Type: A/N

## Zero-dollar approval with subsequent declines

To get a zero-dollar approval with subsequent declines, use the Zero Card (see Demo Card Scenarios).

- Transaction is approved if the transaction amount (API 0002) is $0.00.
- If transaction amount requested is greater than $0.00, the standard decline logic is applied.

## Address Verification Service approvals and declines

For Address Verification Service (AVS), use the following values:

- AVS ZIP Code (API 0700)

**Example:** 33606

- AVS Billing Street Address (API 0701)

**Example:** 100 MAIN ST

Any matching values would be a match, and any other values would be considered a non-match.

The results will be placed in AVS Result Code (API 1020).
- Y – Both ZIP Code and Billing Street Address match
- Z – ZIP Code matches and Billing Street Address does not match
- A – ZIP Code does not match and Billing Street Address match
- N – Neither ZIP Code nor Billing Street Address match

## Card Verification Value (CVV2/CVC2/CID)

For Verification Value (CVV2/CVC2/CID), use the following values:
- CVV2/CVC2/CID Information (API 0050)

**Example: (382)**

A matching value would be a match, and any other value would be a non-match. The results will be placed in CVV2/CVC2/CID Response (API 0040).
- M – Match
- N – No Match

## Approvals

To get a credit card approval, use any other card number that is not a Decline Card, Zero Card or Partial Authorization Card.

MasterCard requirements

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