Bakery deposits and payments over WhatsApp: links, not card numbers

A custom cake is bought months before it is made and paid for in two parts, which makes payment the part of the process most likely to go wrong. A deposit that was never paid holds a date for nobody. A balance that arrives on collection day means a conversation at the counter. A cancellation with no stated terms becomes an argument.

None of that is difficult, and one rule sits above the rest: card details do not belong in a chat thread, ever, for reasons that go beyond the obvious.

What we'll cover

• Never take card details in chat
• What a deposit is actually for
• Payment links, and making them work
• Building it with CodeWords
• The balance, and when to ask
• Terms that prevent arguments
• When somebody cancels
• Keeping the money side tidy
• Pricing conversations, which happen here too
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

Never take card details in chat

It is a data problem, since the numbers are then in a thread, in a backup and on a phone.

It is not how card payments are meant to be taken, and your payment provider's terms almost certainly say so.

It trains customers badly, which is the reason that matters most — a customer used to sending card numbers to a business will send them to somebody impersonating you.

Fraudsters copy this exact pattern, including the friendly tone, and a customer who has done it once has no reason to hesitate.

Say so when asked. Customers offer, meaning well, and a polite "I will send you a secure link instead" is reassuring rather than awkward.

The same applies to photographs of a card, which people send surprisingly often.

What a deposit is actually for

It holds the date, which is the thing you are selling when you accept an order months ahead.

It covers what you commit — ingredients ordered, a date declined for somebody else — rather than being a fee.

It signals commitment, which changes who books as well as who pays.

A proportion of the total is the usual approach, and what proportion is yours to decide.

Say what it is for, since customers understand holding a date far better than they understand an abstract deposit.

Apply it to the balance, which is easier to accept than an additional charge.

Payment links, and making them work

Send a link, not an account number, which is both safer and easier to pay.

One tap from the message, since a customer at work will not open a banking app to type a reference.

Say what it is for in the message and on the payment page, so it is recognisable in a statement later.

Include the order reference, which is what makes reconciliation possible when four people pay on one day.

Give it a deadline, stated plainly — the date is held until then.

Bank transfer is still fine for customers who prefer it, with a clear reference, and it needs more chasing.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: when the deposit link goes, when the balance is requested, and what happens if neither is paid.
3. Authorize the connections to your payment provider, wherever orders are recorded, and your WhatsApp Business Platform account.
4. Describe the exceptions: an unpaid deposit at the deadline, a cancellation, a partial payment, an order changed after paying.
5. Run it against a month of past orders and check what each customer would have received.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

The balance, and when to ask

Not on collection day, which is the most common arrangement and the worst.

A week ahead is usually right — enough time to chase, late enough that the order is certain.

Send it with the collection details, which gives the message a purpose beyond asking for money.

Say what happens if it is not paid, which should be stated rather than discovered.

Chase once, and then by phone rather than by a third message.

Never hand over an unpaid cake and resolve it afterwards, which sounds obvious and is what happens under pressure at a counter.

Terms that prevent arguments

Write them once, plainly, in a few lines rather than a page.

What the deposit holds and whether it is refundable.

When the balance is due.

What happens on cancellation, at different distances from the date, since a month out and two days out are not the same.

What happens if you have to cancel, which customers notice is missing and which builds trust when present.

Send them with the quote, not buried in a website, and keep a record that they were sent.

When somebody cancels

Close to the date is different from months ahead, and your terms should say how.

Ingredients bought and work done are the fair basis for what is retained.

Consumer rules apply in most markets and constrain what you may keep, particularly for distance sales — check your own position rather than copying another baker's terms.

Be generous with genuine circumstances. A bereavement or an illness is not the case your terms were written for, and handling it kindly is remembered.

Offer to move the date rather than cancel, which keeps the order and the goodwill.

Record what was agreed, since a cancellation resolved verbally resurfaces.

Keeping the money side tidy

Match every payment to an order, which is why the reference matters.

Know what is outstanding, by order, without scrolling a chat.

Record deposits as received against the order rather than in your memory.

Keep the records for your tax return, since this is income and a chat thread is not a book.

Separate business and personal payments, which matters more as the business grows.

A simple list is enough at small volume, provided it exists somewhere other than the conversation.

Pricing conversations, which happen here too

The payment mechanics are the easy half. The harder one is that price gets discussed in the same thread, in fragments, usually while you are doing something else.

Answer the price question directly when it is asked, since deflecting it to a call loses people on this channel.

Give a from-figure rather than refusing, because "prices start at" filters honestly and keeps the people who are comfortable.

Quote the whole thing once, not piecemeal, since a price assembled across several messages invites negotiation at each step.

Do not discount under pressure in a live exchange. A price reduced in the moment is one you will be held to next time.

Say what changes it, so an added tier or a sugar flower is an expected adjustment rather than a dispute.

Write the agreed figure back, with what it includes, which is the same habit that prevents every other argument in this trade.

Making it survive

Never confirm an order as paid without checking the payment actually arrived.

Make the payment request idempotent, so nobody receives two links for one deposit.

Check the order state before chasing, since they may have paid an hour ago.

Handle the partial payment, which happens and needs a person.

Report the outcome: deposits requested, paid, outstanding by age, and balances due this week.

Limits worth knowing about

Payment providers charge per transaction, which matters on small deposits.

Consumer rules constrain what may be retained on cancellation, and they differ by market and by how the sale was made.

Bank transfers need chasing more than card payments do.

Refund timing is not yours to control once issued, so set the expectation honestly.

This is not legal or tax advice, and your accountant and local consumer rules govern.

What to build first

The deposit link with a stated deadline and the date held until then. It converts chasing into an expectation the customer manages, it removes the held-for-nobody date, and it is one message rather than a system.

Two habits make the difference. Never accept card details in a chat, and say why when customers offer, because the real cost is training them to do it for whoever asks next. And request the balance a week before collection rather than on the day, since that is the difference between a message you can chase and a conversation at the counter with a cake in your hands.

Frequently asked questions

Can I take card details over WhatsApp?

No. It puts the numbers in a thread, a backup and a phone, it is almost certainly against your payment provider's terms, and worst of all it trains customers to send card details to anybody who asks in a friendly tone — which is exactly what an impersonator will do.

What is a deposit actually for?

Holding the date, and covering what you commit — ingredients ordered, another booking declined. Customers understand "this holds your date" far better than an abstract deposit, and applying it to the balance is easier to accept than an extra charge.

How should payment links work?

One tap from the message, with the order reference included so four payments on one day can be reconciled, a description recognisable on a statement, and a stated deadline with the date held until then.

When should the balance be requested?

About a week before collection. Not on the day, which is the most common arrangement and leaves you resolving it at the counter with a cake in your hands.

What should the terms cover?

What the deposit holds and whether it is refundable, when the balance is due, what happens on cancellation at different distances from the date, and what happens if you have to cancel — which customers notice is missing.

What can I keep if somebody cancels?

Ingredients bought and work done is the fair basis, and consumer rules constrain it in most markets, particularly for distance sales. Check your own position rather than copying another baker's terms.

What about genuine circumstances?

A bereavement or illness is not the case your terms were written for. Being generous there is remembered, and offering to move the date rather than cancel usually keeps both the order and the relationship.

Do I need anything more than a list?

At small volume, a simple list of what is outstanding by order is enough — provided it lives somewhere other than the chat thread, and provided the records are adequate for your tax return.

Should I put prices in the conversation?

Answer directly when asked — deflecting to a call loses people on this channel. A from-figure filters honestly and keeps the customers who are comfortable with your range.

How do I avoid negotiating piecemeal?

Quote the whole thing once rather than assembling a figure across several messages, say what would change it, and write the agreed price back with what it includes. A price discounted under pressure in a live exchange is one you will be held to next time.

Related reading

• Taking custom cake orders over WhatsApp
• Order confirmations and collection reminders
• Where cake enquiries die