Your guide to getting started with ZoomMate
Everything you need to start using ZoomMate: notes, search, workflows, and AI tools — all inside Zoom Workplace.
Select a language
Learn how to start taking credit card payments for your small business: setup steps, processing fees, security tips, and the right processor.
12 min read
Published on September 10, 2026
A customer wants to pay you right now, but your only options are a check they'll forget to mail or a bank transfer that takes three days to clear. That gap between wanting to get paid and actually getting paid is exactly why taking credit card payments matters for small businesses of any size, from a solo consultant to a five-person studio. The process involves more moving pieces than it looks like from the outside: merchant accounts, processors, equipment, and fee structures that affect how much of each sale you actually keep. This guide walks through the baseline requirements, the online and in-person methods available, what processing actually costs, and how to pick a setup that fits the way you run your business. If you're still refining how you bill clients in general, our complete invoice guide for small businesses is a useful companion to this one.
Invoice clients and collect payments in one place
Before you take your first card payment, a few pieces need to be in place. At the core, you need a payment processor (and in some cases a merchant account) to move money from a customer's card to your business bank account. You'll also want a dedicated business bank account so card revenue stays separate from personal funds, which makes bookkeeping and taxes far less messy. Beyond that, your equipment or software needs depend entirely on how you plan to take payments, whether that's in person, online, or over the phone.
A traditional merchant account is a dedicated account that holds card funds temporarily before they settle into your business bank account, typically set up through a bank and requiring its own approval process. A payment processor, by contrast, bundles the merchant account function with the software and equipment needed to actually run transactions. Most small businesses today use a bundled payment processor because it skips the separate merchant account application and can help simplify how quickly they start accepting payments.
What you need on the ground varies widely. A freelancer invoicing clients online might only need payment software, while a business selling at a market needs a physical card reader, and a service business taking calls needs a way to key in card details manually. The next few sections walk through each of these setups in detail.
Most freelancers and service businesses start taking cards online because it requires the least setup. A payment link is a shareable URL a customer clicks to pay with a card, and you can learn more about how to create and use payment links effectively if you want a deeper walkthrough. Online invoices go a step further by combining itemized billing details with a built-in pay button, so the customer sees exactly what they owe before paying. Recurring billing is worth setting up if you work with retainer clients or sell subscriptions, since it charges a saved card on a set schedule instead of requiring a new request each billing cycle. Businesses that sell products directly through a website often add an embedded checkout page instead, which keeps the payment step inside the site rather than sending customers to a separate link. For a broader rundown of these and other options, our guide on five simple ways to accept payments online covers the landscape in more detail.
A payment link can work well for quick, one-off requests where there's nothing to itemize, like a $150 deposit or a flat consulting fee. An online invoice makes more sense when the customer needs a documented breakdown, such as hours worked, materials used, or multiple line items with taxes and discounts applied. A freelance photographer might send a payment link for a same-day print order but switch to a full invoice for a wedding package with several deliverables. If you expect the customer to reference the document later for their own records or expense reports, the invoice format is the safer choice.
Taking a card payment in person, whether at a storefront, a weekend market, or a client's office, starts with a card reader or POS (point-of-sale) terminal. Small mobile readers plug into or pair with a phone or tablet over Bluetooth, which works well for a freelancer or a business that moves locations often. Standalone terminals make more sense for a fixed storefront that processes a steady volume of transactions each day.
Chip insert, tap-to-pay, and other contactless methods are now standard on most readers, letting customers choose whichever option feels most convenient to them. These card-present transactions typically carry lower processing fees than online payments because the physical card and chip reduce the risk of fraud, giving the processor more confidence that the customer is who they claim to be.
Once a payment clears, you can issue a receipt either digitally, by texting or emailing a copy, or in print if your terminal includes a receipt printer. A landscaper collecting a $400 payment after a job, for example, might tap a customer's card on a phone-based reader and send the receipt straight to their inbox.
Some customers can't or won't complete an online form, whether they're calling in with questions or simply prefer to read their card number out loud. A virtual terminal solves this by letting you manually key in card details from a computer or app, turning any device with internet access into a makeshift card reader. This setup is common among service businesses taking phone orders, collecting deposits before a job starts, or closing a sale with a client who's more comfortable on a call than filling out a web form.
Manually entered payments fall into the card-not-present category, which carries higher fraud risk than a chip or tap transaction since there's no physical card to verify. Processors typically charge higher fees for these transactions to offset that added risk, so it's worth factoring into your pricing if phone orders make up a regular part of your business. Collecting the billing address and CVV (card verification value) code at the time of entry helps reduce chargeback risk by giving the processor more data points to confirm the cardholder's identity.
If phone and manual entry payments are a regular occurrence, it's worth comparing this approach against other collection methods in our guide on the efficient ways to receive payments from clients.
Invoice clients and collect payments in one place
Card payments typically come with a fee, and understanding where that fee comes from helps you budget accurately and compare providers on equal footing. Interchange fees sit at the base of the structure: they're set by the card networks (Visa, Mastercard, and others) and vary depending on card type, with rewards and business cards typically costing more to process than standard debit cards. On top of that, your processor adds its own markup, which is where pricing models start to differ from one provider to the next.
Beyond per-transaction costs, many providers charge monthly fees, statement fees, or equipment rental fees for card readers and terminals. These add up quietly, so it's worth asking for a full breakdown rather than judging a provider on the transaction rate alone.
Most processors use one of three pricing structures, and each comes with tradeoffs worth asking about upfront:
Invoicing software with built-in payment collection, like Bonsai invoicing, can help simplify fee tracking by keeping payment records tied directly to the invoice they came from.
Credit card transactions generally fall into one of two categories, and knowing which one applies to a given sale explains a lot about your fees and your fraud exposure. Card-present transactions happen when the physical card is used at the point of sale, typically by inserting, tapping, or swiping it through a reader or terminal. Card-not-present transactions cover the rest: online payments, phone orders, and manually keyed entries where the card itself doesn't touch your equipment.
The fee differences between the two come down to risk. A card-present transaction gives the processor more confidence that the person paying is the actual cardholder, since the chip or magnetic stripe verifies the card itself. A card-not-present transaction relies on the number, expiration date, and security code alone, which is easier to use fraudulently, so processors typically charge more to offset that risk.
Fraud liability shifts with the transaction type as well. In many card-present disputes, the added verification from the chip can work in the merchant's favor, while card-not-present transactions more often leave the business responsible for a chargeback if the purchase turns out to be fraudulent.
| Factor | Card-present | Card-not-present |
|---|---|---|
| How it happens | Chip insert, tap, or swipe at a terminal | Online, phone, or manually keyed entry |
| Relative fraud risk | Lower | Higher |
| Typical processing fees | Lower | Higher |
| Common use case | Storefronts, markets, in-person services | E-commerce, phone orders, virtual terminals |
The right payment processor depends less on chasing the lowest advertised rate and more on how well the fee structure matches your sales volume and transaction mix. A flat rate that looks appealing for a $50 sale can quietly eat into margins on a $5,000 project invoice, so it's worth running your typical transaction sizes through a few pricing models before committing. Transparent, predictable pricing, where you can actually explain your monthly bill without calling support, tends to serve small businesses better over time than a headline rate.
How well a processor connects to the rest of your workflow matters just as much as the fee itself. A processor that syncs with your invoicing, CRM, or accounting software can help reduce the manual re-entry that eats into a Friday afternoon, especially once you're tracking dozens of client payments a month.
Contract terms deserve a close read too. Some processors lock you into multi-year agreements with early termination fees, while others operate month to month with no penalty for switching. Finally, consider which payment methods each provider supports. A business that only accepts cards today may want ACH (Automated Clearing House) transfers or digital wallets tomorrow, and confirming that flexibility upfront saves a painful migration later.
Once you've settled on how you want to take card payments, the next challenge is keeping those payments organized alongside the other details you track for a client. Bonsai invoicing lets you accept credit cards, ACH bank transfers, and PayPal directly on an invoice, so a client can pay however they prefer without you juggling a separate processor login. A freelance web developer billing a $3,200 project milestone can send a branded invoice with a pay button built in, and the payment status updates automatically once the client covers the balance.
Recurring invoices and auto-pay are useful if you bill retainer clients on a set schedule. A marketing consultant charging a $900 monthly retainer can set the invoice to auto-generate and auto-pay against a saved card, and automated payment reminders can help manage follow-up for one-off invoices that go past due, cutting down on the awkward "just checking in" email.
Because most invoices and payments tie back to a client record in Bonsai CRM, you get a running history of who's paid, who's overdue, and what was discussed along the way. Zoom meeting transcripts can sync to that same client record, so if you hopped on a call to confirm a $400 deposit before starting a job, the notes from that conversation sit right next to the invoice itself. For a small studio managing a handful of active clients, that combination means less time spent piecing together payment status from separate tools and more time spent on the actual work.
Yes. Most small businesses skip the traditional merchant account application entirely by using a payment processor that bundles the merchant account function with the software and equipment needed to run transactions. Sign-up for these processors is usually online, requires basic business and banking details, and can have you accepting cards within a short setup window.
This approach works for freelancers, service businesses, and retailers alike, since the processor handles the underlying banking relationship on your behalf. The tradeoff is usually a slightly higher per-transaction fee compared to a dedicated merchant account, which tends to make more sense once a business processes a high volume of sales each month.
Either structure can accept credit card payments, since the ability to take cards depends on your payment processor setup rather than your business entity type. What changes between an LLC and a sole proprietorship is how liability and taxes are handled, not whether a processor will approve you for card payments.
Many freelancers start as sole proprietors and accept cards under their own name before forming an LLC as their business grows. If you're unsure which structure fits your situation, an accountant or business attorney can walk through the liability and tax tradeoffs in more detail, since those factors matter more for entity choice than payment processing does.
Freelancers and individuals can accept credit card payments by signing up for a payment processor that supports sole proprietors, then sending a payment link or an online invoice for clients to pay. No separate business entity or merchant account is required to get started, since most processors approve individuals under their own legal name or a registered DBA.
A freelance writer, for example, can send a client a payment link for a $500 project fee without ever opening a traditional merchant account. As work picks up, some freelancers add invoicing software with a built-in pay button so clients see an itemized breakdown alongside the payment request.
Accepting credit card payments itself doesn't require a business license, since payment processors typically only ask for identifying and banking information during signup. That said, your city, county, or state may require a general business license to legally operate, regardless of which payment methods you use, so it's worth checking local requirements separately from your payment setup.
Requirements vary widely by location and industry, so a freelance consultant working from home may face different rules than a retail storefront. Checking with your local government office is the most reliable way to confirm what applies to your specific situation.
Bonsai invoicing lets you accept credit cards, ACH bank transfers, and PayPal directly on an invoice, so clients can pay however they prefer without you managing a separate processor login. Invoices can include line-itemized taxes and discounts, and payment status updates automatically once a client covers the balance.
Bonsai also supports recurring invoices with auto-pay for retainer clients, along with automated payment reminders for one-off invoices that go past due. Because payments tie back to a client's record in Bonsai CRM, freelancers and small agencies get a running view of who's paid, who's overdue, and what was discussed along the way.
Taking credit card payments comes down to matching the method (online, in person, or over the phone) to how your customers actually want to pay, then choosing a processor whose fees and features fit your transaction mix. Once that setup is in place, tools like Bonsai invoicing can help keep card payments, client records, and follow-ups organized alongside your client records rather than scattered across separate logins. Whichever processor you land on, the goal is the same: make it as easy as possible for a customer to pay you when they're ready to make a payment.
