> For the complete documentation index, see [llms.txt](https://docs.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplorpay.com/api-reference/resources/visas-commercial-enhanced-data-program/submit-enhanced-transaction-data/line-item.md). # Line-item The following table describes the level 3 line-item data fields from the [Transactions API](/api-reference/api/payments/cards-card-not-present/transactions.md) request code.

Name	Data type	Required?	Length	Description
`item-description`	String	Required	35	The description of the line item. For example, Part name.
`item-net-gross-ind`	Boolean	Required	Not any	Specifies whether the line-item total includes tax. Available values are: `true`: Set this value to include tax. `false` Set this value to exclude tax.
`item-product-code`	String	Required	12	The unique code for the line item. For example, SKU.
`item-quantity`	String	Required	16	The total quantity of the line item in the order. For example, 1.
`item-unit-cost`	String	Required	16	The cost of the line item for the order. For example, 10.
`item-line-total`	String	Required	14	The total amount for the line item, calculated by multiplying the `item-quantity` and `item-unit-cost` field values. For example, `10.00`.
`item-unit-of-measure`	String	Required	14	The unit of measure for the line item, based on ANSI X-12 Allowable Units of Measure and Codes. For example, GAL.

{% hint style="warning" %} If the sales order includes *multiple* items, each line-item field must include the required data to comply with Visa’s enhanced data quality standards. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.xplorpay.com/api-reference/resources/visas-commercial-enhanced-data-program/submit-enhanced-transaction-data/line-item.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.