Square
Square is payment processing software that handles cards on file and payment links, so nobody has to type or write down a customer's card number by hand.
Square is payment processing software: the system that takes a customer’s card, whether tapped in person or entered online, and moves the money without the business ever having to see or store the raw card number itself. Most small businesses already run some part of their payments through it, often without thinking of it as infrastructure at all, just as “the thing that takes the card.”
Where it becomes a real fix rather than a background tool is when it replaces a habit that puts customers at risk. I have seen offices where the actual practice was writing a customer’s card number into a calendar event or a sticky note, because the booking system and the payment system were never wired together. That is not a minor untidiness. It is a liability with the business owner’s name on it if that information ever leaks.
Square already solves this properly through payment links and cards on file, a way to charge a customer later without anyone typing or storing the number in plain text anywhere. The fix, in most cases, is not new software. It is using the tool already in place the way it was designed to be used.
Why it matters to you
A card number sitting in a calendar event or a note is not encrypted, not access-controlled, and often visible to anyone who can open that calendar. If it leaks, whether through a hack, a shared device, or a simple mistake, it is the business’s name attached to the breach, not Square’s.
Beyond the risk, it is also just fragile. A calendar event gets deleted, and the payment detail attached to it goes with it. A card on file inside Square, connected to the actual booking, does not disappear when a calendar entry does.
How I use it
Where a client already runs Square, I connect it directly into the booking and lead flow, so a card goes on file through Square at the point of booking rather than getting typed anywhere else. Payment links replace the manual card entry entirely for jobs that are quoted and paid remotely.
The customer history already sitting in Square, in one case I worked on, several thousand customer records and years of transaction history, moves forward into the new system rather than getting abandoned. Nothing is thrown away. It gets connected properly for the first time.
What it looks like in practice
Before: a card number typed into a calendar note next to the booking, readable by anyone with access to that calendar, gone the moment the event is deleted.
After: the card sits on file inside Square, tied to the booking through a proper payment link, with the existing customer history intact and carried forward rather than lost in the switch.
Questions I get about this
- We already use Square. What is there to fix?
- Usually nothing about Square itself. The problem I find is card numbers being typed into calendar events or sticky notes alongside it, because the booking process and the payment process were never actually connected. Square already has a safe way to hold a card on file, it just wasn't being used for that step.
- Is it safe to keep a customer's card on file?
- Handled through Square's own system, yes, that is what it is built for. What is not safe is a card number typed into a calendar event or a note in plain text, which is what I find replacing it in most offices I look at.
- What happens to our existing Square history if we change how the site works?
- It moves with you. Existing customer records and payment history stay in Square and carry forward into whatever booking or lead system the new site connects to, so the business does not start over.
Want this set up properly for your business?
This is the kind of thing I build every week. Grab a time and we will talk through what fits.