Merchant Services for Business: Pricing and Settlement

Separate card acceptance from the operating bank decision

A business can often use one institution for deposit banking and a different provider for merchant acquiring. The merchant services relationship covers card authorization, clearing, settlement, chargebacks and related processing, while the business checking account receives the net proceeds. Bundling can simplify support, but it should not prevent a company from comparing the economics and operational performance of each service independently.

For example, a restaurant may like its bank’s branch network but receive a better card processing package from a specialist that integrates directly with the point of sale system. The right comparison asks whether settlement can still reach the preferred bank on the required schedule, whether reconciliation remains clean and whether support is available when batches fail. Choosing a deposit bank solely because it offers merchant services can be expensive if the processing spread is materially higher.

Model the full processing cost at your real transaction mix

Merchant pricing can include interchange, network assessments, processor markup, monthly platform fees, gateway fees, equipment costs and additional charges for disputes or special transaction types. A single advertised percentage rarely describes the total cost. Businesses should model a representative month using actual card mix, average ticket size, keyed versus card present activity and transaction count.

If a company processes $400,000 per month, a 0.25 percentage point difference in effective cost equals about $1,000 per month before considering fixed fees. But the lowest headline rate is not always cheapest. A processor with lower markup but expensive gateway, chargeback and PCI fees may cost more overall. Calculate effective rate as total processing fees divided by card volume, then separately track equipment and one time implementation costs so finance can compare providers consistently.

Treat settlement timing as a working capital variable

Card revenue is not useful until it is available in the bank account. Settlement timing depends on processor rules, batch close time, weekends, holidays and risk holds. A retailer with $100,000 of daily card sales can create a meaningful liquidity gap if settlements arrive one day later than forecast. Treasury should record when each batch closes and when funds normally become available, then compare that expectation with actual deposits.

Test special situations such as Friday night sales, holiday weekends and manual batch closure. Some businesses also face reserves or delayed funding after unusual volume spikes, chargeback activity or underwriting review. Ask the provider what events can change normal funding. Cash forecasts should distinguish card sales from settled card cash so finance does not spend revenue before it is actually available to the operating account.

Understand chargebacks, reserves and account exposure

Merchant acquiring creates contingent exposure because cardholders can dispute transactions after the original sale. The processor may debit chargebacks, fees or reserves from the settlement account. Businesses with seasonal spikes, advance delivery or higher dispute rates should understand whether the agreement permits rolling reserves, funding delays or other risk actions. Those terms can matter more than a small difference in processing markup.

Build a process for chargeback notices and evidence deadlines. Assign ownership to operations or finance, and reconcile every debit back to the underlying transaction. If the processor deducts a $3,000 chargeback from a $40,000 daily settlement, accounting should identify the difference immediately rather than leaving an unexplained deposit variance. High dispute rates can also signal product, fulfillment or fraud problems that treasury alone cannot fix.

Treat PCI compliance and access security as operating requirements

Businesses that accept payment cards have responsibilities under the payment card security ecosystem. PCI DSS v4.0.1 is the current standard, and the future dated requirements associated with version 4 became effective on March 31, 2025. The exact validation method depends on the merchant environment and provider. A company should confirm its responsibilities with its acquirer or qualified security resources rather than assuming the processor handles everything.

Reduce exposure by keeping card data out of internal systems where possible, using validated payment technology and restricting administrative access. Merchant portal credentials can change bank settlement instructions, issue refunds or expose transaction data, so protect them with strong authentication and role based permissions. Review who can alter the settlement account. A compromised merchant portal can redirect cash even if the primary bank login remains secure.

Compare integrations and reconciliation before switching

The processor must fit the point of sale, ecommerce platform, accounting system and treasury process. Before signing, test the settlement report, fee detail, refund data and chargeback files that finance will use every day. A slightly more expensive provider can be cheaper overall if it removes several hours of manual matching and produces reliable settlement references.

Run parallel reconciliation for a sample period when possible. Confirm that gross sales, refunds, fees and chargebacks can be tied to the net deposit. Also plan for provider outages and account changes. Keep support contacts, expected batch times and a backup acceptance method appropriate to the business. The merchant service decision should improve revenue collection without turning the bank reconciliation into a daily investigation.

Editorial Verdict

Sources

• OCC Payment Systems handbook
• PCI Security Standards Council, PCI DSS v4.0.1

Primary, regulatory and payment network sources were checked for this update. Bank specific terms can change after publication.