# Level 2 / Level 3 Processing

## Visa Level 2 Deprecation Notice
Starting April 17, 2026, Visa will not accept Level 2 data for lower interchange rates. To keep interchange savings on Visa transactions, create [Transfers with Level 3 data](#create-a-sale-with-level-3-processing) and [Authorizations with Level 3 data](#create-an-authorization-with-level-3-processing). Mastercard Level 2 processing is unaffected.

In this guide, you'll learn the requirements of L2/L3 processing, which merchant types are ineligible, how to enable L2/L3, and how to create a sale, authorization, and capture using L2/L3.

Credit card processing fits into three levels: Level 1, Level 2, and Level 3 processing.

Each level is defined by the amount of information needed to complete a transaction.

- **Level 1:** Normal interchange, no additional fields required.
- **Level 2:** Lower interchange, additional fields required. Visa is ending its Level 2 offering in April 2026.
- **Level 3:** Lowest interchange, additional fields required.

For Level 2 and Level 3 processing, only business-to-business merchants and the government can receive lower interchange fees. Additionally, a corporate, business, or purchase card is required to obtain the lower interchange rate for Level 2 and 3 processing.

- This feature is only supported on Visa and Mastercard branded cards.
- Because only business-to-business and government transactions qualify, [the `Merchant` needs to be enabled](/api/merchants/updatemerchant) for Level 2/3 processing.
- Level 2 and Level 3 processing is only available in Live environments. This feature isn't available to test in Sandbox environments.
- Tax-exempt transactions are not eligible for Level 2. They are eligible for Level 3.
- Merchant must be located in the United States.

## Supported APIs

Level 2 / Level 3 Processing is available for:

- [Transfers](#creating-a-sale-with-level-2-and-level-3-processing)
- [Authorizations](#create-an-authorization-with-level-2-and-level-3-processing)
- [Payment Links](#create-a-payment-link-with-level-2level-3-processing)

## Ineligible Merchants

Specific businesses are excluded from processing Level 2 and 3 transactions.

If a `Merchant` has one of the following Merchant Category Codes ([MCC](http://www.dm.usda.gov/procurement/card/card_x/mcc.pdf)), they aren't eligible to process Level 2/3 transactions:

| MCC Code | Merchant Description |
|  --- | --- |
| **3000-3299, 4511** | Airlines/Passenger Transport |
| **3351-3500, 7512** | Car Rentals/Auto Rental |
| **4411** | Cruise Lines |
| **5962, 5966, 5967** | High Risk Direct Marketing |
| **3501-4010, 7011** | Hotels/Lodging |
| **4112** | Passenger Railways |
| **5812, 5814** | Restaurants |
| **4722** | Travel Agents |
| **7513** | Truck and Utility Trailer Rentals |

## Network Support

| Network | Level 2 | Level 3 |
|  --- | --- | --- |
| Visa | ⚠️ Deprecated April 17, 2026 | Yes |
| Mastercard | Yes | Yes |

## Quality Data

It’s important that the data that is being passed along is accurate. The card network's validation technology will identify generic descriptions, placeholder data, and artificially generated content. The data must be real, accurate, and descriptive of the actual products or services being sold. There will be additional dues and assessments associated with the network's validation of data quality, effective October 17, 2025.

The examples below are meant to help point you in the right direction, but it isn’t exhaustive. Ultimately, the card network decides whether the data a merchant submits qualifies.

| **Finix Line Item Field** | **Card Network Recommendation** | **Avoid** |
|  --- | --- | --- |
| `item_data#item_description` | They must provide meaningful information about purchased items/services | Do not provide merchant name, single characters, or generic descriptions |
| `item_data#merchant_product_code` | Typically, the SKU or identifier by which the Merchant tracks and prices the item or service. Must always be provided for every line item. Product code can be:• Merchant's product code• Manufacturer's product code• Buyer's product codeThis field must provide information about the purchase and not the customer. | Do not use erroneous data, such as the card product or MCC |

## Update a Merchant to Enable Level 2/3 Processing

Before a `Merchant` can process Level 2 or 3 transactions, update the `Merchant` resource and enable `level_two_level_three_data_enabled`. For more information, see [`Update a Merchant`](/api/merchants/updatemerchant).

## Creating Sales with Level 2 and Level 3 Processing

Once `level_two_level_three_data_enabled` is updated to **true**, the `Merchant` can process both Level 2 and Level 3 `Transfers` and `Authorizations`.

### Create a Sale with Level 2 Processing

[Create a Transfer](/api/transfers/createtransfer) and include the required request arguments to include Level 2 processing.

Example

**API Definition**
A successful request returns a `201 Created` status code and includes a `Transfer` resource with level 2 processing details in the response.

### Create a Sale with Level 3 Processing

[Create a `Transfer`](/api/transfers/createtransfer) with the additional fields to include Level 3 processing.

### Create an Authorization with Level 2 and Level 3 Processing

### Create an Authorization with Level 2 Processing

[Create an `Authorization`](/api/authorizations) with the additional fields to include Level 2 processing.

### Create an Authorization with Level 3 Processing

[Create an `Authorization`](/api/authorizations) with the additional fields to include Level 3 processing.

### Capture an Authorization with Level 2/Level 3 Processing
Finix will automatically include the Level 2/Level 3 data with the [capture](/api/authorizations/captureauthorization) request.