Canadian ISVs: own your payments without shipping them across the border
Canadian software companies build for Canadian merchants, then hand payments to a provider that treats Canada as a footnote. Interac, CAD settlement and Quebec's rules are where that choice starts costing you. --- Most Canadian software companies never sat down and made a payments decision. They set out to ship a product, and payments got solved by whoever had the cleanest docs on a Tuesday aftern

Most Canadian software companies never sat down and made a payments decision. They set out to ship a product, and payments got solved by whoever had the cleanest docs on a Tuesday afternoon. Usually that's an American provider, and for a couple of years it holds up fine.
Then the gaps show up. They tend to arrive in the same order.
Interac comes first
Canadian platforms ask me about debit before they ask about revenue share.
That sounds basic until you look at what Interac actually is. There's Interac Debit at the point of sale, the chip and tap transaction that dominates in-person payments here. There's Interac Debit online through participating platforms. And there's tokenized Interac Debit sitting in Apple Pay and Google Pay. Three products, three enablement paths, three different timelines. A provider can say "yes, we support Interac" and mean any one of them.
Ask which one, and ask what it takes to turn it on.
The commercial stakes are bigger than the technical ones. Canadian debit and credit carry different economics, and merchants with heavy in-person volume watch that mix more closely than almost anything else on your rate card. A platform that can only offer credit leaves its merchants two options: absorb worse economics, or keep a second terminal on the counter. That second terminal means a second relationship, a second statement, and a slice of their revenue your software can't see or report on. You lose the data before you lose the merchant. Usually you lose both.
CAD settlement, and everything after it
Settling in Canadian dollars sounds like table stakes right up until you read the contract. Some providers settle in USD and let the merchant absorb the conversion. Your merchant will find that fee eventually, and they'll blame you for it, correctly.
Then there's what happens when one of your good Canadian merchants starts selling into the US or further out. We process across 40+ markets and settle in CAD, USD, EUR, AUD and GBP. Get that same level of specificity in writing from whoever you're evaluating, and ask how cross-border settlement and FX actually appear in a merchant's reporting. Vague answers here turn into support tickets you inherit.
Some rules are Canadian, and some are Quebec's
The Retail Payment Activities Act put payment service providers under Bank of Canada oversight, with registration and operational risk requirements attached. If you're a platform moving money for merchants, find out where your partner sits under that regime and what obligations, if any, land back on your side.
Quebec adds a layer. Loi 96 carries French-language service obligations, Loi 25 covers privacy, consent and breach notification. If you have Quebec merchants, bilingual onboarding and support sit inside your compliance obligations, not beside them.
I want to be careful on data residency, because the marketing copy in this corner gets loose fast. Canadian ownership does not mean every byte of merchant data stays in Canada, and any provider implying otherwise is stretching. Our own rails include Adyen and a Fiserv facilitator, so we don't make that claim. The narrower questions are the useful ones. Where is cardholder data processed? Which entity is accountable? What does the contract say about breach notification? And can you get a straight answer inside a week? A partner who handles those plainly beats one with a flag in the footer.
What an ownership change actually changes
Canadian payments ownership has moved a lot lately. Francisco Partners agreed to acquire Moneris from BMO and RBC this August, with long-term referral agreements in place and a close expected in their FY2027. Nuvei went to Advent. Bambora went to Shift4.
None of that is a reason to switch on its own. But ownership shapes decisions that reach you eventually. Who the roadmap gets built for. How often pricing gets revisited. Whether support stays where it is. How fast a new market request moves through. All of that runs on somebody's mandate, and mandates change when owners do.
If Canadian ownership matters to your shortlist, PayFacto is the other Canadian-owned option worth having on it. We're in Montreal. That earns a seat at the table and nothing more.
What actually decides it
Lead with the P&L. Attach rate, revenue share, who controls merchant pricing, how much support burden lands on your team, what happens when a dispute comes in. A Canadian-rooted partner who wins on those is a genuine advantage. One who doesn't won't be rescued by proximity.
Four questions I'd bring to any Canadian shortlist. Which Interac products, on what timeline? What currency do we settle in, and what happens when a merchant crosses a border? Where does our merchants' data go, and who's accountable for it? And who picks up the phone in French on a Saturday?
Those four separate a field faster than any deck will.
---
The Payments Health Score on valpay.com takes about two minutes and gives you something concrete to bring into the next provider call. Free, and a decent gut check even if you're staying put. If you're working through this right now, send me a note. Happy to compare notes.
Want to go deeper on this topic?
Talk to our team about embedded payments for your platform.