The short version: Manual e-Transfer works fine for occasional large payments. If you're collecting more than 20โ€“30 e-Transfers per month, you need the Request Money API โ€” otherwise reconciliation alone will eat your afternoon. VoPay, Apaylo, and Flinks are the Canadian fintechs that can wire this up for you.

Business e-Transfer vs Consumer e-Transfer

The e-Transfer most Canadians know โ€” the one where you send $200 to your roommate โ€” is consumer e-Transfer. Limits top out around $3,000 per transaction at most banks, and the whole thing runs through your personal banking app.

Business e-Transfer is a separate product offered through business banking accounts. Transaction limits go up to $25,000 per transfer, and most banks offer higher daily limits than consumer accounts. You're also eligible for the Request Money feature, which is where things get interesting for merchants.

Per-Bank Business Limits (2026)

If you need to move more than $25,000 at once, you're splitting transfers or using wire transfer or EFT instead.

The Request Money Feature: What It Actually Does

Request Money is the business-facing side of e-Transfer. Instead of waiting for a client to initiate a payment to your email address, you initiate a payment request. The flow looks like this:

This is a fundamentally better user experience than the old "send an e-Transfer to [email protected]" approach. The customer doesn't have to look up your email, guess the security answer format, or enter anything manually. They tap approve and it's done.

Request Money is built into most major bank business portals, but the manual bank version is still capped at manual workflows. If you want this integrated into your invoicing software or website, you need an API provider.

API Integration: VoPay, Apaylo, and Flinks

These three Canadian fintechs are the main options for businesses that want to programmatically send e-Transfer requests, receive payments, and auto-reconcile โ€” without logging into a bank portal.

VoPay

VoPay is a Vancouver-based fintech that provides an e-Transfer API alongside EFT/ACH, pre-authorized debit, and real-time payments. Their e-Transfer API lets you trigger Request Money flows programmatically: your system generates an invoice, fires an API call, and the customer gets a payment request immediately.

VoPay handles the bank connectivity and compliance layer. You build the integration against their REST API and they manage the Interac relationship. Pricing is custom and volume-based โ€” expect $0.25โ€“$0.75 per transaction depending on volume and feature set. They're a good fit for platforms, property managers, and lenders that need to scale e-Transfer collection without hiring a treasury team.

Apaylo

Apaylo (formerly part of the Concentra ecosystem) focuses on e-Transfer and EFT for Canadian fintechs and platforms. Their API covers both send and receive flows with webhook-based reconciliation. Apaylo is particularly popular with rent collection platforms, lending companies, and billers who want real-time confirmation of payment receipt.

One advantage: Apaylo's API has solid documentation and sandbox support, which makes integration testing straightforward. Like VoPay, pricing is volume-based and negotiated โ€” typically in the $0.15โ€“$0.50/transaction range.

Flinks

Flinks is best known as a financial data aggregator (think: connecting bank accounts to verify income), but they also offer payment initiation. Their strength is the bank connection layer โ€” if you need to both verify a customer's bank account and collect payments via e-Transfer or EFT, Flinks can do both with one integration. It's particularly useful for lending, insurance, and high-value service businesses where bank account verification is part of onboarding anyway.

Flinks is now part of the National Bank ecosystem, which gives them deep connectivity with Canadian financial institutions. Their payment product is newer than VoPay or Apaylo, but it's matured significantly in the last two years.

Fees: e-Transfer vs Card Processing

This is the actual reason Canadian businesses care about e-Transfer. The fee difference is significant:

On a $1,000 B2B invoice, card processing costs $25โ€“$29. An e-Transfer API call costs $0.50 at worst. The math is obvious for high-value transactions โ€” especially recurring ones.

For small businesses sending monthly invoices over $500, e-Transfer collection via Request Money or API is almost always cheaper than Stripe or Square. The friction trade-off is real (cards are more convenient for customers), but for B2B clients who pay by invoice anyway, it's a non-issue.

When e-Transfer Makes Sense vs Cards

e-Transfer is the better choice when:

Cards win when:

The Manual e-Transfer Trap

Plenty of small businesses still collect via manual e-Transfer โ€” they post their email address on invoices, wait for transfers, and manually cross-reference bank notifications against outstanding invoices. This works until it doesn't.

The problem isn't the payment itself โ€” it's reconciliation. When you're matching 5 transfers a month to 5 invoices, it's fine. At 50 transfers a month across multiple clients who all pay "Smith, John" or give no reference, you're spending 3โ€“4 hours a month doing manual matching. That's before you account for the ones who misspell your email, don't include a security question you forgot to set, or send to an old address.

Request Money API eliminates this. Every payment request has a unique ID. When it's paid, your system gets a webhook. The invoice closes automatically. This is what scaling e-Transfer collection actually looks like โ€” not a shared email inbox and a spreadsheet.

RTR: What's Changing in Late 2026

Payments Canada's Real-Time Rail (RTR) is expected to launch in late 2026. RTR is a new payment infrastructure that settles in seconds, 24/7/365, unlike the current Interac e-Transfer system which settles in near-real-time during business hours but has overnight gaps.

What this means for businesses: e-Transfer for Business will evolve to run over RTR infrastructure. The $25,000 limit isn't going away, but transaction speed and certainty should improve. More importantly, RTR opens the door for new payment flows โ€” including merchant-initiated real-time debits โ€” that don't exist today.

For now, the practical impact is limited. If you're building on VoPay or Apaylo today, those integrations will migrate to RTR as the infrastructure providers update their rails. You won't need to rewrite your integration from scratch.

For context on other 2026 payment changes affecting Canadian merchants, see the 2026 Canadian payment regulatory changes guide.

How to Get Started

If you're processing under 20 e-Transfers per month, your existing business banking portal's Request Money feature is probably enough. Log into RBC, TD, Scotiabank, or BMO business banking, find the e-Transfer section, and enable Request Money if it's not already active.

If you're processing at volume, or want e-Transfer integrated into your invoicing or platform workflow:

All three have sales teams that'll demo their product and provide volume-based quotes. None have self-serve pricing pages โ€” you'll need to call or email.

Also worth reading: EFT, PAD, and wire transfers for Canadian B2B payments โ€” e-Transfer isn't the only option for moving money between businesses, and sometimes pre-authorized debit is the better fit for recurring billing.