Deborah Foley Portfolio Deborah Foley Portfolio

Developer Center

A design-leadership case study

Merchant Services Developer Center

The product was the Merchant Services Developer Center. It began as a redesign of the aging, decade-old portal many merchants used to connect to their payments and reports — with the aspiration to rebuild it on APIs already in the air. I came to it as Head of UX, Merchant Services, then carried it as the design SME through the reorg that made me Tribe Lead — owning it the whole way. Within a year I was assigned the organization’s API platform project: the multi-storefront, one-application API store. That left Merchant Services at a fork — keep extending the ten-year-old site, or build a new storefront that integrated with the API store I’d built. I set that strategy and that direction; the final integration was theirs to decide. It’s where the firm’s developer-platform craft began.

What it became

A modern, self-service developer portal.

Discoverable APIs, interactive docs, and self-service onboarding — rebuilt from a legacy stack into the experience that set the pattern for the firm’s developer ecosystem.

Public — Developer Center landing
Public — service page
Public — support
Public — docs and guides
Public — API documentation

Outcome

Replacing PDFs with a CMS-driven docs platform cut friction for third-party developers, and taking the APIs and docs public turned partner onboarding into self-service discovery — no longer locked behind a sign-in and business-development hand-offs.

This case walks the work in the order it happened — discovery, concepts, the build and its docs — and where it led next. The strategic and refinement detail is available on request.

At a glance

Role

Owned it as design SME across the reorg — from Head of UX, Merchant Services to Tribe Lead, API Portals — managing the cross-functional team: a design lead, UX designers, research, and a content strategist / hybrid technical writer

Scope

The Merchant Services developer portal (older tech stack) — discovery, portal UX, docs, and certification; web and mobile

Where it led

The origin of the firm’s dev-portal work — the one-API-store strategy (JPM · Chase · MS), the API Portal, and Connected Banking

Skills

Discovery & research · Information architecture · Content strategy · Design systems · Dev handoff · Platform modernization

On confidentiality. This page shows my process and leadership. Any data shown is illustrative, and internal artifacts are recreated clean. Full detail on request.


Before · the problem

A payments platform developers couldn’t easily build on.

The developer experience for Chase’s payment and merchant-services products ran on an aging stack. Getting started meant working through a list of PDF documents and a static catalog — products were listed, but there was no way to discover them, search, read docs in context, or start building.

For a platform meant to attract third-party developers, the experience itself was the barrier.

Legacy developer portal
The legacy portal. The old developer experience — the PDFs and static catalog lived here, with no self-service path to build.

Discover · due diligence

Learn the developer — and the services — cold.

Before designing anything, I ran deep due diligence: on the developers who’d use the portal, and on the payment services themselves. This is where the discovery method I later taught began.

Competitive analysis of developer portals
Competitive analysis. How the best developer portals handled discovery and docs.
Developer personas
Developer personas. Who builds on payment services, and what they need to start.
Developer journey
The journey. From first landing to a working integration, step by step.
Digitized service blueprint
Service blueprint. The payment services mapped end to end — learned cold.
Content and IA model — entities via the CMS
IA & content model. The entities and structure the portal's CMS would publish from.
Sitemap
Sitemap. How discovery, docs, and onboarding fit together.

Content strategy → DX philosophy

What research said makes a good developer experience.

The research kept returning the same truths: developers expect to solve problems themselves, and self-service is the norm — they search, scan the docs, and want to start building without jumping through hoops. Finding and accessing the documentation was the priority.

Research finding — the self-service API model is the expected norm
Self-service is the expected norm. Developers search, scan, and start building on their own — the portal had to meet that.
Finding — accessing documentation was a priority
Docs access was the priority. Finding and reading the documentation mattered most of all.
Stage 1: API adoption decision making — the five questions developers ask
The API adoption decision. Research mapped the five questions developers ask before adopting an API — security first, then trust, cost, features, and documentation — each grounded in their own words.

Workshops & ideation

Turning research into direction, with the team.

I facilitated ideation workshops with the team: empathy mapping, a design studio — sketch, share, critique, vote — and journey mapping with “how might we” framing to decide what to solve first.

Workshop agenda — journey mapping and ideation
The agenda. How I structured the journey-mapping and ideation session.
Grouping and voting on how-might-we questions
Vote on the HMWs. Grouping "how might we" questions to decide what to solve first.
Empathy mapping with the team
Empathy mapping. Grounding the team in the developer's real context and frustrations.
Design studio — sketching the onboarding experience
Design studio. Sketch, share, critique, vote — the team drawing the onboarding together.

Concepts → flows

From sketch to high fidelity.

The onboarding, project creation, and core flows, built up in fidelity as the direction firmed — low-fi sketches, into wireframes, into high-fidelity screens.

MVP user flow
MVP user flow. The path we committed to shipping first.
Wireframe — create project
Wire · create project. Starting a new integration.
Wireframe — project landing
Wire · project landing. The developer's home for a project.
Low-fi sketches
Low-fi sketches. The starting point — fast, rough, exploratory.
High-fidelity developer center pages
High-fidelity pages. The same flows, resolved into finished screens.

The finals

The modern Developer Center, shipped.

The self-service portal that replaced the legacy stack — a marketing-grade landing, discoverable APIs and docs, and self-service support.

The public experience, as a visiting developer first met it — landing, service pages, support, and the API documentation.

Public — Developer Center marketing landing
Public — service page
Public — support
Public — contact support
Public — docs and guides
Public — API documentation
Mobile — creating your first application
Mobile · onboarding. Creating your first application from the phone.
Mobile — overview dashboard
Mobile · dashboard. The project overview, responsive to the phone.

The strategy deep dive — password protected

The refinement, certification, and build detail.

The user-testing and refinement iterations, the full certification application flow, and the dev-handoff specs and design system that scaled it — the deeper, sensitive work is available on request. A blurred glimpse of what’s inside:

Dev-handoff specs — gated teaser🔒 Gated
Dev-handoff specs. The specs and design system that let the build scale.
Certification flow — gated teaser🔒 Gated
Certification flow. The full application a developer completes to certify on Chase payments.

Inside: user-testing & refinement · the certification application · dev-handoff specs · the design system.

Open the strategy deep dive →


Modernization & what it became

The foundation the ecosystem grew from.

The Dev Center was later modernized off its legacy stack as the APIs matured — a snapshot here; the full modernization story lives in Connected Banking. See Connected Banking →

Dev Center — concept proposal
The concept proposal. The modern self-service direction I proposed for the Developer Center.
Dev Center — the final live modernization
The final, live. The modernized Developer Center as it shipped — the full story lives in Connected Banking.

The one-API-store strategy

The Dev Center work set the case for unifying JPM, Chase, and Merchant Services into a single API store — which became the API Portal.

Connected Banking

The consented-API platform and the firm-wide developer ecosystem grew from this foundation.

The craft, taught

The discovery method here became the playbook I later taught — see How I run design.


Next case study

Next →

Branding Developer Experiences

Developers are customers too — a branded, cohesive Chase developer portal and payment APIs, held to a consumer-grade bar.

Related cases

click outside · Esc to close · ← → to page