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

Bakeries collect deposits and payments on WhatsApp by sending a payment link, never by taking card numbers in the chat. A custom cake is bought months before it is made and paid in two parts, so payment is the step most likely to go wrong. An unpaid deposit holds a date for nobody, a balance that arrives on collection day means a conversation at the counter, and a cancellation with no stated terms becomes an argument.

What we'll cover

• Never take card details in chat
• What a deposit is 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 in the same thread
• Keeping payment automations working
• Limits worth knowing about
• What to build first
• Frequently asked questions

Key takeaways

• Send a payment link and never accept card numbers or card photographs in a chat thread.
• A deposit holds the date and covers what you commit, so say that in the request message.
• Request the balance about a week before collection, not on collection day.
• Write short cancellation terms once, and send them with the quote.
• Match every payment to an order reference, so you always know what is outstanding.

Never take card details in chat

Never take card details in chat. Customers offer them with good intentions, and four reasons still rule it out.

It is a data problem. The numbers end up in a thread, in a backup and on a phone.

It is not how card payments are meant to be taken. Check your payment provider's terms, which commonly restrict it.

It trains customers badly. This reason 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. A polite "I will send you a secure link instead" reassures the customer and does not feel awkward. The same rule applies to photographs of a card, which people send often.

What a deposit is for

A deposit holds the date, which is the thing you sell when you accept an order months ahead. It also covers what you commit, such as ingredients ordered or a date declined for somebody else. It is not a fee.

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

Take a proportion of the total. The proportion is yours to decide.

Say what the deposit is for. Customers understand holding a date far better than an abstract deposit.

Apply it to the balance. Customers accept that more easily than an additional charge.

Payment links, and making them work

A payment link works when the customer can pay in one tap and recognise the charge later. Follow these rules:

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

Make payment one tap from the message. A customer at work will not open a banking app to type a reference.

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

Include the order reference. The reference makes reconciliation possible when four people pay on one day.

State a deadline plainly, and say the date is held until then.

Bank transfer is still fine for customers who prefer it. Give a clear reference, and expect to chase more.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations (CodeWords pricing page, 2026), and you make each connection once and reuse it. To build a payment automation:

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 you record orders, and your WhatsApp Business Platform account.
4. Describe the exceptions: an unpaid deposit at the deadline, a cancellation, a partial payment, and an order changed after payment.
5. Run it against a month of past orders and check what each customer would have received.

You describe the outcome, and Cody builds it, connects it and deploys it. The Free plan costs $0, Pro costs $39 per month and Business costs $100 per month (CodeWords pricing page, 2026). Details are on the pricing page.

The balance, and when to ask

Ask for the balance about a week before collection. That is enough time to chase and late enough that the order is certain. Asking on collection day is the most common arrangement and the worst.

Send the request with the collection details. That gives the message a purpose beyond asking for money.

Say what happens if the balance is not paid. State the consequence in advance so the customer does not discover it.

Chase once, then phone. Do not send a third message.

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

Terms that prevent arguments

Write terms once, in a few lines instead of a page, and cover five points:

• What the deposit holds and whether it is refundable.
• When the balance is due.
• What happens on cancellation, at different distances from the date. A month out and two days out are not the same.
• What happens if you have to cancel. Customers notice when this is missing, and stating it builds trust.
• Where the terms live. Send them with the quote, not buried on a website, and keep a record that you sent them.

When somebody cancels

When a customer cancels, your terms should set what you keep, based on how close the cancellation is to the date.

Ingredients bought and work done are the fair basis for what you retain.

Consumer rules apply in most markets and limit what you may keep, particularly for distance sales. Check your own position instead of 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 customers remember kind handling.

Offer to move the date instead of cancelling. That keeps the order and the goodwill.

Record what was agreed. A cancellation resolved verbally resurfaces later.

Keeping the money side tidy

A tidy payment record needs six habits:

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

Know what is outstanding by order without scrolling a chat.

Record deposits as received against the order, not in your memory.

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

Separate business and personal payments. This matters more as the business grows.

Use a simple list at small volume, provided it exists somewhere other than the conversation.

Pricing conversations in the same thread

Customers discuss price in the same WhatsApp thread as payment, in fragments, while you are doing something else. Handle price questions in six ways.

Answer the price question directly when asked. Deflecting to a call loses people on this channel.

Give a from-figure instead of refusing. "Prices start at" filters honestly and keeps the people who are comfortable with your range.

Quote the whole price once. A price assembled across several messages invites negotiation at each step.

Do not discount under pressure in a live exchange. You will be held to a price you reduced in the moment.

Say what changes the price, so an added tier or a sugar flower is an expected adjustment and not a dispute.

Write the agreed figure back with what it includes. This habit prevents every other argument in this trade.

Keeping payment automations working

Payment automations stay reliable when they verify payment instead of assuming it.

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

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

Check the order state before chasing. The customer may have paid an hour ago.

Hand partial payments to a person. They happen and need judgement.

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

Limits worth knowing about

Payment automation has five limits.

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

Consumer rules limit what you may retain on cancellation, and they differ by market and by how you made the sale.

Bank transfers need more chasing than card payments.

You cannot control refund timing once you issue a refund, so set the expectation honestly.

This article is not legal or tax advice. Your accountant and local consumer rules govern.

What to build first

Build the deposit link with a stated deadline, and hold the date until then. It turns chasing into an expectation the customer manages, it removes the date held for nobody, and it is one message instead of a system.

Two habits make the difference. First, never accept card details in a chat, and say why when customers offer, because the real cost is training them to send details to whoever asks next. Second, request the balance a week before collection, not on the day. 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. Card details in a chat put the numbers in a thread, a backup and a phone, and they may break your payment provider's terms. They also train customers to send card details to anyone who asks in a friendly tone, as an impersonator will.

What is a deposit for?

A deposit holds the date and covers what you commit, such as ingredients ordered or 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?

A payment link should work in one tap from the message. It should include the order reference so you can reconcile four payments on one day, a description recognisable on a statement, and a stated deadline with the date held until then.

When should I request the balance?

Request the balance about a week before collection. Do not request it on the day, which is the most common arrangement and leaves you resolving payment at the counter with a cake in your hands.

What should the terms cover?

Terms should 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.

What can I keep if somebody cancels?

Ingredients bought and work done are the fair basis for what you keep. Consumer rules limit it in most markets, particularly for distance sales. Check your own position instead of copying another baker's terms.

What about genuine circumstances such as illness?

A bereavement or illness is not the case your terms were written for. Being generous in these cases is remembered, and offering to move the date instead of cancelling usually keeps both the order and the relationship.

Do I need more than a list?

At small volume, a simple list of what is outstanding by order is enough. The list must live somewhere other than the chat thread, and the records must be adequate for your tax return.

Should I put prices in the conversation?

Yes. Answer directly when asked, because 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 piece by piece?

Quote the whole price once instead of 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 becomes the price you are held to next time.

Related reading

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