A customer wants to pay you. They're ready right now, card in hand. But your website doesn't take payments, so you tell them to call during business hours, or mail a check, or Venmo you. Some of them will follow through. A lot of them won't.
I've helped local businesses set up online payments, and the conversation always starts the same way: "I didn't think I needed that" or "I figured it was too complicated." It's simpler than you think, and I want to walk you through what's actually involved.
Why This Matters for Local Businesses
You might think online payments are only for e-commerce stores shipping products across the country. That's not the case anymore. Service businesses, contractors, consultants, and shops right here in Sedalia can all benefit from letting customers pay online.
Think about it from the customer's side. They get your invoice and want to pay it right then, at 9 PM on a Tuesday. If they can click a link and type in their card number, you get paid that night. If they have to remember to call you tomorrow or find their checkbook, there's a real chance it gets pushed off. Then pushed off again.
Faster payments mean better cash flow. It's that straightforward.
The Big Three: Stripe, Square, and PayPal
There are a lot of payment processors out there, but for small businesses, these three cover almost every situation.
Stripe is my go-to for website integrations. It's built for developers, which means I can make it do exactly what your business needs. Custom checkout forms, recurring billing, invoicing, subscription plans. The API is excellent and the documentation is some of the best in the industry. Your customers never leave your website to pay, which looks professional and builds trust.
Square is great if you also need in-person payments. A lot of businesses here use Square terminals already, so adding online payments through the same system makes sense. Everything stays in one dashboard. If you're already swiping cards at a counter with Square, adding website payments through the same account is a natural next step.
PayPal is the one everyone knows. Your customers probably already have accounts. The downside is that PayPal redirects people away from your website to complete the payment, which feels clunky. It also has a reputation for freezing accounts and holding funds, which is frustrating when you're a small operation. I generally recommend it as a secondary option, not the primary one.
What Does It Actually Cost?
Every payment processor takes a cut. The standard rate across the industry is 2.9% plus $0.30 per transaction. Stripe, Square, and PayPal all charge roughly the same.
Here's what that looks like in real numbers:
- On a $100 payment, you pay $3.20 in fees. You keep $96.80.
- On a $500 payment, you pay $14.80 in fees. You keep $485.20.
- On a $1,000 payment, you pay $29.30 in fees. You keep $970.70.
Is that worth it? Compare it to the invoices that sit unpaid for 30, 60, 90 days because paying is inconvenient. Compare it to the checks that get lost in the mail. Compare it to the customers who would have paid you that night but didn't because there was no easy way to do it. For most businesses, the fees pay for themselves many times over.
There are no monthly fees with any of these processors at the basic level. You only pay when a transaction goes through.
What Can Payments Look Like on Your Site?
Online payments aren't one-size-fits-all. Depending on your business, the setup can range from dead simple to fairly sophisticated.
Payment links and invoices. The simplest option. You send a customer a link (via email or text), they click it, enter their card, done. No website changes needed. Stripe and Square both offer this out of the box.
A payment button on your site. A step up. You add a "Pay Now" button to a page on your website, and customers can pay a set amount or enter a custom amount. Good for deposits, flat-rate services, or donations.
Full checkout. If you're selling products or packages, you build a checkout flow right into your site. Shopping cart, item selection, card entry, confirmation. I built something like this for the SPARK ham radio club's Spark-Con event site using WooCommerce, and it handled ticket sales and merchandise without a hitch.
Recurring billing. If you charge monthly (maintenance plans, subscriptions, memberships), the payment system can automatically charge the customer's card on schedule. They sign up once and you get paid every month without chasing anyone.
Security: The Part Everyone Worries About
This is usually the biggest concern I hear. "What if someone's credit card gets stolen through my website?" Valid question. Here's the good news: if you're using Stripe, Square, or PayPal, you never touch the card numbers.
That's by design. When a customer types their card number into a Stripe checkout form on your site, that data goes directly to Stripe's servers. It never passes through your server. You never see it, you never store it, you never have access to it. This is called tokenization, and it's the industry standard.
This also means you don't have to worry about PCI compliance (the set of security standards for handling credit card data). Since the card data never touches your systems, the compliance burden falls on the payment processor, not on you.
What you do need is an SSL certificate, which encrypts the connection between your customer's browser and your website. If your site starts with "https" and shows a padlock icon, you have one. If it doesn't, that needs to be fixed before you even think about payments. Every site I build includes SSL from day one.
Simple Button vs. Real Integration
There's a big difference between dropping a PayPal button on a page and building a real payment system into your website.
A dropped-in button works. But it looks generic, it redirects your customer to a different site, and it doesn't connect to anything else in your business. You still have to manually track who paid what and when.
A proper integration means the payment flow matches your website's design, the customer stays on your site the whole time, you get automatic email confirmations, and you can connect it to your invoicing or record-keeping. It's the difference between duct-taping something together and building it into the foundation.
That's the kind of work I do. Not just "here's a button," but a payment system that actually fits your business and looks like it belongs on your site.
Do You Actually Need This?
Not every business does. If your customers always pay in person at a register, online payments might not change much for you. But if any of these sound familiar, it's worth a conversation:
- You send invoices and wait weeks (or months) to get paid
- Customers ask if they can pay by card and you say no
- You lose potential sales after business hours because there's no way to complete a purchase
- You're manually tracking payments in a spreadsheet or notebook
- You want to offer deposits or payment plans but it's too much hassle to manage manually
If you checked even one of those, online payments would probably make your life easier and your business more money.
Getting Started
The first step isn't buying anything or signing up for a processor. The first step is figuring out what makes sense for your specific situation. A lawn care company and a retail shop and a consultant all need different setups.
If you want to talk through what online payments could look like for your business, reach out. I'll tell you honestly whether it's worth the investment and what it would take to set up.