e-Transfer for a home bakery

Last updated 19 August 2026 · Practical guidance, not banking, legal or tax advice. Limits, fees and account rules differ by bank and by account type, so confirm yours with your own bank rather than with this page.

Why this is the right rail in Canada

Because it is what your customer already uses. She does not need an account, an app or a card on file. She opens her banking app, types your email address, and it is done. For a home bakery taking orders out of Instagram, that is the whole argument.

The other argument is that nobody takes a cut. Card processing runs somewhere near 3% once you count the fixed piece per transaction, and on a $400 wedding cake that is real money for doing nothing you noticed. e-Transfer is free on most personal chequing accounts, though plenty of business accounts charge per transfer, which is worth checking before you assume.

Cards still earn their place. Some customers want the protection, some are not in Canada, and a corporate order will often want a card and a receipt. The point is that e-Transfer should be the default and the card should be the exception, not the other way round.

Turn on autodeposit. It is the single most useful thing here.

Without autodeposit, every transfer arrives with a security question the sender picked and you have to answer. That sounds harmless and it is the part that actually goes wrong: the answer gets sent in the same message thread as the transfer, or it is "cake" for the fortieth time, or you are icing something and cannot get to your phone and the transfer sits there expiring.

With autodeposit registered against your email address, money lands in the account by itself. No question, no clicking, nothing to answer at nine at night.

Two things to know before you switch it on. The sender sees the name registered on the account, so if that is your legal name rather than your bakery name, say so in your instructions or people will think they have the wrong address. And an autodeposit is harder to unwind than a pending one, which matters in a way that is mostly good and occasionally not. See below.

If you are not using autodeposit, at least do this

• Never put the answer in the same place as the transfer. If it is in the same DM thread, the security question is decoration.
• Do not reuse one answer forever. "cake", lowercase, for every customer you have ever had, is a password you have given to a hundred people.
• Say the answer format in advance. Half the failed attempts are capital letters and spaces, not fraud.

The reference is what makes this a system

Here is the actual daily problem. It is Saturday, three transfers have landed, two are for $50, and the names on them are a husband, a maiden name and someone's teenager. Which order is which?

The fix is boring and it works: give every order a short code and ask the customer to put it in the message field. Four characters is plenty. Avoid the characters people misread, so no zero against O and no one against I, because somebody is going to type this on a phone in a parking lot.

Then your bank notification, your order and your calendar all agree, and matching a payment is reading rather than remembering.

Three things e-Transfer will not do for you

• It will not tell your system anything. There is no webhook and no feed for an individual. A transfer lands, an email arrives, and a person has to notice. Any tool claiming your orders update themselves from e-Transfer is either parsing your bank email or overpromising, so ask which.
• It will not ignore limits. There are caps per transfer, per day and per week, and they vary by bank, by account and sometimes by how long you have banked there. Nobody warns you until a customer tries. Before you quote a large wedding cake, check your own limits and be ready to say "send it in two".
• It will not reverse for you. Once deposited, an e-Transfer is effectively final. There is no chargeback button.

That last one is exactly why it suits deposits

A card payment can be pulled back months later. An e-Transfer, once it has landed, has landed. For a deposit that is holding a Saturday in your calendar, that finality is the entire point: it is what makes the deposit mean something rather than being a gesture.

It cuts the other way with a customer who has never met you, and it is worth being generous about that. Somebody sending $200 to a stranger's email address is taking a real risk and knows it. A photo of your setup, a clear written policy and a receipt sent the moment it arrives all cost you nothing and do most of the reassuring.

More on how to word the policy itself in deposit policies that stick.

Two housekeeping things people put off

It is income, and it is visible. Money arriving by e-Transfer is not invisible just because it did not go through a card terminal. Keep the date, the amount, the customer and the reference for every one. If you are ever asked, the difference between a bad afternoon and a bad month is whether that list already exists. What you owe and when you have to register for GST or HST is a question for an accountant, not for us.

Ask your bank about business use. Many banks treat a personal chequing account differently once it is clearly running a business, and the rules differ between them. It is a five-minute question now and an awkward one later, so ask before you are taking twenty orders a week.