Farshad Amiri
← All case studies

Case study 04 · iTOLL · Direct debit

Making direct debit easy to switch on

  • Problem

    Direct debit lets people pay in one tap, but only 1 in 10 who started activation finished it.

  • Approach

    Data showed where people left, and 72 phone calls showed why. So we explained before asking, and framed it as wallet auto-pay.

  • Result

    By the end of the quarter, activation went from 10% to 22% — more than twice as many people finished.

Role
Product Designer, core team
Timeline
3 sprints
Platforms
App and website
Methods
Clarity, data, interviews, A/B tests
Reading
8 min
Visit iTOLL ↗
The redesigned iTOLL website in two browser windows, in Persian: the wallet top-up page with automatic top-up from a bank account, and the direct debit activation page listing three benefits above a bank picker and a Start activation button.

10% → 22%

direct debit activation rate

Before and at the end of the quarter · +12 points

2.2×

more users finishing activation

Relative change

68%

of test activations came from Plan A

Curated, clearer copy · A/B test, 14,000 users

2.5×

wallet auto-pay vs direct debit

127 vs 50 activations, 500 users each

01 · The problem, Context · Empathize

A one-tap payment almost nobody turned on

iTOLL brings car payments into one app: debts, tolls and insurance. Direct debit lets it take a payment straight from a bank account, with no bank gateway each time. To turn it on, users sign a contract and add their bank card once, on the bank’s Faraboom platform. Most people who started never finished.

~10%

of users who started activation finished it

Before the redesign

~5%

of debt-list payers activated and paid

Users paying a debt or toll from the debt list

2 drop-off points

where people left

The amount and limit page, and the Faraboom bank platform

Before: activating from the debt list

  1. Opens the debt list to pay“Let me pay this toll.”
  2. Sees direct debit as a payment option“Is this another gateway?”Pain point
  3. Sets an amount and withdrawal limit“How much can they take?”Pain point
  4. Is sent to Faraboom“My bank isn’t here.”Pain point
  5. Enters card details and waits for a code“The code never came.”Pain point
  6. Gives up and uses the gateway“I’ll just pay the old way.”Pain point

The flow asked for bank access before people understood what they were agreeing to, then sent them out of the app.

How I found out where, and why, people left

  • 01 · Clarity and data analysis

    Session recordings and funnel data for the debt list and both activation entry points: the menu and the wallet top-up page.

  • 02 · Phone interviews

    72 calls over 10 days with users who dropped that day or had cancelled their contract. 43 calls were completed.

  • 03 · Heuristic evaluation

    The flow reviewed against UX principles and best practices.

What people told us — three themes, by how often they came up

  • 1 · Complexity and doubt

    Worried about giving access to a bank account · didn’t trust the method · afraid the account could be hacked or emptied · thought it might be a scam.

  • 2 · Technical errors

    Form errors while entering details · problems receiving the code · account issues.

  • 3 · Not knowing direct debit

    Saw it as just another gateway · someone else turned it on for them · didn’t see how it differs from wallet top-up.

  • “I couldn’t find my bank.”
  • “I didn’t get the OTP code.”
  • “iTOLL would have access to my account, so I couldn’t trust it.”
  • “I used it to pay my debt, but it went to the bank gateway.”
  • “My friend turned it on for me. I don’t know what it is.”
  • “I didn’t know how to cancel it. I don’t want money taken from my account again.”

Pain → Gain

Pain → Gain
PainGain
Slow payment methodsFast, easy payment
Typing card details every timeSafe payment
Distrust of the activation flowTrust in the direct debit flow
Fear of not being able to cancelAn easy way to cancel

02 · The approach, Define · Ideate

Make it understood before asking for trust

I turned the research into an empathy map and a journey map, reviewed the flow against UX principles, and traced every pattern to how people decide. Then the team generated ideas together, and I benchmarked how other products introduce a stored payment method.

  • HMW 1

    How might we explain direct debit so people understand and trust it, before we ask for bank access?

  • HMW 2

    How might we make activation short and error-free, so that starting it means finishing it?

Where the flow broke UX principles — and the fix for each

Where the flow broke UX principles — and the fix for each
PrincipleIssueFix
Visibility of statusActivation status, date and contract length weren’t shownShow status, activation date and transactions
Error preventionOur VPN breaks the bank step; supported banks only show inside the inputWarn about VPN first; show supported banks up front
Help users recover from errorsDirect debit looked like a gateway in the debt listClear micro-copy; wallet auto-charge instead
Aesthetic and minimalist designOnboarding was a wall of text that nobody readOnboarding with micro-copy and images
Help and documentationUsers didn’t know how much was taken, or whyShow each transaction with its reason
Goal gradientNo sense of how many steps were leftShow the activation steps

Why each pattern happened

Why each pattern happened
ObservedWhat was happeningPrinciple
Distrust of bank accessAn unfamiliar method asked for account access up frontAmbiguity aversion · Loss aversion
Seen as just another gatewayDirect debit sat in the debt list like any payment methodMental models
Dropping at the limit pageAmount and limit were asked before the value was clearCognitive load
Errors on FaraboomNo warning before leaving the app (VPN, supported banks)Error prevention
Not knowing how far alongNo steps or status shownGoal gradient · Visibility of status

Nine ideas from the team

  1. ChosenClearer, easier copy
  2. ChosenOnboarding for first-time activation
  3. ChosenHide direct debit for users who haven’t activated it
  4. ChosenWallet auto-pay instead of direct debit on the toll landing page
  5. ChosenActivate direct debit through wallet auto top-up
  6. LaterA landing page for direct debit activation
  7. ChosenInform users along the way to prevent errors
  8. LaterSettings to edit or cancel the contract
  9. LaterA transaction list in auto-pay settings

Benchmark: Airbnb, Google Play, Tapsi and Bazar

How products we and our users know introduce a stored payment method.

  • Explain in one screen before asking for anything
  • One clear start button
  • Say it can be turned off any time
  • Keep payment methods in one place

03 · What we did, Design

Explain first, then ask

The redesign leads with a familiar idea, wallet auto top-up, and explains direct debit in plain words before asking for any bank details.

Screens shown in Persian, as shipped.

The direct debit activation page on the iTOLL website, in Persian: a short title, three benefits in highlighted rows, a bank picker and a blue button to start activation.

01 · Activation page

Three benefits in plain words — pay in one click, automatic wallet top-up, turn it off any time — then choose your bank.

The iTOLL user account in Persian: a side menu, the wallet balance in toman with top-up and direct debit buttons, and a card inviting the user to switch on automatic wallet top-up.

02 · Account and wallet

Wallet balance, top-up and direct debit, managed from the user account.

The iTOLL wallet top-up page in Persian: a banner for automatic top-up from a bank account, the current balance, a choice between one-time and automatic top-up, preset amounts and a confirm button.

03 · Wallet top-up

Automatic top-up from a bank account, powered by direct debit.

Main changes

  1. Wallet top-up methods made easy to tell apart
  2. Three benefits in plain words: pay in one tap, top up your wallet automatically, turn it off any time
  3. Auto top-up powered by direct debit
  4. Choose your bank first, with supported banks visible
  5. Onboarding pages with short copy and images
  6. One primary action: Confirm and continue
  7. Direct debit copy rewritten for each feature

Every change maps to a principle, and to a problem from research

Every change maps to a principle, and to a problem from research
ChangePrincipleFixes
Hide direct debit in the debt list until it’s activeMental models · Choice overloadSeen as just another gateway
Wallet auto top-up instead of direct debitFraming effectDistrust of bank access
Rewritten, clearer copyAmbiguity aversionNot knowing direct debit
VPN warning before FaraboomError preventionErrors on the bank platform
Onboarding pageAesthetic and minimalist designA wall of text nobody read
Direct debit as a top-up methodRecognition over recallNot seeing how it differs from top-up

Trade-offs we chose on purpose

Trade-offs we chose on purpose
DecisionGained · gave upHow we handled it
Ship 6 of 9 ideasDelivered within time and tech limits · contract settings and the transaction list waitedPlanned as next steps
Lead with wallet auto-pay2.5× more activations on the landing page · direct debit itself is less visibleIt still powers auto top-up behind the scenes
Hide direct debit until it’s activeLess confusion when paying · fewer chances to discover it in the debt listDiscovery moved to the wallet and onboarding
Curated copy (Plan A)More trust, 68% of activations · less detail on screenOnly the key points, under clear headings
VPN warning before FaraboomFewer failed activations · one more message in the flowShown only at the hand-off step

04 · The result, Test

Activation more than doubled

We ran two A/B tests: first what to say, then how to frame the feature.

  • Test 1 · Copy

    Google Optimize · 14,000 users who entered wallet auto top-up with direct debit. Same flow, different copy.

    • Plan A · curated copy68%
    • Plan B · general copy32%
    Share of all activations in the test. Scale 0–100%.
  • Test 2 · Framing

    Toll landing page · 500 users per option. Same capability, framed two ways.

    • Wallet auto-pay127 · 25%
    • Direct debit auto-pay50 · 10%
    Activations out of 500 users per option. Scale 0–100%.

10% → 22%

direct debit activation rate

Before, and at the end of the quarter

68%

of test activations came from Plan A

More than twice Plan B’s share

2.5×

more activations with wallet auto-pay framing

127 vs 50, 500 users each

Why it worked

  • Explain before you ask

    Understanding came before bank access, so the request felt fair. Clear, selected copy removed the unknowns that made people say no. · Ambiguity aversion

  • Familiar framing

    Wallet auto top-up is a known idea, so direct debit stopped looking like a strange new gateway. The same feature drew 2.5× more activations. · Framing effect

  • No surprises

    “Turn it off any time” lowered the felt risk, and the VPN and bank warning before Faraboom prevented errors. · Loss aversion · Error prevention

  • Show the way

    Hiding an option people hadn’t set up made paying simpler, and showing the steps made the end feel close. · Choice overload · Goal gradient

05 · What I learned, Reflection

Trust is a design problem

Three lessons I carry into every project.

  • Trust is a design problem

    People didn’t reject direct debit. They rejected what they didn’t understand. Copy moved the number more than layout.

  • Framing changes behaviour

    The same feature, called wallet auto-pay, was chosen 2.5× more often.

  • Call the people who left

    Talking to users who dropped that same day explained what the data couldn’t.

Next steps

  1. Show status, activation date and transactions in auto-pay settings.
  2. Let users edit or cancel the contract from settings.
  3. Measure retention: are activated users still paying with direct debit after three months?
  4. Track the debt-list funnel on its own, against its 5% baseline.