B2B Credit Card Processing Fees

Published August 6, 2026 · Updated August 6, 2026

Business-to-business payment processing carries its own cost profile. Most B2B invoices are paid remotely — through a hosted payment link, a virtual terminal, or a customer portal — which means the majority of B2B card transactions are card-not-present. Commercial and corporate cards are common in B2B purchasing and typically carry different interchange structures than standard consumer cards. This guide explains what B2B companies pay to accept cards, how commercial-card data affects cost, and how to calculate and review your company's effective processing rate. See the full guides list for related topics.

1. What B2B companies pay to accept cards

When a business customer pays an invoice by card, the full amount does not arrive in your account. A portion is retained as processing cost. That cost is made up of several distinct components, and no single advertised rate captures all of them.

B2B companies often process fewer but larger transactions than consumer-facing businesses. A higher average ticket means the percentage-based portion of processing costs carries significant weight — even a fraction of a percent on a $5,000 invoice represents meaningful dollars. At the same time, B2B customers frequently pay with commercial, corporate, or purchasing cards that carry different interchange structures than standard consumer cards. Understanding both of these dynamics is the starting point for evaluating B2B payment processing costs. For a thorough breakdown of each fee type, see the guide to merchant account fees explained.

2. Why B2B invoice payments are often card-not-present

Card networks classify transactions based on how and where a card is used. A card-present transaction occurs when a physical card is read at the point of sale — chip inserted, card tapped, or stripe swiped. A card-not-present (CNP) transaction occurs when the card is not physically read: the payer enters card details into a payment page, a staff member keys the number into a virtual terminal, or a card on file is charged.

Most B2B invoice payments are card-not-present. Business customers typically pay invoices through a link emailed to them, through a customer portal, or by reading a card number over the phone. Unlike a retail store with a physical checkout counter, B2B companies often have no card-present terminal at the point of payment. The card-not-present environment generally results in higher applicable interchange compared with in-person card-present alternatives for the same card, all else equal. This is a structural cost consideration for business-to-business payment processing.

Visa publishes its U.S. interchange rates at usa.visa.com and Mastercard at mastercard.com. These schedules can and do change. For a full comparison of how transaction method affects pricing, see the e-commerce processing fees guide, which covers similar card-not-present dynamics in detail.

3. Components of a B2B processing bill

Interchange

Interchange generally passes between the acquiring bank (your bank) and the card-issuing bank (your customer's bank) on each transaction. It is set by the card networks, not your processor, and is only one component of the merchant discount rate you ultimately pay. Ordinary merchants cannot directly negotiate card-network interchange schedules; however, provider markup, gateway charges, fixed fees, and contract terms may sometimes be compared or negotiated.

Card-network assessments

Assessments are fees charged directly by Visa, Mastercard, Discover, and American Express for use of their payment networks. They are typically a small percentage of sales and appear as separate line items on interchange-plus statements. Like interchange, they are set by the networks and are not ordinarily negotiable by the merchant.

Provider markup

Your payment processor or service provider adds its own margin on top of interchange and assessments. This markup may be expressed as an additional percentage, a per-transaction fee, a flat monthly fee, or a combination. It is the component that varies most between providers and is most open to comparison and negotiation.

Per-transaction charges

A fixed dollar amount charged on each individual payment, regardless of invoice size. For B2B businesses with high average ticket sizes, per-transaction fees represent a smaller share of total cost than they would for a business with small average tickets. On a $500 invoice, a $0.20 per-transaction fee is 0.04% of the sale. On a $20 sale, the same fee equals 1.00%.

Gateway, integration, and invoicing-platform fees

B2B companies that send hosted invoice links, use accounts-receivable software with embedded card payments, or connect payment processing to an ERP system typically incur gateway or platform fees. These may be a monthly subscription, a per-transaction fee, or both. If billed on a separate invoice from your merchant account statement, include these costs when calculating your effective rate — omitting them understates your true B2B payment processing costs.

Monthly, statement, PCI, and other fixed fees

Fixed costs include monthly account or statement fees, PCI compliance or non-compliance fees, minimum monthly fees, and other recurring charges. A PCI non-compliance fee is charged when the required annual Self-Assessment Questionnaire has not been completed; completing those steps may prevent or remove this fee depending on your processor and agreement. Fixed fees add to total cost regardless of monthly volume.

Cross-border and international card charges

Transactions made with cards issued outside the United States may incur additional network fees — often called cross-border or international assessment fees — on top of standard interchange and assessments. B2B companies with international customers or suppliers should identify whether these fees appear on their statements.

Refund fees and dispute fees

Refunds reverse a payment. Treatment of the original processing fee on a refunded transaction varies by provider and agreement. Disputes (chargebacks) occur when a cardholder or their bank challenges a charge. Authorization approval does not prevent a customer from later filing a dispute. A provider may charge a dispute administration fee per case; whether it applies, is waived, or is returned varies by provider, agreement, and outcome. Merchants should review their own statements and contracts.

4. Business, corporate, fleet, and purchasing cards

Business customers commonly pay B2B invoices using commercial payment cards — including business cards, corporate cards, purchasing cards, and fleet cards. These card types carry different interchange structures than standard consumer credit or debit cards. Exact rates are not uniform across all commercial cards; they vary by network, card program, merchant category code, transaction type, and whether qualifying enhanced data is submitted.

The interchange structure for commercial cards reflects that card programs often include expense-management features, reporting tools, and controls that the issuing bank provides to the cardholder's employer. The published Visa USA Interchange Reimbursement Fee schedule contains separate programs and rate entries for commercial card environments. These schedules are not complete merchant quotes — they represent one component of the total cost a merchant pays. Review the schedule and your own statements to understand what card categories appear in your transaction history.

5. Level 2 and Level 3 enhanced transaction data

“Level 2” and “Level 3” are commonly used terms in B2B payment processing to describe additional commercial-card transaction data that can be submitted alongside the standard payment details.

What Level 2 data typically includes

Level 2 data may include items such as the tax amount and a customer code, invoice number, or purchase-order reference. The exact fields and terminology vary by card network, provider, gateway, card program, and transaction type. There is no single universal definition that applies identically across all networks and programs.

What Level 3 data typically includes

Level 3 data may include line-item detail such as product description, quantity, unit cost, tax amount, freight, or item commodity code. It is generally more granular than Level 2. As with Level 2, exact fields and requirements vary by network, provider, card program, and transaction. Visa provides guidance on commercial-card enhanced data in its Visa Developer documentation on enhanced line-item data.

Important limitations

Interchange is generally paid between the acquirer and issuer and is only one component of the merchant discount rate. Merchants ordinarily cannot negotiate network interchange directly. Provider markup, gateway charges, fixed fees, and contract terms may sometimes be compared or negotiated separately.

6. What affects B2B processing cost

• Average ticket size: Fixed per-transaction fees have a smaller proportional impact on larger invoices. The percentage-based component is the dominant cost driver for high-ticket B2B transactions.
• Transaction volume: Higher transaction count amplifies per-transaction charges and dilutes fixed monthly costs across more sales. Both affect the effective rate.
• Card mix: Standard consumer cards, business cards, corporate purchasing cards, and international cards each carry different interchange structures. The blend of card types your customers use directly affects your blended effective rate.
• Payment channel: Hosted invoice links, virtual-terminal entries, and card-present terminals are all handled differently for interchange purposes. Card-not-present channels typically carry higher interchange than card-present alternatives.
• Domestic versus international cards: Cross-border fees apply to transactions made with cards issued outside the United States and raise the blended cost for companies with international customers.
• Enhanced data submission: For eligible commercial card transactions, submitting Level 2 or Level 3 data through a supported integration may affect interchange qualification — but eligibility is not guaranteed. See Section 5.
• Refunds and returns: Refund-fee treatment varies by provider. Some retain the original processing fee on a reversed transaction. Both the original fee and any reversal fee count toward total cost.
• Failed authorizations and retries: Failed authorization attempts may generate fees depending on your provider. Retry practices that do not follow network rules can result in additional costs or account flags.
• Disputes and chargebacks: Authorization approval does not prevent a later dispute. Dispute administration fees vary by provider; whether they are charged, waived, or returned depends on the provider, agreement, and outcome.
• Gateway and integration fees: Invoicing platforms, ERP connectors, and payment gateways may charge separately from your merchant account. Include all processing-related charges when calculating your effective rate.
• Pricing model: Flat-rate, interchange-plus, tiered, and subscription-style pricing distribute costs differently for the same underlying card mix and transaction volume.

7. Payment method comparison

The table below summarizes the main cost factors and review points for payment methods B2B companies commonly use. It does not present fixed rates — actual costs depend on card type, network, your provider agreement, and other factors specific to each transaction. When choosing between payment methods, consider total cost, authorization requirements, customer preference, settlement timing, returns, disputes, reconciliation, and operational needs.

This table is for general comparison purposes only. It does not present fixed rates or benchmarks. ACH is a separate payment rail and is not credit card processing.

8. Pricing models for B2B companies

Payment processors offer several ways to structure fees. For a detailed comparison, see the guide to flat-rate vs. interchange-plus vs. tiered pricing and the Flat-Rate vs. Interchange-Plus Calculator.

This table is for general comparison purposes only. This guide does not recommend any specific processor or pricing model.

9. How to calculate your B2B effective processing rate

Your merchant statement contains everything you need. The How It Works page explains the formula in detail, and the effective-rate calculation guide walks through step-by-step instructions. For context on what your result means, see What Is a Good Effective Credit Card Processing Rate?

1. 1Collect at least three recent merchant processing statements from representative periods. Avoid months distorted by a large one-time fee, unusually low volume, or a high number of disputes.
2. 2Record total gross card sales — the full amount charged to customer cards — for each period. Use gross processed sales, not net deposits after fees.
3. 3Identify all processing-related fees: interchange, network assessments, provider markup, per-transaction fees, gateway fees, integration fees, monthly account fees, PCI fees, and any other charges on your statement.
4. 4If your gateway, invoicing platform, or ERP integration is billed separately, add those fees to your total for a complete effective-rate calculation.
5. 5Exclude ACH and bank-payment volume from your card effective-rate calculation — they use a different payment rail with a different cost structure.
6. 6Do not treat the principal amount of a disputed sale as a processing fee — only the dispute administration fee itself is a processing cost.
7. 7Avoid double-counting fees already included in a bundled total on the statement.
8. 8Divide total processing fees by total gross card sales for each period, then multiply by 100.
9. 9Compare results across multiple months to identify trends or unexplained fee increases.
10. 10Use the free Merchant Fee Analyzer calculator to confirm your numbers and compare with an alternative quote.

10. Hypothetical monthly calculation example

Notice that the 2.40% percentage-based charge is not the effective rate. The effective rate of 2.50% is higher because it incorporates per-transaction charges and gateway and fixed fees. This is why comparing a quoted percentage rate to your current effective rate — without accounting for all fee components — can produce an inaccurate cost estimate. The numerator (total fees) and denominator (gross card sales) must cover the same period. Use gross processed card sales, not net deposits. Exclude ACH volume from this calculation.

For guidance on reading each line of your statement, see How to Read a Merchant Processing Statement.

11. How to review a B2B merchant statement

For a detailed walkthrough of typical merchant statement sections, see the guide on how to read a merchant processing statement. For B2B companies, pay particular attention to:

• Commercial card interchange categories: On interchange-plus statements, each card type appears as its own line. Look for business, corporate, purchasing, and commercial card entries. Identify whether enhanced-data programs appear and whether your integration is submitting data correctly.
• Cross-border fees: If your company invoices international customers who pay by card, look for cross-border or international assessment line items. Identify what share of your volume is from internationally issued cards.
• Gateway and integration fees: Confirm whether gateway, ERP connector, invoicing-platform, or accounts-receivable integration costs appear on your merchant statement or on separate invoices. Include all charges in your effective-rate calculation.
• PCI compliance or non-compliance fees: Identify whether a non-compliance fee is being charged. If so, contact your provider for SAQ instructions.
• Dispute and chargeback fees: Note how many disputes occurred, the fee per dispute, and whether any fees were returned after resolution.
• Monthly minimums: If your processing fees fall below a contractual minimum in any month, you are charged the difference.
• Failed authorization fees: Some providers charge for failed authorization attempts in addition to successful transactions.
• Fee increases from prior months: Compare the current statement to recent months. Unexplained increases are worth querying with your provider.

12. Practical ways to reduce avoidable costs

The steps below are general suggestions. No guide can guarantee savings, qualification, authorization approvals, or chargeback prevention. Outcomes depend on your specific agreement, card mix, volume, and negotiation. For a more detailed review process, see the guide on reviewing and reducing processing costs.

• Calculate your effective rate across several representative statement periods before drawing conclusions. A single month with atypical volume, fees, or disputes can distort the calculation.
• Separate percentage, per-transaction, gateway, integration, fixed, refund, and dispute-related fees when reviewing statements so you can identify which components are largest.
• Review your commercial versus consumer card mix where statement reports provide it. Identify what share of transactions involve business, corporate, or purchasing cards.
• Separate card-present, card-not-present, domestic, and cross-border transaction activity if your statement reports these breakdowns.
• Confirm whether your integration submits enhanced transaction data and whether it is submitted correctly. Ask your processor or gateway which programs and fields are supported and whether the data is reaching the network. Never enter fabricated or placeholder values.
• When comparing quotes, use the same monthly card sales volume, transaction count, average ticket, card mix, and payment channels for each provider.
• Ask providers to break out interchange, network assessments, and their own markup separately so you can compare each component across quotes.
• Check for overlapping or duplicate fees from your processor, gateway, ERP integration, accounts-receivable platform, or invoicing software for the same service.
• Review failed authorization rates and retry practices. Retries that do not follow network rules can generate fees and account flags.
• Improve invoice descriptions, payment terms, and customer-service contact information to reduce the number of customers who dispute charges due to confusion.
• Review dispute patterns and the supporting transaction records you retain to respond to challenges.
• Evaluate suitable bank-payment alternatives such as ACH separately for larger or recurring invoices, considering total cost, settlement timing, return risk, and operational requirements.
• Complete your annual PCI Self-Assessment Questionnaire. Doing so may prevent or remove non-compliance fees depending on your provider and agreement.
• After any pricing change, recalculate your effective rate from actual statements to confirm the impact.

13. PCI DSS and safe invoice-payment collection

The Payment Card Industry Data Security Standard (PCI DSS) provides security requirements for environments where payment-account data is stored, processed, or transmitted. B2B companies that accept card payments are subject to PCI DSS requirements. The scope of your obligations depends on how invoice payments are collected and whether card data passes through your systems.

Recommended practices

• Use provider-hosted invoice links or other properly implemented provider-controlled payment solutions where appropriate to reduce the scope of card data your systems handle.
• Confirm your specific PCI DSS responsibilities with your processor, acquirer, gateway, invoicing platform, and other service providers. The type of Self-Assessment Questionnaire that applies depends on your integration method.
• Limit administrative access to payment systems and use multifactor authentication where supported.
• Keep software, payment plugins, and integrations updated.
• Avoid storing raw card details in any form. Use processor- or gateway-supported tokenization for card-on-file and recurring arrangements.
• Review access logs and transaction records regularly.
• Maintain clear recurring-payment consent, billing, and cancellation terms for customers.

Card details in messaging channels

Do not ask customers to send card details through ordinary email, SMS, text, or chat. If a messaging channel receives cardholder data, that channel and its related systems may enter PCI DSS scope and must meet the applicable security requirements. The PCI Security Standards Council has published specific guidance on cardholder data in messaging technologies. Use a provider-hosted payment link or a PCI-compliant provider-hosted virtual terminal instead.

When taking phone payments, enter the card directly into the provider-hosted virtual terminal without writing, recording, or retaining the details outside that system.

PCI DSS prohibits storing CVV, CVC, CID, or similar card verification codes after authorization, including for recurring or card-on-file payments. Customer permission does not override this restriction. See the PCI SSC's FAQ on card verification code requirements.

Hosted checkout does not remove every PCI responsibility, and tokenization does not guarantee lower fees or prevent disputes. PCI DSS documentation is available through the PCI Security Standards Council. This section is for general informational purposes only and does not constitute security or compliance advice.

14. B2B credit card surcharges

Some B2B companies consider adding a credit card surcharge to invoices. B2B transactions are not automatically exempt from card-brand rules or applicable law.

Visa's current U.S. surcharge rules

Under Visa's published U.S. Merchant Surcharge Q&A:

• A merchant must notify its acquirer at least 30 days before beginning to surcharge.
• Surcharges may only be applied to eligible credit card transactions. They must not be applied to debit cards or prepaid cards.
• The surcharge amount may not exceed the lower of the applicable merchant discount rate or 3%.
• Work with your acquirer or processor to ensure the surcharge is identified correctly.
• Appropriate disclosures are required at the point of payment and on the receipt.

State and local laws may impose additional restrictions that vary by jurisdiction and can change. Other card brands may have different or changing requirements. Do not treat surcharges, convenience fees, service fees, and cash-discount programs as interchangeable — each is governed by different rules and has different disclosure requirements. Not every B2B invoice can necessarily be surcharged under all applicable rules.

Before implementing any surcharge program, confirm current requirements with your processor or acquirer and with qualified legal counsel. This guide does not constitute legal, tax, financial, security, or compliance advice. See the full disclaimer.

15. Frequently asked questions

Related guides

16. Sources and methodology

This guide draws on publicly available materials from the following official sources. No fabricated statistics, invented benchmarks, or unverified third-party rates are used. All examples are hypothetical and labeled as such.

• Visa USA Interchange Reimbursement Fees (effective April 18, 2026)
• Visa — Credit Card Processing Fees and Interchange Rates
• Visa Core Rules and Visa Product and Service Rules
• Visa Developer — Supplier Matching Service and Level III Line-Item Data
• Mastercard — Interchange Rates and Fees
• PCI Security Standards Council — PCI DSS
• PCI SSC — Cardholder Data in Messaging Technologies
• PCI SSC — Card Verification Code Requirements
• Visa — U.S. Merchant Surcharge Q&A
• Nacha — ACH Payments Fact Sheet

Interchange schedules, network rules, PCI DSS requirements, and legal requirements change over time. Readers should verify current requirements directly with the relevant card networks, their payment provider, the PCI Security Standards Council, and qualified legal counsel before making decisions.