How to accept online payments without building a full store

Mariela runs a sewing workshop in Durango. She mends dresses, alters suits, and makes custom clothing, and her work almost always starts the same way: the customer sends her a photo over WhatsApp, she replies with a price — “the dress comes to $450, ready by Thursday” — and the customer says yes.

That’s where it gets complicated. Because after the “yes” comes the “so, do I just deposit it?” — and that question kicks off a second job nobody pays her for: sending her account number again, waiting, getting a blurry screenshot at eleven at night, checking the banking app the next day, not finding the deposit, asking without sounding rude. Sometimes she doesn’t get paid until they pick up the garment. Sometimes they never pick it up.

If this sounds like your week, the fix isn’t building an online store. It’s much smaller than that.

Why don’t you need a full store to accept payments?

Accepting online payments means your customer pays from their phone, on your own page, without you having to chase the money down. That’s it. It doesn’t mean a catalog, it doesn’t mean inventory, and it doesn’t mean you sell products.

The confusion comes from the fact that almost everything you see online about this is written for stores: photos of every product, a cart, sizes, colors, shipping. That’s a different kind of business than Mariela’s. She isn’t selling a hundred things — she sells one thing at a time, quoted separately for each customer.

For a business like that, the page you need is a page with one single thing and its “pay” button. The job you agreed on, its price, and that’s it.

What do you need to accept online payments?

You need exactly three things: what you charge for, how much it costs, and where the money lands. If you have those three, you can already get paid; everything else is decoration.

What you charge for. The name of the job or service, written the way you’d say it to the customer: “Formal dress alteration,” not “Service A.” If you have three or four jobs that come up again and again — hemming, waist adjustment, zipper replacement — each one can be its own line item with its own price.
How much it costs. A number in pesos. If your work is usually quoted case by case, publish the ones that do have a fixed price and leave the rest for quoting by message.
Where the money lands. Your account. When you connect card payments, the money drops straight in there; you never handle card data or store anything.

That’s the whole baseline. A single-screen page with those three pieces of information can already take payments.

How much does it cost to accept card payments?

A percentage gets deducted from each charge, and it’s worth saying plainly because nobody does: in Mexico, processing a card typically runs around 3% to 4% of the amount plus a small fixed fee per transaction, depending on the processor and card type. On a $450 job, that’s roughly $15 to $20.

I’m not going to tell you it’s free. I’ll tell you what to weigh it against instead: against the dress that hung there for three weeks because the customer never came back, against the four messages you send asking if the deposit ever went through, and against the job you delivered on the promise that you’d get paid on Friday.

And check the exact number the day you turn it on, not now — fees change, and every processor has its own.

What if your customer prefers a transfer or cash?

You can offer both — you don’t have to pick just one. Your page can offer both options: pay by card right there, or reserve the order to pay in cash or by transfer when they come pick up the garment.

Here’s what you gain even when they don’t pay online: it gets recorded. Instead of a message buried among forty others, you get an order with a name, a phone number, what the job is, how much it costs, and whether it’s already paid or not. That list is half the value on its own — and it’s the part WhatsApp alone will never give you.

A lot of people in Mexico still prefer to pay in person, and forcing them onto a card costs you sales. Offer both.

What you don’t need (even if someone tries to sell it to you)

A catalog. If you sell quoted work, you don’t have a catalog. You have agreements.
Inventory. Nothing to subtract from anything.
A cart. No one is going to buy two dress alterations and a zipper replacement at once.
Photos of everything. Four well-photographed jobs tell a customer more than thirty blurry ones.

Each of those is one more decision to make and one more thing to keep updated. If it’s not solving your money problem, it’s dead weight.

When it’s not the right fit yet

If you always get paid in person, on the spot — a stall, a counter, people who walk up, pay, and leave — accepting payments online isn’t going to move the needle for you. The problem it solves is the gap between “yes, I want it” and “I actually got paid.” If that gap doesn’t exist in your business, spend your energy somewhere else.

Where it really pays off is custom orders, scheduled services, classes, and anything agreed on one day and delivered on another.

Describe it, and it’s already taking payments

Here’s what Mariela would write in Proyecta, word for word:

A page for my sewing workshop in Durango. I want to accept online payments for the alterations that already have a fixed price: hemming $180, waist adjustment $250, zipper replacement $200. Let the customer pay by card, or reserve the order and pay me in cash when they pick it up. Send me an email with their name, phone number, and which job it is. And a WhatsApp button for anything that needs a separate quote.

From that comes a published page, with its own link, already taking payments. No catalog, no store.

An exercise before you decide

Pull up your last five jobs and, next to each one, jot down how many days passed between “yes, I want it” and “I actually got paid.”

If you get zeros, you’re already in good shape. If you get fours, sevens, and a twelve, there’s your answer — and it’s not that you have bad customers, it’s that you handed them an account number instead of a button.

When you’re ready to see it working, describe it at proyecta.dev and publish it.