The B2B Interchange Optimizer helps merchants qualify for the best possible interchange rates when processing Purchasing and Corporate card transactions.

These card types can accept enhanced transaction data (Level II and Level III), which, when passed accurately, reduces interchange costs. Once enabled, Merchant automatically validates and supplements the required Level II and III data, ensuring merchants always receive optimal rates without any manual input.

Key Features:

Automatic Level II & III Optimization: MX™ Merchant automatically attaches enhanced data to qualifying transactions.
No Manual Entry Required: The app runs entirely in the background.
Supports Multiple Payment Types: Works with Quick Pay, Invoice, and Recurring Payments.
Consistent Savings: Helps merchants qualify for lower interchange categories without changing their existing payment flow.

Activating the B2B

From the MX™ Merchant dashboard, navigate to Apps.
Locate the B2B Interchange Optimizer tile and click Activate.
Review the app details and confirm by clicking OK.
- Clicking Cancel returns you to the App Store without activating.
After activation, the app appears under Active Apps.

Once activated, the B2B App works entirely in the background. No interface or workflow changes are required.

Eligibility and Requirements

All merchant types are eligible except those in the following MCC categories:

High-Risk Direct Marketing: 5962, 5966, 5967
Travel & Entertainment:
- Restaurants (5812, 5814)
- Hotels (3501–3833, 7011)
- Car Rentals (3351–3441, 7512)
- Truck/Trailer Rentals (7513)
- Airlines (3000–3299, 4511)
- Cruise Lines (4411)
- Passenger Railways (4112)
- Travel Agents (4722)

Only merchants processing with the MX™ B2B Interchange Optimizer App activated will receive the benefits.

To identify merchants that could benefit from B2B optimization:

Check merchant statements for corporate or purchase card volume (terminology varies by processor).
Use reports that provide detailed insights by interchange category.

AVS (Address Verification Service) Requirements

Keyed Transactions: AVS details are mandatory.
Card Present: ZIP code must match.
Card Not Present: AVS entry is required, but a match is optional.
Vaulted Customers: If AVS data is stored in Customer Vault, it auto-populates during payment.

💡
Best Practice: Always ensure AVS data is entered correctly to minimize fraud and maximize qualification.

Pricing (Admin)

Pricing is configured in PCE ISO/Agent at the portfolio and merchant levels. Contact your reseller/admin to review or update it.

How It Works

Once activated, PCE automatically identifies Purchasing and Corporate card transactions and adds the required data for Level II and Level III qualification. Processing a sale involves sending the customer's payment details to our API.

Make a POST request to /checkout/v3/payment endpoint with required parameters.

Parameter	Required	Description
`amount`	✓	Amount to charge (in USD currency)
`cardAccount`	✓	Valid Payment Card details or a vaulted token Note: You can vault the card for future use using Card Vaulting guide
`merchantId`	✓	The Merchant's unique identifier that is used to process the payment.
`tenderType`	✓	Set to `CARD` for card transactions.
`paymentType`		Type of transaction. It is defaulted to `Sale`
`customerName`		The name of the customer. Recommended for guest checkout where the card is not vaulted.
`posData`		An object containing Point of Sale data. While optional, we highly recommend including this object for all keyed (card-not-present/online) transactions to improve approval rates and potentially lower processing fees. You can view more details of the recommended POS data based on presentment type here.

Our system will processes the payment and returns a response indicating the outcome. You can learn the outcome of the request via GET /checkout/v3/payment/{id} or wait for the Payment webhook You can determine the result by checking the status and responseCode fields in the response.
1. status: The primary outcome of the transaction, either Approved or Declined.
2. responseCode: A detailed code explaining the reason for the status. See our comprehensive Response code guide guide for full list
For every approved payment, it is critical to store two identifiers
1. id : The unique Payment ID. Use this for retrieving or voiding the transaction before it settles.
2. paymentToken: The secure Transaction Token. Use this for follow-up actions like refunds or adjustments after the transaction has settled.

The B2B Optimizer is entirely automated — no manual intervention or data entry is needed for merchants to benefit from lower interchange rates.

If merchants manually enter enhanced data (e.g., tax, invoice number), that information overrides system-generated data.

Merchants must settle batches daily to ensure qualification for the best interchange rates.

Enhanced Data Fields

Level II Fields

Field	Description
Invoice Number	Pulled from Quick Pay or Invoice; generated if missing.
Client Reference Number	Uses customer number if available; otherwise generated.
Customer Code / PO Number	System generated.
Product Code	“MISC” (system generated).
Product Description	“MIS” (system generated).
Unit of Measure	“EA” (system generated).
Quantity	“1” for Quick Pay; actual item quantity for Invoices.
Unit Price	Transaction subtotal.
Discount Amount / Rate	Uses merchant-entered value or defaults to 0%.
Tax Amount / Rate	Uses merchant-entered value or defaults to 7% (reporting only).
Extended Amount	Total payment amount (including tax and discount).

Level III Fields

Field	Description
Ship-From ZIP	Merchant’s corporate ZIP (from MXA).
Ship-To ZIP	System generated.
Destination Code	System generated.
Invoice Number	Uses entered or system-generated value.
Order Number	System generated.
Item Product Code	“MISC”.
Item Commodity Code	Merchant’s MCC (Visa only).
Item Description	System generated.
Item Quantity	“1” (Quick Pay) or invoice item quantity.
Item Unit of Measure	System generated.
Item Extended Amount	System generated.
Freight Amount	0.
Duty Amount	0.

PCE transmits L2/L3 data, but card brands and processors determine the final interchange category. Ensure data accuracy and retain documentation supporting tax, freight, and itemization.

Troubleshooting

Downgraded despite B2B optimizer: Check that tax is set correctly, at least one item line exists with qty × unit cost, and destination details are present.
Gateway/device limitations: Confirm your gateway and device support full L3; if not, aim for L2.
Partial authorizations or edits after settle: Post‑settlement changes don’t re‑qualify prior transactions.

Not all gateways or device integrations support full L3 data sets. Missing or inaccurate fields can cause interchange downgrades.