When processing payments through CardConnect, merchants can take advantage of Level 1, Level 2, and Level 3 data. Each level captures progressively more detailed information, which can help reduce interchange fees, improve transaction transparency, and strengthen reporting capabilities.

What Are Transaction Levels?

• Level I Data: Basic transaction details such as merchant ID, transaction amount, and date. Required for all credit card transactions.

• Level II Data: Adds tax amounts, customer codes, and merchant details. Often required for business or corporate cards to qualify for lower interchange fees.

• Level III Data: Provides the highest level of detail, including line-item descriptions, product codes, shipping details, and freight information. This level is especially important for B2B and government transactions, where detailed reporting is mandatory.

Data Mapping in Salesforce

The table below outlines how key data elements are captured across API parameters, transaction levels, and Salesforce fields.

  Data ElementAPI ParameterTransaction LevelSalesforce FieldSalesforce Field – Echeck (if dual pricing is enabled) Merchant Identifier merchid Level I, II, III Payment Processor Object (fw1__API_Live_Vendor__c) — Order Amount (Total) amount Level I, II, III Payment Object (fw1__Amount__c) — Order Date orderdate Level I, II, III Payment Object (fw1__Payment_Date__c) — Merchant Postal Code N/A* Level II, III — — Merchant Tax Identification Number (TIN) N/A* Level II, III — — Merchant State Code N/A* Level II, III — — Order Tax Amount taxamnt Level II, III Invoice Object (fw1__Tax_Amount__c)Invoice Object (fw1__Tax_Cash_Amount__c) Order Customer Code (PO Number) ponumber Level II, III Invoice Object (fw1__PO_Number__c) — Order Ship From (Origin) Postal Code shipfromzip Level III — — Order Ship To (Destination) Postal Code shiptozip Level III Payment Object (fw1__Shipping_Zip__c) — Order Freight Amount frtamnt Level III — — Order Duty Amount dutyamnt Level III — — Order Discount Amount discamnt Level III Invoice Object (fw1__Total_Invoice_Discount_Amount__c)Invoice Object (fw1__Total_Invoice_Discount_Cash_Amount__c) Item Universal Product Code (UPC) items/upc** Level III — — Item Commodity Code items/material** Level III — — Item Description items/description** Level III InvoiceLine Object (Name) — Item Quantity items/quantity**     — Item Unit of Measure (UOM) items/uom** Level III — — Item Net Cost items/netamnt** Level III InvoiceLine Object (fw1__Unit_Price__c * fw1__Quantity__c)InvoiceLine Object (fw1__Cash_Price__c * fw1__Quantity__c) Item Tax Amount items/taxamnt** Level III InvoiceLine Object (fw1__Sales_Tax__c) — Item Discount Amount items/discamnt**Level III

InvoiceLine Object (fw1__Total_Discount_Amount__c)

InvoiceLine Object (fw1__Total_Discount_Cash_Amount__c) Item Freight Amount items/frtamnt** Level III — — Unit Cost items/unitcost Level III InvoiceLine Object (fw1__Unit_Price__c)

InvoiceLine Object (fw1__Cash_Price__c)

Tax Exempt Indicator

taxexempt Level II (No salesforce field mapping
value = Y if taxamnt is 0 and N if taxamnt > 0) —

How Salesforce Supports Level 3 Data

Through Kulturra’s Payment Center integration, Salesforce fields are aligned with CardConnect’s API parameters. This ensures that when a payment is processed, the correct transaction level data is sent automatically, provided the fields are populated in Salesforce.

• If a field is missing, the transaction may only qualify for a lower level (e.g., Level I instead of Level III).

• Ensuring fields such as PO Number, Tax Amount, and Ship From Postal Code are consistently populated helps merchants maximize savings and compliance.

In summary, CardConnect Level 3 data mapping in Salesforce ensures merchants can process payments with maximum efficiency, qualify for lower interchange rates, and meet compliance requirements. By aligning API parameters with Salesforce fields, the integration simplifies this process for admins and end-users alike.

Availability: Summer '25