Making an international transfer easier to get right

Someone is about to send money abroad. The recipient has already shared their bank details — a name, an account number, a routing number, maybe a SWIFT code. Now all of it has to get into the right fields without a mistake.

This is a placeholder case study. Replace the story with your own work, but keep the rhythm: a real problem, the constraints around it, the decisions you made, and what changed.

The problem

The details were already there. The work was copying them, one field at a time, between two apps.

People did not need a better form. They needed fewer trips through the form. The goal became simple to say and hard to do: let someone paste the whole message once, and let the product do the sorting.

The stakes

A single wrong digit can fail a transfer or send it to the wrong place. The interface has to be forgiving without becoming careless. Every shortcut needs a way to check itself, and a way for the person to correct it.

• The wrong number goes into a field.
• A local transfer number gets used for an international payment.
• A detail is missing, but the form still lets you continue.
• The message contains more than one set of details.

Research

I read support tickets, watched people complete real transfers, and mapped where they left the screen. The pattern was consistent: the failures were not in the form, they were in the handoff between the message and the form.

The idea

What if people could paste the whole message?

The first version recognized a handful of common formats and filled what it could. Everything else stayed manual. That was enough to test the idea without pretending the hard part was solved.

“

It felt like the app had read the message with me instead of making me read it twice.

”

Checking

We put the first version in front of a small group and asked them to send money the way they normally would. The parsing worked. The trust did not. People wanted to know what had been filled in, and they wanted a way to undo it.

So we added a review step: every extracted detail was highlighted, editable, and labelled with where it came from.

The result

The revised flow cut the number of manual entries per transfer and made the failure states obvious. The product still asks people to check. It just does not ask them to start from nothing.

Impact

The placeholder numbers in this case study are here to show the layout. Replace them with your own results, or remove the metrics entirely if you do not have them.

• More transfers completed without a support ticket.
• Fewer recipient-detail corrections after submission.
• Faster median time to a completed transfer.

Takeaways

The best version of this feature was not a smarter input. It was a better conversation between the person and the product: here is what I found, here is what I think it means, here is how you change it.

That pattern shows up in almost every case study on this site.