# Summary The following table describes the level 3 summary data fields from the [Transactions API](/api-reference/api/payments/cards-card-not-present/transactions.md) request code.

Name	Data type	Required?	Length	Description
`billing.zip`	String	Required	10	The postal code of the cardholder’s billing address. For example, 85284.
`shipping.zip`	String	Required	10	The postal code of the cardholder’s shipping address. For example, 85285. Set the `billing-is-shipping` field to `true` if the cardholder’s shipping and billing postal codes are the same.
`duty-amount`	String	Optional	12	The total amount of import or export duties applied to the order. For example, 10.00
`freight-amount`	String	Optional	12	The total amount of freight or shipping charges applied to the order. For example, 10.00
`discount-amount`	String	Optional	12	The total discount applied to the line-item total when an invoice-level discount is present.
`Invoice`	String	Required (Card-not-present transactions)	15	The invoice number associated with the order. This field is used for reporting, reconciliation.
`Purchase-Order`	String	Required (Card-not-present transactions)	15	The purchase order number. This field is used to support detailed billing.
`Order-id`	String	Required (Card-not-present transactions)	15	The unique identifier for the order. This field is used to match transactions to order records.

{% hint style="warning" %} To qualify card‑not‑present transactions for lower interchange rates, include **at least one** of these fields: * `Invoice` (highest priority) * `Purchase-Order` * `Order-id` (lowest priority) **Selection rules** * If you send multiple fields, the system uses the first valid value in this order: `Invoice` → `Purchase-Order` → `Order-id`. * If a higher‑priority field is present but blank/invalid, the system falls back to the next valid value. {% endhint %} --- # Agent Instructions: 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: ``` GET https://docs.xplorpay.com/guides/visas-commercial-enhanced-data-program/submit-enhanced-transaction-data/summary.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.