Accenture · Tech Consulting · Medium · 25-35 min

Canadian Bank Launching Consumer-Driven Banking

Canadian Bank Launching Consumer-Driven Banking is a medium Accenture tech consulting case interview that runs 25-35 min. Canada's consumer-driven banking framework is moving from policy to a live regime: customers will be able to share deposit and payment data with accredited third parties. A strong answer works through 5 phases: Separate provider obligations (let customers share their data out) from the commercial choice to be a recipient; Size the scrape problem; Choose participation: build a consent and API layer on the industry standard vs waiting for a vendor wrapper; Sequence read-access for deposits first; payments initiation and 'we pull competitors' data' only after consent works; Set the operating model.

Last updated 2026-09-05

The brief

Canada's consumer-driven banking framework is moving from policy to a live regime: customers will be able to share deposit and payment data with accredited third parties. A Big Six bank has 11M digital users and a patchwork of screen-scraping fintechs already pulling data with customer passwords. The retail CEO wants to be a day-one data provider and is tempted to also become an accredited recipient so the bank's app can pull balances from competitors. Screen scraping must die. You have 15 months and a delivery team that has never run a consent platform. Advise on scope, build vs scheme participation, and what goes live first.

How to approach it

  1. Separate provider obligations (let customers share their data out) from the commercial choice to be a recipient
  2. Size the scrape problem — fraud, password risk, broken journeys — as the reason to move, not only the regulation
  3. Choose participation: build a consent and API layer on the industry standard vs waiting for a vendor wrapper
  4. Sequence read-access for deposits first; payments initiation and 'we pull competitors' data' only after consent works
  5. Set the operating model — consent revocation, accredited-party monitoring, customer support — before the marketing launch

What a strong answer does

  • Treats day-one provider compliance as mandatory and recipient strategy as a separate business case
  • Kills screen scraping on a dated plan rather than running it in parallel forever
  • Designs consent, revocation, and liability with the same care as the API
  • Puts a narrow product live (balances and transactions) instead of a super-app
  • Staffs support and dispute handling, not only engineering

Red flags interviewers score down

  • Bundles 'become a fintech aggregator' into the compliance program with no economics
  • Leaves screen scraping in place with no end date
  • Ships write/payment initiation in the first release
  • No design for a customer who revokes consent on a Friday night

Cases are written in each firm's style, written and reviewed by working consultants; they are not the firms' own published cases.

More Accenture cases