Small business.
Credit card
processing.

01 / Start with the business

The best processing setup fits the way you actually sell.

A coffee shop taking hundreds of small payments has a different problem from a contractor collecting deposits, an online store shipping orders, or a consultant billing a few large invoices. A low headline rate cannot tell you which system fits any of them.

Small business credit card processing is the combination of an acceptance method, a processing relationship, and a funding arrangement that lets your business accept card payments. Choosing it well means checking the checkout experience, complete cost, funding schedule, support, and contract together.

You do not need to become a payments engineer. You do need to know who is responsible when a payment fails, a deposit is late, or a customer asks for a refund. The terminal or checkout is the part customers see; the merchant agreement determines much of what happens behind it.

Know the five pieces you are buying

• Checkout or terminal: where the customer presents a card or compatible digital wallet.
• Gateway: the technology that securely connects a payment interface to processing services, particularly online.
• Processor: the service that handles payment messages and transaction processing.
• Acquiring relationship: the arrangement that enables your business to accept card payments. Mastercard describes an acquirer as the licensed financial institution helping a merchant accept its cards. [1]
• Business bank account: the account receiving your payouts. This is separate from a dedicated merchant processing account.

One provider may package several pieces together. Another may combine an independent gateway, acquiring bank, and software vendor. Both can work. Ask for the names of the parties, the agreements you will sign, and the support contact for each part.

02 / Choose the relationship

Payment facilitator or dedicated merchant account?

A payment facilitator can bring onboarding, payment tools, and account management into one service. In Mastercard’s definition, it is a provider registered by an acquirer to facilitate transactions for submerchants. A dedicated merchant account establishes a business-specific acquiring relationship, often arranged through a bank, processor, or independent sales organization. [2]

Neither label proves that a service is cheapest, that approval is automatic, or that funds cannot be held. Both models involve eligibility requirements, risk review, and contractual obligations. Compare the actual offer and the accepted business activities.

Do not confuse the account model with the pricing model

Flat-rate, interchange-plus, and subscription pricing describe how charges are calculated. They do not, by themselves, identify the legal account arrangement. Likewise, “payment service provider” can describe several kinds of service; ask how your business is enrolled rather than relying on the marketing label.

There is no universal revenue line at which every merchant should switch. A business processing $15,000 in 3,000 small purchases has different economics from one processing the same amount in 30 invoices. Software requirements and the cost of changing systems also matter.

Go deeper: merchant accounts versus payment facilitators and how merchant accounts work.

03 / Understand the full bill

Credit card processing fees: the percentage is only the beginning.

Visa distinguishes interchange—the fee exchanged between acquiring and issuing institutions—from the merchant discount negotiated with the merchant’s financial institution. A network interchange table is therefore not a complete merchant quote. [3]

Your expense can include transaction charges, account and gateway fees, software, equipment, and charges triggered by particular events. Separate recurring commitments from costs that rise with sales, then calculate them for the same month.

The common pricing structures

• Flat-rate: a stated percentage, often plus a transaction charge, for a defined category. The price can differ by channel, plan, or other conditions.
• Interchange-plus: underlying interchange and specified network charges plus the provider’s markup. Helcim’s published disclosure illustrates a percentage and per-transaction margin added to those underlying charges. The markup alone is not the total rate. [4]
• Tiered: transactions are grouped into pricing categories. Request the qualification rules and an estimate of the share falling into each category.
• Membership or subscription: a recurring charge combined with a transaction schedule. Include the membership cost when comparing quiet months and seasonal sales.

Published schedules demonstrate why the channel matters. Square distinguishes in-person, online, API, and manual-entry or card-on-file payments, with plan-specific pricing. This is a provider example, not a universal rate chart or a recommendation that one provider fits every business. [5]

A small transaction can carry a large effective percentage

Consider a hypothetical 2.6% + $0.15 transaction price. This is an arithmetic illustration, not a NUMUS quote, market average, or offer.

At $10,000 of monthly card sales, 1,000 purchases of $10 would produce $410 in modeled transaction charges. Two hundred purchases of $50 would produce $290. The same volume and advertised rate generate a $120 difference because the transaction count changed. Software and other fees are excluded.

Use a consistent monthly comparison

Modeled monthly cost = percentage charges + transaction charges + recurring charges + applicable event charges. For interchange-plus, estimate the underlying costs using the actual card and transaction mix; do not enter just the markup as if it were an all-in rate.

A simple effective-cost measure divides the included charges by gross processed card sales for the same period. For example, $390 of included charges divided by $12,000 of card sales is 3.25%. State what you included. An all-in operating comparison that includes POS software is different from a processing-only measure.

Do not count the face value of a refund as a processing fee, or treat money held in reserve as permanently lost expense. Both affect available cash, but they belong in separate rows. Refunds can still leave costs behind: Stripe, for example, states that its original processing fees are not returned when a successful payment is refunded. Your agreement may differ. [6]

Use our processing fees guide for statement categories, and pricing-model comparison for a closer look at how quotes are structured.

04 / Build the checkout around the customer

In person, online, on the road, or by invoice?

The best small business payment system should support the transaction you make every day and the exception that occurs on a busy Friday. Demonstrate the entire workflow before buying hardware or signing a software contract.

For remote payments, a hosted payment page or invoice link can keep customers from reading card details to an employee. Confirm how the link is created, how the customer recognizes your business, and whether payment confirmation automatically updates the invoice.

If you operate both a store and a website, ask whether inventory, refunds, customer records, and reporting truly work across channels. Two interfaces carrying the same logo do not prove that an online order can be refunded at the counter.

For larger invoices, adding bank payments may be worth exploring alongside cards. Compare the authorization, return, and funding process as carefully as the price. Our ACH and credit card processing guide explains the two methods.

05 / Know when cash becomes usable

Approved payment does not mean available bank balance.

There are several milestones between a card tap and money available to pay suppliers. Understanding them helps you ask better questions when a payout is delayed.

1. Authorization: the issuer approves the payment request and generally places a hold against available funds or credit. Where capture is separate, the authorization must be captured before it expires. [7]
2. Capture and settlement: the transaction is submitted for financial processing and settlement through the relevant institutions. Check whether your system captures automatically and when its daily batch closes.
3. Payout: proceeds become eligible under your account terms and are sent to your bank. Provider availability, payout scheduling, and bank posting are separate considerations. Stripe’s documentation explicitly distinguishes these stages. [8]

Ask about the first payout separately from the usual schedule. Also confirm cutoff times and time zones, weekend and holiday treatment, charges for accelerated funding, and circumstances that can trigger review. “Next day” is incomplete without those details.

A useful planning question is: “If we take a large payment late Friday before a bank holiday, when could it reach our bank, and what could change that date?” Have the provider explain the same example for a refund and a negative balance.

If a reserve is proposed, obtain the amount or percentage, holding period, release mechanics, and conditions that may extend the hold. Put the working-capital effect into your forecast separately from processing expense. Review our reserve guide and questions to ask when a payout is delayed.

06 / Protect the payment and the relationship

Security and dispute handling belong in the buying decision.

A small team needs security controls it can actually maintain. Start by reducing the card data your staff handles, limiting account access, and making responsibility clear.

Understand your PCI responsibilities

Using a third-party processor does not remove all PCI DSS responsibilities. PCI SSC says merchants should verify the provider’s compliance for the relevant services, document responsibilities, monitor status, and confirm their own validation obligations with the organization managing the compliance program. The appropriate questionnaire depends on the actual setup. [9]

Ask what changes if you add telephone orders, a new checkout integration, or another terminal. A paid “PCI fee” is a billing line; it is not evidence that your business has completed its required work.

• Use individual staff accounts and appropriate permissions; enable multifactor authentication where available.
• Keep payment software and supported devices updated, and remove access promptly when staff leave.
• Use the provider’s supported payment interface instead of collecting card details in ordinary email, chat, or spreadsheets.
• Never retain the card verification code after authorization, even with customer permission. PCI SSC explicitly prohibits that practice. [10]
• Keep a device inventory and inspect applicable card-present terminals for tampering or substitution. Train staff to question unexpected equipment changes. [11]

Build the evidence before a dispute arrives

A chargeback is not the same as a refund you initiate. A customer contests a charge through their issuer; the process can remove funds and create fees while the case is reviewed. Providers have response deadlines and evidence procedures. Stripe’s dispute documentation shows why an owner needs an assigned response process, not just an unread email alert. [12]

Keep the order or service agreement, the terms presented at purchase, delivery or completion records, and relevant customer communication. Use a recognizable statement descriptor and an easy-to-find support contact. For subscriptions, retain the authorization and cancellation history. These practices help explain what happened; they do not guarantee a dispute will be won.

Assign a primary person and a backup to review disputes and provider requests. A busy small business should not discover its submission deadline after the only person with access returns from vacation.

07 / Compare the offers

Ask every provider the same questions.

A useful shortlist might include an integrated POS platform, an online-focused provider, and a merchant-account proposal built around your business. Evaluate the same sales channels and software needs. A stripped-down processing price cannot fairly compete with a quote that includes your entire POS subscription.

Give each provider the same transaction profile. Existing businesses can use several representative statements, including a normal and a busy month. New businesses should label estimates clearly and show the assumptions behind average ticket, transaction count, and expected sales.

1. Business eligibility: Is our actual product, fulfillment model, location, and sales channel supported?
2. Complete cost: What will a representative month cost, with every required charge included?
3. Exceptions: What changes for refunds, disputes, international cards, manual entry, and faster funding?
4. Operating limits: What are the approved volume and ticket limits, and how do we request changes?
5. Funding: What is the first and normal payout schedule, and what holds or reserves may apply?
6. Software and equipment: What is included, what is optional, and what requires another contract?
7. Support: Who answers during our trading hours, and how do we escalate a funding problem?
8. Exit: What notice, renewal, termination, equipment, or migration obligations apply?

Request written answers and a sample statement. Check whether an equipment lease has a separate term from the processing agreement. Record any introductory pricing, monthly minimum, annual charge, or cancellation window rather than assuming the advertised offer lasts indefinitely.

Compare a low-volume month as well as a busy one. A lower variable rate with higher fixed charges may be attractive at one volume and expensive at another. Calculate your own crossover using complete offers; a generic “switch at $10,000” rule cannot resolve that tradeoff.

Also price the work. If a new system saves $40 a month but creates two hours of manual reconciliation, the fee reduction may not justify the change. Equally, do not pay for a large software bundle when your business only needs a reliable terminal and clear reporting.

Bring the processing quote comparison guide and merchant agreement questions to your next provider conversation.

08 / Make a controlled change

Switch processors without making checkout the experiment.

Start with the dependencies: POS software, website checkout, invoicing, stored cards, subscriptions, gift cards, accounting exports, and open disputes. Decide which records must remain accessible after the old account stops taking payments.

Saved payment details need a migration plan. A token in one provider’s system may not be directly usable in another. Ask both providers what can move, who handles the transfer, and how customer and subscription records will be matched. Stripe’s migration documentation describes provider coordination, record mapping, and customer-update planning; this is a useful example of the work involved. [13]

1. Confirm approval and terms. Resolve outstanding requirements and confirm the intended sales channels before routing live transactions.
2. Configure and test. Use the provider’s test environment where available, then follow its approved production-verification procedure. Cover sale, decline, receipt, refund, and reconciliation.
3. Train the team. Practice the exception cases, including failed connectivity and a refund from a previous day.
4. Set a cutover. Define when each channel changes, who checks the first payouts, and how you will avoid duplicate recurring charges.
5. Close deliberately. Follow cancellation instructions after resolving data access, refunds, disputes, equipment, and residual balances.

Keep the migration owner and provider contacts in one short checklist. You want someone responsible for confirming that “payment accepted” becomes the correct order record, receipt, accounting entry, and bank deposit.

09 / Prepare a clear application

Help the provider understand the business you are building.

A good application gives a reviewer a coherent picture: who owns the business, what customers buy, how you collect payment, and when you deliver. Inconsistent names, unexplained volume estimates, and missing policies create avoidable follow-up work.

Have your legal and trading names, business contact information, ownership details, website or sales materials, bank information, and relevant supporting documents ready. Established businesses should prepare available processing statements. Startups should explain their estimates and current stage rather than inventing a processing history.

Be specific about subscriptions, deposits, preorders, unusually large tickets, or products that require specialized review. Disclose previous processing issues accurately and explain what changed. An application is the beginning of underwriting, not a promise of acceptance, a particular rate, or a funding schedule.

Before you begin: review our application checklist or startup processing-estimate guide.

10 / Questions business owners ask

Small business credit card processing FAQ

What is the best credit card processor for a small business?

The best fit supports your business model and sales channels at an understandable total cost, with workable funding, support, and exit terms. Compare complete offers using the same volume and transaction assumptions. A provider that suits a café may not suit a contractor or subscription business.

Can I accept credit cards without a dedicated merchant account?

Yes. A payment facilitator arrangement may let your business accept cards as a submerchant. You still have an agreement and eligibility requirements. Confirm the account structure, supported activities, and obligations before treating an activated dashboard as approval for every kind of sale.

Is interchange-plus always cheaper than flat-rate pricing?

No. Compare the full underlying charges and markup, transaction count, monthly costs, and included software. An interchange-plus markup is not an all-in processing rate. The result depends on the actual proposals and transaction mix.

What does “no monthly fee” leave out?

It describes one charge category. Transaction fees, equipment, optional software, disputes, international cards, or other applicable charges can still exist. Ask for a complete schedule and confirm what your required setup will cost.

Can a startup apply without processing statements?

A startup can seek review, but requirements vary by provider and business model. Present truthful sales estimates, business records, and the documents available to you. Explain that you are new instead of treating missing processing history as something to disguise.

Can I pass processing fees to customers?

Do not add a generic checkout fee without reviewing your program. Surcharging, cash discounts, and dual pricing have different mechanics and requirements. Confirm the proposed setup with your acquirer and qualified advisers for the places you operate. Visa publishes specific merchant surcharging guidance. [3]

Will changing processors move my subscriptions automatically?

Do not assume so. Confirm saved-payment portability, customer-record mapping, billing schedules, consent records, and cancellation handling. Plan how customers will update payment details if a credential cannot migrate, and prevent the old and new systems from billing the same renewal.

Research notes

Primary sources and further reading

Source material reviewed October 22, 2026. Provider documentation describes that provider’s service; it is not a universal promise or a NUMUS price quote. Rates, features, and account terms can change. Numerical scenarios in this guide are clearly labeled illustrations.

1. Mastercard: frequently asked questions — acquiring relationships and merchant acceptance.
2. Mastercard: payment facilitators — definition and registration relationship.
3. Visa: rates, fees, and rules — interchange, merchant discount, and links to surcharging guidance.
4. Helcim: United States fee disclosures — one provider’s interchange-plus structure.
5. Square: processing fees, plans, and software pricing — channel and plan distinctions.
6. Stripe: refund and cancel payments — refund treatment and original processing fees.
7. Stripe: separate authorization and capture — authorization holds and expiry.
8. Stripe: receive payouts — settlement availability, payout schedules, and bank timing.
9. PCI SSC: outsourced processing responsibilities — merchant responsibilities when using third parties.
10. PCI SSC: storage of card verification codes — prohibition on retention after authorization.
11. PCI SSC: point-of-interaction device protection — device inspection, tampering, and substitution.
12. Stripe: how disputes work — dispute handling, debits, and evidence response.
13. Stripe: payment-data migration overview — coordination and customer/payment-record mapping.