International Wires for Business
Web & App Design
2025-2026
Lead Designer

Project info
International Wires for Business
Role
Lead DesignerTeam
1 content designer, 1 rotating bench product designerClient
U.S. BankDate
2025–2026
I owned the end-to-end experience strategy, journey architecture, detailed interaction design, and cross-functional alignment with engineering and the foreign exchange team.
Bringing end-to-end international transfers into the core experience
Adding International Wires for business customers was a major leadership initiative, and one I championed a full redesign around. Rather than forking domestic and international wires into two separate paths, as originally proposed, I pushed for a single standard journey that let customers choose their direction within the same experience — giving business users the ability to complete end-to-end transfer payments without leaving the product. That decision meant designing one coherent system instead of two disconnected ones — a tradeoff in short-term complexity for long-term consistency.
A gap that was costing the business, not just the user
International wires had no functionality within customer login at all — business customers had to go to a bank branch to send one, or sign up for a more expensive, outdated product that the business planned to sunset. That gap wasn't just an inconvenience; it was a missed revenue opportunity. Other internal teams couldn't leverage a white-label version of international wires either, which left them looking outside the bank for vendor solutions instead. Solving it wasn't just about giving customers a missing feature — it was about closing a revenue and platform gap the whole bank was exposed to.
Building without a map, and without a PM
Two things made this project harder to de-risk: release timeline and lack of available competitive research. The competitive research that was available didn't give us a full picture — most of it was aimed at consumers under Regulation E, and our user segment for this release didn't fall under the same regulatory requirements (ex. foreign exchange rate display differs). On top of that, the product manager was absent for a stretch of the project, so I worked directly with the engineering lead to keep decisions moving and finalize the work.
Original definition of success for MVP vs. my own
The original goal for the MVP was to provide an easy to access digital way to send wire transfers without needing support from a banker and design within the existing API constraints. When I joined the team, however, I found the existing constraints for API design were far too tight and that is when I began to explore redefining what success looked like for MVP. I wanted us to look at success for the project a little differently.
Help first-time wire customers complete the journey with confidence.
Support regulatory requirements across applicable markets.
Keep API and front-end complexity viable for MVP and future releases.
Create a reusable foundation for white-label teams.
Designing the shared journey
I inherited an MVP design path that was designed for constraints that design should push back on and after evaluating, wouldn't work given how they were building our APIs to make the calls. I regularly met with the Engineering Lead and proposed alternative experience paths that solved both the user experience and the front-end development complexity with how we'd be calling back-end APIs to make it work within our constraints. Once I shared a proposed flow, we refined that and established a viable MVP release date.
Rather than branching domestic wires and international wires as separate flows with separate payee lists, I made the case for a unified flow around the journey rather than the task. A user wants to wire money to this person and if they happen to be in another country, that will make it an international wire. We don't have to lock them in one way or another early on. That would be designing for backend constraints rather than the user experience.

Helping users find the right code, not just enter one
That intent-led approach became especially important when customers needed to provide international banking details. Sending an international wire depends on knowing the correct SWIFT/BIC code for the receiving bank — and that requirement isn't standardized; formats and conventions vary by country. Expecting a business customer to already have that code, or go look it up elsewhere, would have undercut the whole point of bringing wires into the product. I designed a search experience that let users look up the right code by bank name, country, and city instead of requiring them to already know it. Once a code was entered or selected, the system validated it immediately and surfaced what it actually represented — which bank, and which location — so users could confirm they were sending money to the right place before submitting. I reviewed the pattern with engineering and compliance to confirm that search results, validation states, and bank-location details matched the capabilities and requirements of the underlying service.
What changed because of my work
The MVP shifted from two separate experiences to one reusable journey.
The team gained a viable release plan after an unworkable initial direction.
The design reduced duplicated payee management and created a foundation for future wire capabilities.
A slower rollout that paid off
During the phased rollout, enrollment in the lower-fee business plan increased 2.5× compared with the prior period—an early signal of demand for self-service international wires.
What we deliberately did not build into MVP
We chose to hold off on a few important features for the MVP release because of timeline and resource constraints that were fast follows being released by the following quarter (Q1 2026). The most important being foreign exchange currency. The reason for that was primarily that the API was not ready and we didn't want to wait to release for that reason so we made the decision to release international wires in USD only in order to see how it was working with a handful of customers before full public release.
A later follow up that is being released in Q4 2026 is my favorite functional and experience improvements that I designed:
Saving international recipients in payee management
Saving any new recipient within the submit wire flow itself
These are important for users in that they will save them time and seamlessly integrate the saving functionality in the experience they are used to working in without having to constantly re-add a recipients information. We have the functionality for domestic wire recipients but adding international account eligibility into their payee profiles will be a huge win for the user as well as saving them within the flow as they enter it. Previously the experience required them to go somewhere entirely different to save the recipient rather than where they send the wire due to some architecture issues with our APIs but we thankfully have resolved that.
What this project reinforced about how I design
The work created a reusable foundation for additional international-payment capabilities, rather than solving a single launch moment. This project was a reminder that the best design decision isn't always the one that ships fastest — it's the one that holds up as a system. Pushing back on the original fork-in-the-road approach meant more upfront complexity, but it kept the experience coherent for the customer and easier to build on later.
It also reinforced how much of design leadership happens outside the file. With a regulatory segment that limited how much I could lean on competitive benchmarking, and a PM gap partway through, the work depended on staying close to engineering and making judgment calls with incomplete inputs — not waiting for a fully de-risked process to appear.