• Integration Guidelines
• Supported Features (Other Features)
• Supplementary Data
• Level II and Level III Data

Level II and Level III Data

A credit card transaction may be submitted with three levels of transaction data: Level I, Level II, and Level III. Each level is defined by the amount of information provided to process the transaction.

• Level I includes standard transaction data such as date, card number, and total purchase amount.
• Level II includes Level I data plus enhanced transaction data such as customer reference number, invoice number, and sales tax amount.
• Level III includes Level II data plus line item details.

If you accept business, corporate, or purchase cards then providing Level II/III data on your transaction may qualify the transaction for better interchange rates. Your customer's business can also benefit from itemized card statements as well as information to support and streamline business processes such as purchasing authorization, reconciliation, and reporting.

Note that the gateway does not validate that the data provided on the transaction is sufficient to qualify for specific interchange rates as required by the card schemes.

Providing Level II/III Data on Initial Operations

When you create an order, all Level II or III data that you provide will apply to all transactions on the order.

If you use the gateway to perform 3DS authentication and payment transactions, then you can create an order by submitting an INITIATE_AUTHENTICATION followed by an AUTHENTICATE_PAYER request with Level II/III data, and provide authentication.transactionId in the subsequent AUTHORIZE, PAY, or VERIFY request, and Level II/III data is populated from the referenced authentication.

If you provided Level II/III data in the AUTHENTICATE_PAYER request, then provide the authentication.transactionId in the subsequent AUTHORIZE, PAY, or VERIFY request, you can still submit the same or different Level II/III data on your financial request to override Level II/III data provided on authentication.

Level II fields are supported from version 64 and Level III from version 77 of the AUTHENTICATE_PAYER request.

Authenticate Payer API Reference [REST][NVP]

Providing Level II/III Data on Subsequent Operations

You only need to provide Level II/III data on subsequent operations (Capture or Refund) when you want to:

• override the data you provided for the order
  

  You can override the Level II/III data for the order by providing the data at order level. You may want to do this to correct information provided when you created the order. The updated information will then apply to all subsequent transactions on the order. For example, order.customerReference

  Only order-level fields present on the transaction request can be overridden. For example, order.amount can be provided in an Authorize transaction request, but not on a subsequent Capture transaction request.

  See Order-Level Field column in the Level II/III tables below.

• provide data that only applies to the transaction
  

  You can provide Level II/III data that only applies to the specific transaction. For example, transaction.taxAmount

  See Transaction-Level Field column in the Level II/III tables below.

• perform Capture or Refund transactions where the transaction amount differs from the order amount. In these cases, you must provide Level II/III data on the transaction, like amounts or line item details, as these cannot be defaulted from the order.

Sending Level II/III Data to your Acquirer

When the gateway sends Level II/III data to your acquirer, values provided on the transaction take precedence over the values provided at the order level. If you do not provide values on the transaction, the gateway will use the values provided at the order level to send to the acquirer, where applicable only.