14

Blog · November 11, 2026 · 7 min read

P2P Payment UX: Resolve the Recipient Before Anyone Types an Amount

Spend ten minutes in the support forums for any peer-to-peer payment app and you will find the same story told a hundred ways. Someone picked a name from a list of similar names, tapped once, and a stranger now has their rent. Support says the payment is final. The thread fills up with people telling the sender they should have checked harder.

We think that answer lets the product off the hook. When the same mistake shows up thousands of times, the flow is producing it. P2P payment UX has one job above every other job: get the money to the person the sender meant. Speed, delight, and social feeds all come after that.

This post is how we approach a send money flow when we audit or rebuild one for a fintech team. It is opinionated on purpose.

The order of the flow is the design

Most send flows open on a big number pad. The amount comes first, the recipient second, and the confirmation is a sheet that slides up for half a second. That order tells the user the amount is the decision and the recipient is a detail.

We flip it. The recipient comes first, and the app resolves that recipient into a verified identity before the amount field even appears. The sender should see who they are paying the whole time they decide how much to pay.

Our ordering for a standard send:

  1. Pick or enter the recipient. Contacts, recent people, a phone number, an email, or a handle.
  2. Resolve and show the verified identity. The legal or account name from the provider's own records, a masked identifier (the last four of the phone number, part of the email), and the profile photo if one exists.
  3. Enter the amount and a note, with the resolved recipient pinned at the top of the screen.
  4. Review on one screen that leads with the person, then the amount, then the funding source, fee, and arrival time.
  5. Send with a button that names the action, such as "Send $1,200 to Dana Ortiz."
  6. Show a receipt with a distinct state for sent, pending, and failed.

Brazil's Pix rail is a good public reference here. After the sender enters an alias like a phone number, the payee's name is shown before the payment can go through, and the sender can confirm or cancel. That small step does more work than any amount of warning copy.

Display names are where the money goes missing

A display name is whatever the account holder typed into a profile field. It can be a nickname, a business name, an emoji, or a copy of somebody else's name. When a search for "Dana" returns six Danas with cartoon avatars, the app has handed the sender a guessing game.

Our rules for the recipient list:

  • Show the verified name next to the display name whenever the two differ, and make the verified name the stronger text.
  • Show a masked identifier on every row, so two people with the same name can be told apart at a glance.
  • Rank people the sender has paid before above strangers, and label the strangers plainly as "Not in your contacts" or "You haven't paid this person before."
  • Never auto select the top search result. A list of near matches is exactly where a one tap mistake happens.
  • Treat a near duplicate of a saved contact as a warning. If "Dana Ortiz" is saved and a new "Dana Ortiiz" appears, say so.

Friction belongs on the first payment to a new person

Teams worry that more confirmation means more drop off. They are right if they add the same friction to every payment. Sending $20 to your sister for the fifth time this month should feel instant.

The risk sits in a narrow band: a first payment to a new recipient, a large amount, or both. That is where we add weight.

  • A first payment to a new person gets its own review step with the verified name in large type and the masked identifier beneath it.
  • Large first payments get a short cooling window or a delay option where the provider's rails and policy allow it. Even a few minutes of "you can still cancel this" catches a lot of panicked mistakes.
  • A typed check for high amounts, such as confirming the last four digits of the recipient's phone number, works better than a second "Are you sure?" dialog that people tap through on reflex.
  • Payments to a business or marketplace seller get a scam note written for that moment, such as "Paying someone you met online? Payments to people you don't know usually can't be recovered."

Everyone else keeps the fast path. That is how you protect people without taxing your best users.

The send button should say exactly what happens

"Continue," "Next," and "Pay" all describe navigation and say nothing about commitment. The final button is the last moment the sender can still change their mind, so it should read like a sentence they would be comfortable signing.

"Send $1,200 to Dana Ortiz" reads that way. If the payment is instant and final, the line right above the button says so in plain words: "Sent instantly. You can't cancel after this." If it is scheduled or pending, the button and the line say that instead.

We also keep send and request visually distinct. When the two actions share a screen, a color, and a button shape, people request money from their landlord or send money to someone who asked them for it. Different labels, different colors, and a different review screen for each.

Plan for the payment that went to the wrong place

No flow catches every mistake, so the product needs a real answer for the sender who gets it wrong. "Contact the recipient and ask nicely" leaves the sender with nothing to do inside the app.

What we build into the transaction detail screen:

  • A "Something's wrong with this payment" entry point on every sent payment, visible without digging through help center links.
  • Separate intake paths for "I sent it to the wrong person," "I didn't make this payment," and "The amount is wrong." Each one is a different investigation and should feel like it.
  • A guided request back to the recipient that the app sends on the sender's behalf, with a clear status the sender can watch.
  • A stated timeline for what happens next and when they will hear back, written in days.
  • An honest outcome when recovery isn't possible, with the reason and any next step such as reporting fraud to their bank.

People forgive a hard policy much more readily than they forgive silence.

What we reject

When we review a P2P send flow, these patterns get flagged every time:

  • Amount first, recipient second.
  • Recipient lists that show only display names and avatars.
  • Auto selecting the first search match.
  • The same confirmation for a $5 repeat payment and a $2,000 first payment to a stranger.
  • A final button labeled "Next," "Continue," or a bare "Pay."
  • Finality disclosed only in the terms of service.
  • Send and request sharing one screen and one button style.
  • A success animation before the payment has actually settled.
  • No way to report a misdirected payment from inside the transaction.
  • Scam warnings so generic and so frequent that everyone has learned to ignore them.

Why this matters to the business, too

Misdirected payments are expensive in ways that rarely show up on a growth dashboard. They fill the support queue, they turn into public complaint threads, and they teach a user that the app is risky to use for anything that matters. A sender who loses $1,200 once tends to move their larger payments somewhere else, and those are the payments that keep a P2P product alive.

The fixes are mostly ordering, labeling, and a handful of well placed checks. They are cheap to build and very hard to see from inside the team, because the people who designed the flow already know who they meant to pay.

How we work on flows like this

We are a senior only studio that works on complex and regulated products like fintech, health, insurance, and AI. We test send flows in working software, with real states for pending, failed, and reversed payments, because a static Figma mockup can't show you what a near duplicate recipient or a delayed first payment feels like in the hand. We use AI to move fast through the build and keep humans on every judgment call about risk, copy, and policy.

If your send flow, payout flow, or any money movement screen is generating support tickets you can't explain, we can find out why.

Book a discovery call or email us at ash@uxsignalstudio.com.

Let’s talk about your next step

Have a question or a project in mind?

Tell us where you are and what you want to figure out. We’ll review your message and reply within two business days.

Contact UX Signal Studio

We’ll use your details to respond to your inquiry. This form does not subscribe you to a mailing list. Privacy policy.

Prefer to talk? Book a discovery call

Get the next essay in your inbox

One practical piece on UX and product design, every week or two. No noise.