The authentication callback completes while the transaction context disappears.
Fast wallet access protects conversion, while preserved transaction state must not expose signing authority.
Who you’d be doing this for
“I watched the wallet connect, then the trade screen reset and our ops channel lit up.”
Elise Crawford · Blockchain Application Developer
Owns the brokerage’s embedded-wallet transaction flow and investigates onboarding drop-off.
What is at stake
Users complete wallet authentication but lose the trade they intended to submit. You have to weigh a faster return path against keeping transaction context outside browser-visible state.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- transaction continuity vs. authorization boundaries
- fast customer recovery vs. reusable core behavior
- browser routing convenience vs. protected transaction context
Why Stripe
Privy’s embedded wallet flow must let brokerage customers carry users from authentication to secure transaction execution.
Written with these in mind
Not your kind of problem? 88 more at Stripe, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.