B2B, commercial cards and Level 2/3
A line-item detail is an invoice-style record for one product or service included in a payment. Instead of describing only the transaction total, it identifies what was purchased and may include a product name or code, quantity, unit cost, unit of measure, tax amount, discount, and line total.
Level 3 data can contain multiple line items for the same transaction. The exact fields, formats, limits, and transmission rules depend on the payment platform, processor, acquiring setup, card network, and transaction type. A merchant should therefore treat a general field list as a planning guide, not as a universal specification.
Think of line-item detail as the structured payment-data equivalent of the rows on an itemized invoice. If an order contains three kinds of goods or services, each kind can be represented as a separate line with its own description, quantity, unit amount, and related values. The transaction also carries order-level information, but a line item explains the individual component rather than the whole purchase.
Current Braintree documentation describes Level 3 line items as similar to details found on an itemized invoice. Stripe documents line-item fields such as product name, product code, quantity, unit cost, unit of measure, and line-level tax. Cybersource examples likewise place product, quantity, amount, tax, and unit information inside a line-items array. These sources agree on the basic concept even though their field names and requirements differ.
For the broader concept, read what Level 3 card data means.
A product name or description tells what the line represents. A product code, SKU, or commodity code may provide a shorter standardized or internal identifier. These identifiers are not interchangeable, and a provider may accept one while requiring another.
Quantity shows how many units were purchased. Unit of measure explains what one unit represents, such as each, hour, foot, or another value supported by the provider. The quantity and unit should agree with the merchant's order record.
Unit cost, line total, tax, and discount fields describe the monetary parts of that line. Some systems calculate or validate relationships among these values. The merchant should send accurate source values and follow the platform's current rounding and smallest-currency-unit instructions.
A customer code or order reference is usually transaction- or order-level information rather than a description of one item. See how customer codes are used in commercial card processing.
Suppose a business invoice contains two replacement filters and one hour of installation labor. A structured payment record might contain one line for the filters and another line for labor. The filter line could identify the filter product code, quantity two, a unit of measure such as each, and the applicable amounts. The labor line could use a service code, quantity one, a unit such as hour, and its own amounts.
The purpose of the example is to show structure, not to prescribe field names. One gateway might label the product identifier as a product code, another may use SKU, and another may support a commodity code in addition to an internal identifier. Some providers impose character limits, accept only specific unit values, or require totals to reconcile before sending the enhanced data onward.
The item rows should also connect back to the same source order or invoice. The guide to linking B2B invoices to payments explains that broader recordkeeping workflow.
Line-item data is useful only when it represents the underlying sale consistently. If quantity, unit cost, tax, discount, or total values conflict, a provider may reject the request, omit the enhanced data, return a validation message, or handle it according to that provider's configured behavior. Stripe, for example, documents arithmetic validation for payment line items, while Cybersource publishes different required-field tables for particular processing connections.
Merchants should not manufacture values merely to fill fields. Build the payload from the order-management, invoicing, ERP, or checkout record that actually describes the transaction. If the source system does not capture a requested value, determine whether the field is applicable and supported before introducing a default.
Because provider documentation changes, verify requirements for the exact gateway, processor, acquiring connection, card type, market, and transaction flow being used. A sample from one platform does not prove that another platform accepts the same names, formats, or number of items.
Businesses first defining the surrounding workflow can also review the overview of B2B credit card processing and the B2B, commercial cards and Level 2/3 FAQ hub.
Line-item descriptions should contain only information needed to describe the business purchase. Do not place full card numbers, security codes, bank credentials, passwords, secret API keys, or unnecessary personal information in product names, descriptions, reference fields, spreadsheets, or general support messages.
Use the payment provider's approved collection and transmission methods for payment credentials. Limit access to exports and integration logs, and use masked transaction references when troubleshooting. If a provider requests an example payload, remove or replace sensitive values and submit it through that provider's approved secure support channel.
Start with one representative invoice and map each row to the documented line-item fields for the exact payment setup under consideration. Then compare the computed values with the order total and test the supported workflow before applying it broadly.
Payments Max can help organize B2B payment requirements for a processing conversation without assuming that a specific provider or configuration supports the same fields. If you contact Payments Max, share only a high-level description of the order system and desired workflow. Do not submit cardholder data, credentials, complete account numbers, or secret keys through a general inquiry.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US
