Introduction
As B2B and commercial card payments grow, transaction fees can become a significant cost especially when insufficient details push transactions into higher interchange categories.
Level II and Level III payment data provide richer context, including tax amounts and item-level details, helping reduce network costs and improve authorization rates. PayPack leverages Stripe’s payment line items to support both Level II and Level III data, ensuring accurate, audit-ready financial records.
This guide explains what Level II and Level III data are, why they matter, and how PayPack enables compliance via Stripe.
Who This Is For
- Finance and accounting teams managing card processing costs
- NetSuite and ERP administrators using PayPack
- Payments and integration engineers working with Stripe APIs
- Operations and revenue teams handling B2B or high-volume transactions
1. Understanding Level II and Level III Payment Data
Card networks offer lower interchange rates for certain commercial and corporate cards when additional transaction details are passed to issuers. These enhanced details are commonly categorized as Level II and Level III data.
Level II data typically includes summary-level transaction enhancements such as tax and reference information, helping issuers better classify commercial transactions.
Level III data builds on Level II by adding detailed item-level information, offering the highest level of transparency and commonly required for B2B and corporate purchasing scenarios.
Level II vs Level III Comparison:
| Aspect | Level II Data | Level III Data |
|---|---|---|
| Primary use case | Commercial card payments | B2B and corporate card payments |
| Tax information | Required | Required |
| Item-level details | Not required | Required |
| Unit cost & quantity | Not required | Required |
| Line-level totals | Not required | Required |
| Typical benefit | Moderate interchange reduction | Highest interchange optimization |
| Common card types | Business & commercial cards | Corporate & purchasing cards |
2. Why Level II and Level III Data Reduce Network Costs
Issuers rely on transaction detail to assess risk, legitimacy, and purchase intent. When enriched data is missing, transactions are often routed through higher-cost interchange categories.
Providing Level II and Level III data can:
- Help eligible transactions qualify for lower interchange categories
- Improve authorization success for commercial and corporate cards
- Reduce disputes by increasing transaction clarity
For supported card types, enriched data can materially reduce total network and interchange costs over time.
3. How PayPack Supports Level II and Level III Data Using Stripe
PayPack enables Level II and Level III payment data by leveraging Stripe’s payment line items functionality, which attaches detailed purchase information directly to a payment.
PayPack capabilities include:
- Capturing item-level data from upstream systems (orders, invoices)
- Structuring payment data to meet Stripe’s Level II and Level III requirements
- Passing enriched data to Stripe during payment confirmation or capture
- Maintaining consistency between payment data and downstream financial systems
This approach removes the need for custom payment logic while ensuring compliance with issuer and network requirements.
4. Stripe Payment Line Items: Configuration Overview
Stripe payment line items are the core mechanism used to pass enriched transaction data to card networks.
Key considerations:
- Line items are supported only for specific payment methods
- Certain fields are required to qualify for Level II or Level III rates
- Line-item totals must exactly match the PaymentIntent amount
Stripe validates these conditions before submitting transactions to card networks.
5. Cards L2/L3 Rates Eligibility
While enriched data reduces costs in principle, actual Level II and Level III eligibility depends on card and issuer support.
Eligibility is influenced by:
- Card type (commercial or corporate cards)
- Issuer support for enhanced data
- Correct population of required fields
Consumer cards may not receive reduced rates even when line items are provided, while corporate cards often require Level II or Level III data to qualify.
6. Field Requirements for Level II and Level III Data
General Supported Fields
- Product or service description
- Unit amount
- Quantity
- Line total amount
- Currency
Additional Card-Supported Fields
- Sales tax amount
- Tax indicator
- Customer or invoice reference
These fields form the foundation for Level II qualification and are extended for Level III.
7. Additional Payment Method-Specific Fields
| Payment Method | Required / Supported Fields | Purpose & Notes |
|---|---|---|
| Cards (Level II / III) | Item description, unit cost, quantity, item-level tax amounts | Required to qualify for Level II and Level III interchange rates and provide issuer transparency |
| Klarna | Product name, quantity, unit price | Improves authorization success and reconciliation for BNPL transactions |
| PayPal | Item name, quantity, price per unit | Provides clearer purchase details to customers and downstream systems |
8. Cards-Specific Line Items for Level II and Level III Rates
For card payments, additional validation rules apply:
- Line-item totals must equal the payment amount
- Tax amounts must align with invoice-level tax
- Item descriptions should be consistent and non-generic
Stripe enforces these validations before transmitting data to card networks.
9. PaymentIntent Operations with Line Items
PayPack supports passing line items at different stages of the payment lifecycle.
- Set line items during confirmation
- Used when full order details are known upfront
- Enables real-time Level II or Level III qualification
- Set line items during capture
- Used when amounts are finalized later
- Common in delayed capture or fulfillment-based workflows
10. Using Top-Level Discounts and Taxes
Stripe supports top-level discounts and tax amounts in addition to item-level data.
Key rules:
- Discounts and taxes must reconcile with line items
- Totals must match the PaymentIntent amount
This flexibility supports promotions and complex tax scenarios while maintaining data integrity.
11. Industry and MCC Code Considerations
Merchant Category Codes (MCC) and industry classification influence interchange qualification.
Accurate MCC alignment improves:
- Issuer classification
- Interchange eligibility
- Reporting accuracy
12. Flexible Payment Scenarios Supported by PayPack
PayPack supports enriched payment data across complex workflows, including:
- Partial captures
- Mixed payment methods
This ensures Level II and Level III data remain accurate even as payment scenarios scale.
13. Mapping Level II and Level III Data Through PayPack
PayPack enforces consistent mapping of enriched data across systems.
Key considerations:
- Payment-level totals must match aggregated line items
- Tax values must align between invoices and payments
- Product naming and pricing must remain consistent
- Stripe and issuer-required data structures must be preserved
This reduces reconciliation issues and supports audit-ready reporting.
Required vs Optional Fields Checklist
| Category | Field | Required / Optional | Notes |
|---|---|---|---|
| Level II | Total payment amount | Required | Must match line items and taxes |
| Level II | Currency | Required | ISO currency code |
| Level II | Sales tax amount | Required | Mandatory for Level II eligibility |
| Level II | Tax indicator | Required | Indicates tax inclusion |
| Level II | Merchant or customer reference ID | Required | Used for issuer reconciliation |
| Level III | All Level II fields | Required | Level III builds on Level II |
| Level III | Item description | Required | Improves issuer clarity |
| Level III | Unit cost | Required | Must match invoice pricing |
| Level III | Quantity | Required | Used to validate totals |
| Level III | Line-item total | Required | Unit cost × quantity |
| Level III | Item-level tax | Required (if applicable) | Required when tax is itemized |
| Optional | SKU or product code | Optional | Improves internal reporting |
| Optional | Invoice/order reference | Optional | Improves traceability |
| Optional | Consistent product naming | Optional | Reduces audit mismatches |
| Optional | Industry-aligned MCC | Optional | Supports interchange optimization |
Tips for Avoiding Errors
- Avoid missing or incomplete line item fields
- Ensure tax amounts match invoice totals
- Test Level II and Level III data in non-production environments
- Confirm card eligibility before assuming interchange savings
Common Mistakes to Avoid
- Sending item data without tax details
- Inconsistent unit costs or quantities
- Assuming all cards qualify for Level III rates
- Skipping validation of Stripe payment payloads
Result of Applying This Approach
By using PayPack with Level II and Level III payment data:
- Eligible network and interchange costs are reduced
- Finance teams gain cleaner, more detailed records
- Authorization success improves for supported cards
- Payment operations scale without added manual effort