Recur360Pay Level 2/3 Security for Payment Processing

5 min. readlast update: 11.19.2026

In today's digital landscape, ensuring the security of payment processing is paramount for businesses and their customers.


Security Levels 

Level 1

At this level, only standard cardholder information is required for the transaction.

  • Examples of this data include: the card number, card expiration date, transaction value, date, and the merchant’s doing-business-as (DBA) name, and the Merchant Category Code (MCC). 
  • This level of information is the bare minimum for a transaction to achieve authorization; that makes it quicker to collect from customers at checkout (since there are fewer data fields to fill out).

Level 2

To qualify for L2, you’ll need to include all of the L1 data, as well as fields such as sales tax, unit numbers, item descriptions, and the shipping address.

  • You may need to include a Purchase Order number, too.
  • American Express only supports up to Level 2 data.

Level 3

For a Level 3 transaction, L1 and L2 data are required, as well as a longer list of additional fields.

  • Examples include: ship-from ZIP/postal code, ship-to/destination ZIP code, invoice number, order number, item codes and description, freight amount, and duty amount. 

 



  • Recur360Pay offers advanced Level 2 and 3 security features that enhance transaction safety while providing businesses with the tools they need to manage payments effectively.
  • We couple these 2 together for level 3.
  • This article will explore the benefits of Level 2 and 3 security, how to enable it, set it up, and utilize it for optimal payment processing.

Click each section to expand:


About Level 2/3 Security

Level 2 and Level 3 credit card processing data are line-item pieces of information about a payment.

  • They’re extra fields within a payment message which give a fuller picture of exactly what the payment is for.

Credit card companies introduced these extra data fields to facilitate more descriptive (and, therefore, more reliable and secure) payments.

Level 2 and Level 3 data are generally included in business-to-business (B2B) or business-to-government (B2G) transactions.

  • They are rarely, if ever, used in consumer payments.
  • These levels of security are designed to protect sensitive transaction data, reduce fraud, and ensure compliance with industry standards such as PCI DSS (Payment Card Industry Data Security Standard).
  • By implementing Level 2/3 security, businesses can provide a safer payment experience for their customers.

Benefits of Level 2/3 Security

Reduced Fraud Risk: Enhanced security measures help to minimize the risk of fraudulent transactions.

Improved Customer Trust: Customers are more likely to complete transactions when they feel their payment information is secure.

Compliance: Helps businesses meet regulatory requirements and maintain compliance with industry standards.


Qualifications

To qualify for either level, you’ll need to provide different types of data.

  • Card networks have specific requirements for each one.
  • For example, specific merchant category codes (MCC) are excluded from Level 2 or Level 3 data processing eligibility.
  • With Visa, Level 2 or 3 data only apply to commercial credit cards.
  • For Mastercard, it applies to commercial credit, debit and prepaid cards.

Now that you have learned more about Level 2/3 security for payment processing lets go over how to enable, set up and use the feature. 

Click each section to expand:


How to Enable Level 2/3 Security

To enable Level 2/3 security in Recur360Pay, follow these steps:


Setting Up Level 2/3 Security

Once you have enabled Level 2/3 security, you will need to set it up for your transactions:

  • Go to Settings-> Payment Processors and click the Level 2/3 Processing Settings in the upper right. 

  • The to see a list of Commodity Codes click the Browse Commodity Codes button. 

Now we will need to map the commodity codes to your line items and invoice payment fields. 

  • There are two ways of mapping commodity codes, through a CSV upload, or manually mapping the item. 

Click each section to expand:


CSV Upload 

To use our CSV upload, you can download the CSV template and a list of commodity codes for reference. 

  • Start by clicking Download CSV template. 
  • You may also want to download the commodity code list if you do not already know which ones to use. 

  • The CSV will download as an Excel document. 
  • Click the downloads from your browser and open the file. 

  • In the Excel file there is a column for the commodity code. 
  • In this screenshot there was already an item that had the commodity code. 

  • Enter the commodity codes for the rest. 

  • Remember to save the Excel file. 

In Recur360 click the Choose File button and select the correct file. 

  • Now in Recur360 you are ready to click the Upload button. 

  • It can take a little while for the CSV to upload depending on the amount of information. 
  • You will receive an email once the upload is completed. 

 


Manual Item Mapping

You are able to map the items manually. 

  • To do so first select the item. 

  • Next enter the description code. 

  • Move on to the commodity code. 

  • Now check if it is a shipping item. 

  • Last, select the unit of measure. 

  • Click Save. 

  • Repeat these steps for each item that needs to be mapped. 


How it will look

When creating an invoice/ recurring invoice you will now see a new non-adjustable field when adding an item to the invoice. 

  • When going to take payment on any invoice you will see a new field confirming if level 2/3 data was provided. 

  • After a payment is submitted in the payment history report you will see a new sortable column to show if the level 2/3 data was submitted. 

 


 

Was this article helpful?