PayPal: Becoming the Default at Checkout

What was unclear

PayPal showed up differently at every checkout.

Each merchant integration carried its own patterns. Across vaulting, express, and standard flows, the experience changed from one surface to the next: app switch versus web, first time versus returning. That inconsistency worked against the one-click program, where the whole point is that paying takes one tap in any merchant's checkout.

What I clarified

One proposal per merchant, on a weekly sprint.

On the Merchant Enablement team I produced a proposal package for each merchant. Each one mapped the current checkout against a clearer target state across the four entry contexts, Wallet, Express, Standard first time, and Standard return, and the major variants: app switch versus web, Pay Later versus Pay in Full, passkey, and vaulting.

Every package was the same stack: a screen audit, the complete checkout flows, a working prototype, a prototype video, and the decks for the merchant conversation.

The constraint

Three design libraries were live at once, and checkout was locked to the oldest.

Versions 4.0, 5.1 and 5.2, and a 6.0 target ran side by side, with Oslo incoming, and checkout stayed on the oldest because engineering could not move. Part of the job was telling product managers which blue-sky work was presentable now and which was years from shipping. Every proposal came out of that constrained library.

A second thread ran alongside the top accounts: a modular checkout flow library for merchants outside the top 100, covering grocery, retail, subscriptions, and restaurants, mostly mobile, from product selection through payment confirmation. Those generic flows are the ones that can be shown.

Who I influenced

The package was what the team took into the room.

PMs and design leads used it in merchant conversations. I worked from PM briefs, with Principal Designer review and peer review inside a senior team. The proposals fed the merchant pitch for brands including Home Depot, Nintendo, Target, Best Buy, TikTok Shop, Chewy, and Microsoft.

The consumer side

The checkout dead end

A customer reaches checkout and finds there is no card that can pay. The card expired, or it was declined, or it was removed, or it was never added in the first place. The order stops there.

I built the Figma board that mapped that dead end back to every earlier moment the customer could have fixed the card. The board traced the touchpoints across roughly a month before checkout, marked which ones send a message today and which ones send nothing, and ended on the checkout experience itself.

The structure came together fast because I used Claude Code to turn a Design Director's diagram into the underlying framework of the board, then designed into it. The screens came from teams across the company, which meant tracking down owners in parts of the organization I had not worked with before. The work was presented to senior leadership, and the board became the team's template for mapping the next flows.

PayPal, 2026. Figma, Claude Code, cross-team research.

What changed

Twenty-plus packages in my first six months, and the tooling to hold the pace.

The product manager on that work credited the team's merchant-specific proposals and demos with moving several top accounts to contract, integration, or launch on new PayPal checkout enhancements. Wayfair selected PayPal to test upstream presentment on product and cart pages for a new guest checkout. I never saw conversion data. It was proposal work.

Holding a weekly cadence at that volume is its own design problem. The tooling was not part of my assignment, and I built it because the handoff into each package was the part that kept breaking. That story is its own case study: Merchant Flow Builder.