Working in a global insights business like RFI, I try as much as possible to ensure that I am across the analysis and trends that we are creating and reporting to clients around the globe. To this end, I was listening to my colleague George Kawar in Canada present insights on the Canadian payments landscape recently. After the presentation, there are two things that stuck with me – firstly, George is a great presenter, and secondly, that the impact of the changes to merchant surcharging at the back end of 2022 would be very interesting to see play out.
It was certainly interesting timing, with so much focus on cost of living and CPI in Canada having increased dramatically last year. In October 2022, when this announcement came out, CPI stood at 6.9%. The prospect therefore of an additional costs being added to consumers’ bills came with a sense of foreboding.

As a quick recap, in the decade leading up to 2021, several class action lawsuits were brought by merchants in the Canadian provinces of Alberta, British Columbia, Ontario, Québec and Saskatchewan against the card networks and the banks. The merchants claimed that the credit card processing fees they were charged (the Merchant Discount Fees) were a hardship for their businesses.
As a result of the lawsuit, as of October 2022, Canadian merchants (outside of Québec) are able to charge customers a surcharge of up to 2.4% on credit and debit card payments. Merchants must give 30 days’ notice to the card networks and their acquirers before doing this, which means that November 2022 was effectively the first month in which this surcharging could occur.
With this news emerging, RFI got on the front foot and asked Canadian consumers what they would do in the face of this merchant surcharging. Now, you don’t have to be a psychic to know that consumers will not love the idea of a potential increase in costs, and so when 37% of credit cardholders tell us they would reduce their credit card usage significantly and 38% will reduce their usage somewhat if confronted with a surcharge of up to 2.4%, it did not surprise us.

The question is, do we expect that we’re going to see 75% of credit cardholders reducing their spending? It’s always hard to know what is going to happen when changes to regulation like this occur; the difference between sensible conjecture and hyperbole is not often clear. And that is why its handy to be able to draw parallels from other markets that have been through a similar process.
For these purposes, I’m going to look at the Australian market. Both Canada and Australia are increasingly reliant on electron payments from credit and debit cards and are moving away from cash and cheques – albeit cheques are much more significant in Canada than in Australia.

As the chart shows, the volume of purchase transactions (CNP as well as in-person) has grown over the last few years, and while there is a skew towards debit in Australia vs Canada, the total number of credit and debit purchase transactions in 2021 was remarkably similar – 11.91bn in Canada vs 11.97bn in Australia. Data in 2022 is not available for 2022 in Canada (kudos to the RBA for its wealth of payments statistics).
I show these comparisons in order to qualify my assumptions that the changes in usage of Canadian consumers could be expected to be in line with the changes in usage of Australian consumers when similar surcharging was introduced in 2003.
And how significant was that change? The answer is that the number of purchase transactions made by Australian consumers on both credit and debit have grown significantly since 2003. The RBA data shows that in 2003 and beyond there was no short or long term decline in the number of transactions beyond expected seasonality.

As merchants will be allowed to surcharge only to recover costs, the other question that is worth asking is whether we will see a shift from credit card to debit card spend. I.e., if a merchant will charge more to surcharge a credit transaction than a debit transaction, will Canadians opt for the latter? According to the RBA’s survey of consumers in 2013, typical surcharging levels in Australia at the time were 1.5% for Mastercard and Visa credit, whereas debit cards were less likely to be surcharged, consistent with the difference in cost to most merchants.
This one is therefore harder to answer with Australian data. There are several factors that complicate it, including:
All of these have certainly contributed to what we see in the payments data today, which is that the number of debit card transactions has grown significantly faster than credit card transactions as the chart below shows.

So the question now is, why didn’t consumers change their behaviour wholesale in the face of card surcharging? Why didn’t they ditch their credit cards altogether? I would say that it comes down to three major factors:
Get in touch for more insights.
Subscribe to The Banknote, our monthly newsletter delivering expert perspectives and exclusive analysis, powered by 200,000 consumer and 60,000 business interviews each year to help you stay ahead in a fast-changing financial world.
| Cookie | Duration | Description |
|---|---|---|
| __cf_bm | 1 hour | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
| __hssc | 1 hour | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
| __hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
| AWSALBCORS | 7 days | Amazon Web Services set this cookie for load balancing. |
| AWSALBTG | 7 days | Amazon Web Services set this cookie for load balancing. |
| AWSALBTGCORS | 7 days | Amazon Web Services set this cookie for load balancing. |
| cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
| elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
| rc::a | never | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
| rc::c | session | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| wpEmojiSettingsSupports | session | WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. |
| XSRF-TOKEN | 2 hours | This cookie enhances visitor browsing security by preventing cross-site request forgery. |
| Cookie | Duration | Description |
|---|---|---|
| AWSALB | 7 days | AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target. |
| AWSALBTG | 7 days | Amazon Web Services set this cookie for load balancing. |
| AWSALBTGCORS | 7 days | Amazon Web Services set this cookie for load balancing. |
| Cookie | Duration | Description |
|---|---|---|
| __hstc | 6 months | Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
| _ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
| _ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
| hubspotutk | 6 months | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
| wmc | 1 year 1 month 4 days | Workable sets this cookie to assign a unique visitor ID for statistical purposes. |
| Cookie | Duration | Description |
|---|---|---|
| _cfuvid | session | Description is currently not available. |