Interchange optimisation · B2B
topropay captures Level 2 and Level 3 line-item data on B2B and commercial-card authorisations, validates it against scheme rules and forwards it to the connected Visa or Mastercard acquirer routing the transaction. The result: reduced interchange on eligible transactions across the panel.
Consumer card
Standard interchange; the default on any card sale.
Commercial card + basic data
Tax amount and customer reference fields captured on authorisation.
Commercial card + line-item data
Full line-item data forwarded to the scheme for the lowest-tier interchange qualification.
Connected acquirers
Same L2 / L3 fields flow across every Visa / Mastercard acquirer in the panel.
L2 vs L3
Nine data-field categories — which ones L2 captures, which ones L3 adds. L3 typically qualifies for lower interchange than L2 on the same commercial card.
Key benefits
Four properties that show up in production the moment commercial-card volume starts clearing at reduced interchange rates.
Commercial (business, corporate, purchasing) and government (GSA) cards qualify for reduced interchange when the merchant supplies Level 2 / Level 3 data on the authorisation. On high-ticket B2B volume, the interchange delta shows up in every reconciliation cycle.
topropay's orchestration layer captures L2 / L3 fields once and forwards them to whichever connected Visa or Mastercard acquirer routes the authorisation. The merchant doesn't rebuild the capture per provider.
L3 requires strict field formats — tax amounts, unit costs, product codes, commodity codes. The platform validates fields on submission so merchants don't discover L3-qualification failures during monthly reconciliation.
Visa and Mastercard update L2 / L3 requirements periodically. topropay keeps the field lists current — the merchant doesn't monitor scheme bulletins to stay qualified.
How level 2 level 3 processing works underneath
What happens between the merchant's checkout submitting the order and the scheme evaluating whether the transaction qualifies for reduced interchange.
The merchant's checkout or ERP already has line-item data on B2B orders — SKU, description, quantity, unit price, tax. That data feeds into the platform API alongside the standard authorisation payload.
The API validates every L2 / L3 field per Visa / Mastercard scheme rules before the authorisation is routed. Formatting errors surface at submission, not at monthly reconciliation.
The routing engine picks the best-fit connected acquirer for the authorisation, weighted for L2 / L3 support and current interchange programme membership.
Authorisation is sent with the full L2 / L3 payload; the acquirer forwards to the scheme; scheme evaluates for reduced-rate qualification during clearing.
Settlement rows in the unified ledger include the interchange rate at which each transaction cleared — and any L3 qualification failures with their reason codes for follow-up.
Main use cases
Six recurring merchant shapes where commercial-card volume is dense enough for interchange optimisation to matter in the P&L.
High-ticket wholesale, industrial supply and manufacturing orders paid on commercial cards — the archetypal L3 use case, with clear line-item data on every invoice.
GSA and government purchasing cards routinely require L2 / L3 data; suppliers to public-sector buyers see meaningful interchange reduction when the data is forwarded correctly.
Corporate cards on travel bookings, hotel stays and rental cars where L2 / L3 fields (folio, per-day rate, cost centre) push the transaction into reduced interchange.
Enterprise SaaS invoices on corporate cards — line-item description, quantity (seats), unit cost and tax feed straight into L3 fields.
Fleet cards used at fuel or maintenance vendors — product codes, litres / gallons, unit price on the line-item breakdown.
High-ticket medical equipment and supplies sold to licensed healthcare buyers — L3 line-item data supports interchange reduction on the payment layer (PHI / patient adjudication are entirely separate and out of scope).
Platform features
Twelve capabilities grouped into data capture, routing & scheme integration, and reconciliation & analytics. Every capability applies across the connected acquiring panel.
Tax amount / rate, customer reference / PO number captured on authorisation.
Up to the scheme-defined maximum line items per transaction; description, quantity, unit cost, unit of measure per item.
Merchant-supplied UNSPSC or scheme-defined product codes forwarded to the acquirer.
Format, length and required-field checks before the authorisation leaves the platform.
L2 / L3 field capture and forwarding across the connected Visa and Mastercard acquirer panel.
Where the connected acquirer supports it, enhanced-data forwarding for Amex and Discover BIN ranges.
The routing engine weights acquirers by current L3-qualification programme membership and historical acceptance rate.
Field definitions updated as Visa and Mastercard revise the L2 / L3 requirement matrix.
Every settlement row tagged with the interchange programme it cleared under — L1 consumer, L2 commercial, L3 large-ticket, etc.
L3 qualification failures surfaced per transaction with the acquirer's rejection reason for merchant follow-up.
Blended and interchange-plus rate calculation across the ledger — helping finance track the interchange delta from L2 / L3 capture.
L3 qualification rates surfaced per connected acquirer so routing weights can rotate to the best performer per BIN range.
Trust & compliance
One audited environment on the orchestration side plus current scheme-rule alignment per acquirer. Sub-merchants inherit posture without carrying separate certifications themselves.
Ready to shrink interchange
A 30-minute B2B rate review looks at your commercial-card mix, the connected acquirers relevant to your geographies, current L3 qualification benchmarks per acquirer, and a sandbox to test the data pipeline before any commercial commitment.
Frequently asked
Definitions, rate mechanics, qualification requirements, card-product coverage and the practicalities of running L2 / L3 through one orchestration platform.
Level 3 payment processing is a Visa / Mastercard interchange-qualification programme that lets merchants supply detailed line-item data (SKU, description, quantity, unit cost, tax, freight and other fields) on commercial and government-card transactions. When the data meets scheme requirements, the transaction qualifies for reduced interchange — the fee the issuing bank charges the acquirer, ultimately reflected in the merchant's effective rate.
Level 2 processing captures a smaller enhanced-data set (tax amount, customer reference / purchase-order number) on top of the standard cardholder fields. Level 3 processing goes further with per-line-item data — description, quantity, unit price, unit of measure, product / commodity code, plus freight, duty and ship-from / ship-to postal codes. L3 typically qualifies for lower interchange than L2 on the same card.
Level 3 processing rates depend on the card product (commercial vs corporate vs purchasing vs GSA), the scheme, the amount and the interchange programme in effect at the time. As a rough guide, Visa and Mastercard publish interchange tables that show L3-qualifying commercial cards at rates meaningfully below the L1 or standard-commercial rates — often 0.5–1.0 percentage points lower on eligible transactions. The exact rate is set by the schemes, not by topropay.
Level 2 level 3 processing on topropay is a single capture surface. The merchant supplies L2 fields on every commercial-card authorisation and adds line-item data (L3) where the order has that structure. The platform routes the authorisation to a connected acquirer that supports the relevant programme and forwards the full enhanced-data payload; the scheme evaluates qualification during clearing.
Level 3 processing requirements include: a commercial or government-issued card, a merchant category acceptable for the interchange programme, correctly-formatted L2 fields (tax amount, customer reference), and per-line-item L3 fields (description, quantity, unit cost, unit of measure, product code, plus freight, duty, ship-from / ship-to where applicable). Fields must pass scheme format checks at authorisation; missing or malformed fields drop the transaction back to a higher interchange tier.
Visa Business, Visa Corporate, Visa Purchasing, Visa GSA, Mastercard Business, Mastercard Corporate, Mastercard Business World, Mastercard Purchasing, and various government-card BIN ranges qualify. Consumer cards do NOT qualify — L2 / L3 fields on a consumer BIN are captured harmlessly but don't change interchange. BIN identification on the platform surfaces the card product per authorisation.
American Express and Discover have their own enhanced-data programmes similar in shape to Visa / Mastercard L2 / L3. Where the connected acquirer supports Amex or Discover enhanced-data forwarding, topropay captures and forwards the equivalent fields. Support varies per connected acquirer.
The interchange delta scales with transaction size, so the higher the average B2B ticket, the more L3 pays off. Most merchants see a clear ROI at average tickets above roughly $500 US (or equivalent), and a very strong ROI on transactions over $2,500. Below $100 tickets, the delta is usually too small to justify the ERP-integration work on the merchant side.
No. L3 qualification is per-transaction — only the transactions where the merchant supplies full line-item data are evaluated for L3 rates. Transactions without line-item data clear at whatever interchange programme the card product qualifies for on the standard field set (usually L2 if L2 fields are present, L1 otherwise).
The platform runs format and required-field validation on submission: numeric fields are numeric, date formats match scheme specs, tax amount vs tax rate is consistent with the transaction amount, line-item quantities and unit costs multiply to the item total, etc. Validation failures surface as API error responses so the merchant fixes the data at capture time rather than discovering the failure at reconciliation.
The transaction still clears — nothing fails the buyer's checkout. It simply clears at the higher interchange tier (L2 or L1 as applicable) instead of L3. The rejection reason is captured in the settlement row of the unified ledger so the merchant can investigate and adjust the data pipeline.
No — L2 / L3 field capture is separate from PCI DSS. PCI DSS governs how card data is stored, transmitted and processed; L2 / L3 governs which non-card-data fields the acquirer forwards to the scheme for interchange evaluation. topropay's PCI DSS Level 1 posture covers the card-data side; L2 / L3 fields are non-sensitive commercial data.
Yes. PSPs and resellers reselling topropay's platform inherit the L2 / L3 capture and forwarding capability. They can configure it per downstream merchant, keep the merchant relationship, and route their downstream merchants across the same connected Visa / Mastercard acquirer panel.
The platform-side capability is on from day one; the timeline is entirely on the merchant's ERP / checkout integration to pass line-item data. Most merchants with structured order data go from decision to first L3-qualifying transaction in 1–3 weeks. Merchants without structured line-item data typically start with L2 and add L3 as their data pipeline matures.
L3 processing is most established in the US (where the majority of purchasing-card and GSA volume is concentrated) but Visa and Mastercard also operate commercial-data programmes in Europe, the UK, APAC and LATAM. Availability per market depends on the connected acquirer's programme membership; the platform routes L3-eligible authorisations to the acquirer that supports the programme in the relevant region.
Related