Transaction-level data
Tax, invoice or purchase-order information, customer references and location data where supported.
B2B & Commercial Card Optimization
Help every eligible transaction carry the data it needs.
Selective Pay maps Level II and Level III data, card-not-present controls, settlement practices and system integrations around your actual invoice, keyed and card-on-file workflows—so you can identify preventable downgrades and improve cost visibility.
- Commercial-card mix review
- Gateway and ERP data mapping
- Downgrade and effective-rate analysis
Line-item enrichment
Product detail, quantities, unit pricing, freight, discounts and destination data for eligible commercial-card transactions.
Qualification visibility
Connect the card mix, transaction method, gateway and operating controls to a measurable optimization plan.
The Qualification Gap
A low processor markup does not fix a transaction that settles with incomplete data.
Commercial-card costs depend on more than the quoted rate. Card type, entry method, merchant category, enhanced data, authorization controls and settlement behavior can all affect how a transaction is classified.
Data never reaches the network
The invoice, tax or line-item information may exist in your ERP or order system but never be transmitted through the gateway.
Card-not-present controls are inconsistent
Missing AVS or CVV prompts, unclear descriptors and avoidable settlement delays can create preventable qualification problems.
The statement hides the operating cause
A blended effective rate can show that costs are high without showing which card types, departments or workflows need correction.
Enhanced Commercial-Card Data
Level II and Level III are data standards—not a pricing slogan.
The correct fields depend on the card, network, transaction type and technology path. We determine what your systems can capture, what the gateway can transmit and where manual or automated enrichment makes sense.
Level II essentials
Transaction-level business data commonly used in B2B payment flows.
- Sales-tax amount
- Invoice or purchase-order number
- Customer or account code
- Merchant and destination ZIP information
- Consistent transaction and receipt data
Level III enrichment
Detailed line-item information for eligible purchasing and commercial-card transactions.
- Item description, SKU or product code
- Quantity, unit price and unit of measure
- Freight, duty, discount and tax detail
- Ship-from and ship-to information
- Commodity data where available
Selective Pay Optimization Process
Start with the transaction path. Then configure the processor.
We do not assume that turning on a Level III field solves the problem. The review follows the transaction from the customer, through your software and gateway, into authorization, settlement and reporting.
Analyze statements and card mix
Separate processor markup from interchange and assessments, identify commercial-card volume, review effective cost and locate recurring downgrade patterns.
Map each payment workflow
Document how invoice, keyed, ecommerce, card-on-file and integrated transactions originate and which systems touch the payment data.
Configure enhanced data and controls
Align gateway fields, ERP mappings, AVS and CVV prompts, descriptors, tax treatment, user roles and settlement practices.
Measure qualification after go-live
Review real transaction results, confirm the intended data is passing and refine the operating process when exceptions appear.
Where Optimization Fits
Build the data path around the way your team already takes payments.
Different entry methods create different qualification risks. The objective is a consistent commercial-card strategy across every department and channel.
Accounts receivable
Connect invoice and customer references to virtual-terminal, payment-link or integrated payment workflows.
Phone and back office
Standardize AVS, CVV, tax, order and descriptor practices for manually entered transactions.
Card-on-file
Use tokens, consistent customer references and controlled user access for repeat business payments.
ERP and ecommerce
Map transaction and line-item data from the order system through the gateway without unnecessary duplicate entry.
What the Review Covers
A statement analysis should explain where the cost comes from—not just quote a lower rate.
Selective Pay evaluates the pricing structure and the operating conditions that determine how transactions are submitted and settled.
Pricing and effective rate
Interchange, assessments, processor markup, authorization fees and other recurring costs.
Card and entry-method mix
Commercial cards, debit, rewards, keyed, ecommerce, recurring and card-on-file volume.
Qualification and downgrades
Reason codes, data gaps, settlement timing and transaction practices that may be correctable.
Gateway and processor capability
Whether the current platform can accept, enrich and transmit the needed commercial-card data.
ERP and software mapping
Where invoice, tax, customer and line-item data originates and how it reaches the payment network.
Reporting and accountability
How departments, locations and transaction channels can be monitored after implementation.
Important: Enhanced data does not guarantee a particular interchange category. Eligibility and qualification depend on the card, transaction, merchant category, data quality, network rules and processing environment.
Frequently Asked Questions
What B2B merchants usually ask before changing their payment setup.
Does every corporate card qualify for Level II or Level III pricing?
No. Qualification depends on the card product, network program, merchant category, transaction method, enhanced data and other processing rules. The goal is to help eligible transactions carry the right information and avoid preventable errors.
Can our current gateway or virtual terminal support enhanced data?
Many platforms support at least some Level II or Level III fields, but the available fields and automation vary. We confirm the processor, gateway, frontend and integration path before recommending a change.
Do employees have to enter every line item manually?
Not necessarily. Depending on the ERP, gateway and transaction path, data can be mapped or enriched automatically. Manual entry is evaluated only when it is practical and operationally sustainable.
Can card-on-file and invoice payments be optimized?
Yes, when the transaction and platform are eligible. The review includes tokenized card-on-file, invoice, keyed and ecommerce workflows as well as AVS, CVV, customer references and settlement practices.
What do you need for the initial analysis?
A recent processing statement is the best starting point. Transaction exports, gateway reports and a short explanation of how payments are accepted can make the review more precise.
Start With the Data
See how your commercial-card transactions are actually being categorized.
Upload a recent statement and Selective Pay will review the card mix, pricing, qualification patterns and technology path before recommending changes.