Splits / Onchain payments
Simplifying how teams move, review, and approve money.
I redesigned the Send flow for Splits so onchain teams could specify what a recipient should receive without first choosing between a transfer and a swap.
Splits' programmable accounts could move assets, swap tokens, and collect approvals, but the interface treated them as separate operations. Paying someone could require choosing Send or Swap before entering the recipient and amount.
I designed a single Send flow around what the recipient should receive. If the account held a different token, the flow offered funding options and handled the swap on the way, while showing token choice and transaction cost before submission.
I also made transaction review easier to follow: who created and signed a payment, when it was submitted, and whether it succeeded. This established reusable patterns for transaction details and states.
