Supporting Level 2 and Level 3 Transactions for Cardpointe Payments

This document outlines the implementation of level 2 and level 3 processing for CardPointe payment transactions. The changes apply to the Authorization and Capture requests, where additional data fields have been added as per the CardPointe API documentation. Configuration-based control has been implemented to include relevant fields based on card types.

This implementation enables Aptify CardPointe integration to support enhanced data for qualifying card types. This improves interchange rates and meets compliance standards set by card networks.

Level 2 Implementation

Fields Added to Authorization and Capture Requests:

• taxamnt : Total tax amount for the transaction.
• ponumber : Purchase order number.

These fields are conditionally included in the request based on the card type used and the configuration flag.

Configuration in web.config

The following attribute has been added to web.config file
<add key="Aptify.Applications.Payments.Level2.CardTypes" value="VISA, AMEX" />
Note: Replace the card type in the above attribute based on the card used.

Level 3 Implementation

Fields Added to Authorization and Capture Requests:

• shiptozip : Shipping destination ZIP code.
• orderdate : Order date in MM-DD-YY format.
• items : Array of line items, each with the following fields:
  • description : Item description
  • discamnt : Discount amount
  • lineno : Line item number
  • netamnt : Net amount
  • quantity :  Quantity of items
  • taxamnt : Tax amount for the line
  • unitcost : Cost per unit
  • uom :  Unit of measure
  • upc : Universal Product Code

The above fields are added dynamically based on the card type validation against the configuration setting.

Configuration in web.config

The following attribute has been added to web.config file.
<add key="Aptify.Applications.Payments.Level3.CardTypes" value="MASTERCARD, VISA" />
Note: Replace the card type in the above attribute based on the card used.

Conditional Logic in Code

The inclusion of Level 2 and Level 3 fields is controlled by logic that checks the card type against the configured values in web.config. Based on this, the system appends the appropriate fields to the request payload.