Mobile app authenticated onboarding flow

Designed a mobile-first, end-to-end offer flow built around transparency and clear expectations, with an online banking version created alongside it. Sharper visuals at every touchpoint keep clients engaged while staying true to the core integrity of the brand.
Role
Senior Product & Content Designer
company
RBC Royal Bank of Canada
duration
8 months
setting
Product, Engineering, Business, Legal
Results at a glance
~180K
cards acquired through this flow in its first quarter
84%
of clients who entered the flow completed it
6 min
or less for most clients to complete it
context & stakes

A pre-approved offer that still needed a credit check

RBC clients see pre-approved credit card offers in the mobile app. The offer asked them to “Apply”, so clients expected a long application process, and many didn’t continue. Every client who left was a targeted card the bank didn’t acquire. The credit check had to stay, so the flow had to show it was a quick confirmation, not a full application.

I led product and content design on this new, mobile-first flow over 8 months, with an online banking version built alongside. RBC’s design system covers spacing, colour and type, so the screens and components are my own.
The start of the new card offer flow in the RBC mobile app
The start of the new flow in the mobile app.
business & user impact

Most banking happens on mobile, so offers have to work there

Most banking traffic happens through mobile channels, which makes targeted offers an important part of both product acquisition and client servicing. The flow had to include a credit check without adding friction or undermining trust.
Acquisition
Targeted offers in the app are a direct way to bring existing clients into a credit product.
Trust
A “pre-approved” offer that surprises clients later can change how they feel about the bank.
Client confidence
Clients want to understand the offer, and what’s expected of them, before they commit.
Three screens: the offer, its benefits and the confirmation
The offer, its benefits, and the confirmation once the card is on its way.
Primary persona
RBC client, no credit products

The due diligent banker

Has banked with RBC for at least 60 days, with a chequing or savings account but no credit products yet. Manages their money with intention, and when a new product comes along, wants to understand it fully and feel confident it's the right fit before committing.

Character traits
  • Does their research before committing to a financial product.
  • Values transparency, and expects to be told the full picture up front.
  • Asks friends and family for advice, and takes their recommendations seriously.
  • Wants to get the most out of their money.
  • Thinks long term: looks at what a product is worth over the years, not just today.
How they decide
  • Compares options side by side before choosing.
  • Reads the fine print, like fees, terms and conditions, before signing up.
  • Weighs costs, like fees, against the value they'll get over time.
  • Looks for how a product can make their day-to-day life easier.
  • Wants to know what's expected of them before they start.
What frustrates them
Surprises along the way
Hidden or unclear terms
Not enough detail to compare
Feeling pressured to decide
problem & bet

Where expectations broke down

I ran competitive research, reviewed related flows in the bank, gathered knowledge from card teams and met with advisors to hear what clients discuss in branch. From that, we built mid-fidelity mockups, a research plan and a hypothesis to test with clients.
Distrust
Clients read “pre-approved” as meaning no further approval steps would be needed.
Discomfort
Giving an exact income figure created uncertainty, and some clients felt they had to give the “right” answer.
Hesitation
Clients wanted enough information to compare options before committing to a card.
Confusion
Upsell and downsell outcomes left clients unsure of their approval status and what would happen next.

Mapping the experience

I ran an experience mapping session with the team, capturing what clients think, feel and do at each phase of the offer, along with technical needs and business objectives. We then synthesized it into one view of where clients moved forward and where they stalled.
Happy path experience map
The happy path experience map: touch points, thinking, feeling, doing, technical needs and business objectives for each phase.
Experience mapping workshop
The mapping workshop with the team.
Experience map synthesis
The synthesis: where clients moved forward, paused or dropped off at each phase.
the bet
Clarity, not just fewer steps, would reduce friction. If clients knew what was coming and every choice was explicit, they would move through the flow with confidence.
constraints

Designing within real-world constraints

I brought product, business, legal and engineering in early to surface the dependencies shaping the experience, so we could design with them rather than around them later.
Offer logic
Card offers were tied to unique offer codes, limiting which products could be shown in a targeted offer.
Downsell requirement
Clients shown a downsell card had to explicitly decline it. Leaving without doing so could mean receiving the card.
Delivery address
Technical limits meant delivery details had to be settled before the final adjudication step.
Product comparison
Eligibility and offer-code logic limited comparing the targeted card with cards outside the eligible suite.
End-to-end card offer flow
End-to-end card offer flow, mapping eligibility, decision points and alternate outcomes.
three key decisions

Clear expectations, an offer that’s easy to judge and explicit choices

Research showed that clarity mattered more than cutting steps. Each decision made the next step easier to understand. Every screen below was designed from RBC’s spacing, colour and type foundations, not assembled from a component library.
decision 01

Tell clients what’s coming before the credit check

I replaced “Apply” language with a story about confirming client information, changed the primary CTA to “Get started” and added a “What to expect” screen that surfaces the credit check before clients continue. Near the end, the reviewed mailing address became the default delivery address, removing one more decision.
A clearer start to the offer
A clearer start to the offer. Expectations are set before clients move deeper into the flow.
Simplified delivery details
Simpler delivery details. Reusing reviewed information removes an unnecessary decision.
decision 02

Make the offer easy to judge

Clients were most interested in benefits they could use right away, so I surfaced those first and moved the annual fee beside the card name. For income, I explored ranges instead of an exact figure and validated them with risk partners, to ease the pressure of giving the “right” answer while respecting approval requirements.
Benefits built around client relevance
Benefits built around client relevance. The information clients valued most comes first.
A less stressful income interaction
A less stressful income interaction. Less uncertainty, while respecting approval requirements.
decision 03

Confirm approval first, then offer an explicit choice

Upsell and downsell paths were the hardest moments in testing. My first fix, intercept screens, added confusion. I simplified it: acknowledge the approval first, then give a clear choice between cards, with an explicit accept or decline and a confirmation when declining.
Upsell
Upsell. Approval is confirmed before the premium card is offered, so clients can compare both and choose.
Downsell
Downsell. The alternate offer is clear, with an explicit way to accept or decline it.

The words behind the flow

before
“Apply”
after
“Get started”, framed as confirming your information
“Apply” felt like a betrayal on a pre-approved offer. Confirming information felt like a formality.
before
“Approved for an upgrade”
after
“You're approved”, with “Continue with current card” as the primary CTA
Confirms the approval first, so the premium card reads as an option rather than a surprise.
before
A “declined” screen
after
One review screen for declined and pending clients, followed by an email
Nobody on a pre-approved offer is met with a harsh “declined” in the moment.
before
Leaving the screen, and receiving the downsell card anyway
after
“Decline card offer” as the primary CTA, with a confirmation alert
Makes the required action explicit, without pressuring clients to accept.
outcomes

A clearer flow with strong completion

The final experience balanced complex requirements with clearer client decisions.
~180K
cards acquired through this flow in its first quarter after launch
84%
of clients who entered the flow completed it
6 min
or less for most clients to complete the happy path
93%
of clients who reached a downsell chose Accept or Decline

Explore happy path flow

Go through the entire Happy Path flow from the Account Summary to the final success screen in the mobile app.
Explore prototype
what I’d do next

In a regulated flow, clarity beats speed

Clients expected the credit check. The friction came from not being told about it up front, so telling people what’s coming removed more friction than cutting a step.
Compare earlier
Bring card comparison into the first offer screen, if offer-code logic allows.
More time to decide
Give upsell clients more time, since a new choice late in the flow still added cognitive load.
Drop-off by screen
Measure drop-off for each screen, not just overall completion.