Case study 001, fintech
Send and receive with phone or QR.
At Scotiabank I designed the Plin flows in the mobile app, where people send soles for free with a phone number or a QR, and the Metropolitano card top-up, which I then tested with six customers.
Screens
Metropolitano card top-up, end to end
The confirm screen shows who receives, at which bank, how much, and that it's free, before any money moves.
- Role
- Product design and usability research, Scotiabank. Team: the Scotiabank channels and product teams.
- Problem
- When you send money to a phone number, the biggest fear is sending it to the wrong person. The design also has to feel like a Scotiabank feature and like the same Plin people already know, without teaching anyone a new product.
- Decision
- A destination is a phone number, a contact, or a QR, never an interbank account code (CCI) or an account number. The confirm screen is where people decide to trust the transfer. The Metropolitano card top-up reused the app's existing pay-a-service pattern and explains the wait for activation at the station before anyone pays.
- Result
- Plin is live in the Scotiabank app, including interoperability with Yape and other wallets, and the Metropolitano card top-up I designed shipped as an MVP.
Context
What Plin has to be
Plin lets people in Peru send and receive soles for free and instantly across banks, with a phone number or a QR. It lives inside each bank's app, so in the Scotiabank app it has to feel like a Scotiabank feature and like the same Plin people know from friends at other banks. I designed the flows for linking a number, sending, receiving, showing your QR and scanning to pay, and worked with the channels team so they matched what the app could ship.
Decision
Phone first, account details never
A destination is a number, a contact or a QR, never an interbank account code (CCI). The hard part is the edge cases: numbers that aren't linked, people with accounts at several banks, payments routed to Yape and other networks, and limits that have to be clear before someone commits. I designed each one as a full state in the flow.
Decision
Trust is the confirmation screen
The confirm step has to settle the fear of paying the wrong person. It shows who receives, at which bank, how much, and that the transfer is free, with a hard stop before the debit. QR pay and QR charge share the layout, so paying a shop works like paying a friend.
Build
Metropolitano card top-up, designed end to end
The top-up explains the activation wait, asks for the card number, offers preset amounts, confirms the paying account, and ends on a receipt you can share. It had a launch date, so I reused the app's pay-a-service pattern, and it ships as Recargar transporte in the app. Nothing new to learn or to build, at the cost of a plain MVP.
Decision
Half of this flow happens off the phone
The money leaves the account at once, but the balance reaches the card only when you tap it at a station. So the onboarding, the form and the receipt say this before anyone pays. Without it, a customer taps, sees nothing, and thinks the bank took the money.
Context
Tested
Six Plin customers who ride the Metropolitano, four tasks: find the entry point, top up a card, understand a pending activation, and find help. Three of the four went fine. People found the entry point and understood that the top-up finishes at the station.
Context
Found
People also looked for the feature among their other services and inside their account. The validation module has no settled name, so they described a person in a blue vest instead. Everyone expected the app to remember their card. The biggest problem: you must activate the previous top-up before making a new one, which people read as paying for the wait twice.
Decision
Recommended
Allow a new top-up without activating the previous one. Pick one name for the validation module and use it in the app and at the station. Save the card so the second top-up is shorter than the first. Cut the onboarding to the top-up itself, and add more than one entry point.
Result
Result
Plin is live in the Scotiabank app, including interoperability with Yape and other wallets, and the Metropolitano card top-up I designed shipped as an MVP.
Next case
Build 4 Latam