B2B SaaS Case Study · OneCause

B2B Payment Onboarding & Merchant Account Workflows

Simplifying merchant account setup and payment configuration inside a fundraising platform.

B2B SaaS Payments UX Merchant Onboarding Workflow Simplification
Merchant Accounts product visual
Hero image — Merchant Accounts product visual img/Merchant_Account_Case_Study.png
Overview

Connecting payments to fundraising events

OneCause customers use merchant accounts to connect payment processing to fundraising events and platform workflows. The existing experience created confusion around account setup, connection status, and where users should go to manage or connect accounts.

This project focused on improving the merchant account experience through UX evaluation, clearer account states, and a more understandable path for customers configuring payment-related settings.

Role Product Designer
Timeline 2-week Agile sprint
Methods Heuristic evaluation, high-fidelity design, agile delivery
Focus Payments UX, merchant account management, account states, desktop UI
The Problem

Account setup created avoidable ambiguity

Merchant account setup was a critical part of the fundraising platform, but the experience created avoidable ambiguity for customers trying to connect or manage payment accounts.

Customers needed to understand whether they already had a merchant account, whether an account was connected, what status it was in, and what action they should take next. The experience needed to make account setup and payment configuration clearer without adding unnecessary steps.

Design Challenge

Helping customers find the right action

How might we make merchant account setup easier to understand while helping customers quickly identify the right action based on their account status?

The experience needed to clarify

  • Whether an account already existed
  • Whether an account was enabled, pending, or disabled
  • Whether the user needed to create, connect, or manage an account
  • Which merchant account should be used for payment-related configuration
  • How to reduce unnecessary confusion between new-account creation and existing-account connection
UX Direction

Three questions to answer at a glance

I focused the design direction around clearer account visibility, more explicit status states, and improved guidance for connecting or managing merchant accounts.

The goal was to help users answer three questions quickly:

1

What merchant accounts exist?

2

What is the status of each account?

3

What action should I take next?

Account visibility

Make merchant accounts easier to scan and manage from a centralized view.

Status clarity

Use clear status indicators so customers can understand whether an account is enabled, pending, or disabled.

Connection guidance

Make the path for connecting an existing account clearer so users do not default to creating a new account unnecessarily.

Payment configuration context

Help users understand how merchant accounts connect to payment setup and event configuration.

Merchant Accounts list with status labels
Merchant Accounts list — multiple accounts with status labels Crop from img/Merchant Accounts 1-min.jpg, save as img/merchant-account-list-status.png
A centralized list of merchant accounts with clear status indicators
Solution Details

A more structured account experience

The updated direction emphasized a more structured merchant account management experience, with clearer account rows, status indicators, and entry points for creating, connecting, or managing accounts. For event-level payment setup, the experience also needed to support selecting the appropriate connected merchant account so users could understand how account configuration related to specific fundraising events.

01

Make account status visible in the list view

02

Separate new account creation from existing account connection

03

Provide clearer guidance for customers who already had an account

04

Preserve the relationship between merchant accounts and event payment settings

05

Use high-fidelity desktop UI patterns that fit the existing OneCause platform

Payment configuration showing merchant account selection
Payment configuration — selecting a connected merchant account for an event Crop from img/Merchant Accounts 2-min.jpg, save as img/merchant-account-payment-config.png
Selecting a connected merchant account inside event payment configuration
Outcome

A clearer path for managing merchant accounts

The resulting design direction clarified how merchant accounts were displayed, understood, and connected inside the platform. It gave customers a clearer path for managing existing accounts, creating new accounts when needed, and understanding how merchant accounts related to payment configuration.

What This Demonstrates

This project shows how I approach B2B platform complexity: by identifying confusing decision points, clarifying system states, and designing workflows that help users configure important operational settings with more confidence.