0 → 1 · Fintech

Keap Pay

When WePay shut down, I designed Keap’s own payment product from scratch, from zero to launch in four months, so thousands of small businesses kept getting paid.

Role
Sole Product Designer
Timeline
4 months
Team
1 PM · 14 engineers
Scope
Onboarding · Migration · Payments

My contribution

I was the sole designer for onboarding, migration, and payment reporting. I ran merchant research, helped the team agree on the migration flow, and worked with engineering on the Rainforest integration and payment components.

Problem

Replace the processor. Keep businesses running.

Keap is an all in one CRM for small business owners, acquired by Thryv in October 2024. WePay, Keap’s embedded payment processor, was acquired by Chase and ended third-party integrations. Thousands of merchants used it for invoices, subscriptions, and payment links. We had four months to move them to a Keap-owned system.

01

A hard deadline

Four months to build the replacement and move merchants before WePay stopped working.

02

Nothing could break

Invoices, subscriptions, and payment links had to keep working. A failed payment meant a business lost money that day.

03

New verification on top

The new provider needed KYC verification, so merchants who already had payments set up faced a longer sign-up.

Old payment processing settings with WePay set as default and Stripe and PayPal listed the same way1234
Payment processing settings, before the redesign.
  1. 1

    A vague intro

    It said Keap “may need some additional information” without saying what or why.

  2. 2

    WePay was still the default

    The page set merchants up on the processor that was shutting down.

  3. 3

    Status was easy to miss

    A small “Pending” and an empty bank account field did not tell merchants if they could get paid.

  4. 4

    Every option looked the same

    WePay, Stripe, and PayPal had the same weight and almost the same pricing line, so nothing said which one to pick.

Who we designed for

Small businesses with 5 to 25 employees, making $250K to $2M a year in sales.

What merchants felt

The payment tools built into their CRM lacked features and support. WePay closing made them nervous, and payment friction was already hurting retention and growth.

Constraints

  • Speed. Six weeks for research and design, with no groundwork to start from.
  • People. I was the only designer, with little research support.
  • Platform. The provider was white label, with no shared design files or design system.
  • Business pressure. Contracts, leadership urgency, and the risk of churn and lost revenue.

Research

One question mattered most: when will the money arrive?

I started with stakeholder interviews and product analytics, benchmarked five competitors, led two cross-functional workshops, and interviewed ten small business owners.

Stakeholder interviews

Move to Stripe or build our own? Before anyone picked, I helped the team line up priorities and constraints.

What the data showed

Merchants ran a lot of payments through Keap, but Keap earned a small share of that revenue in 2023 and 2024. Only about 25% of customers used payments, and payments felt disconnected and hard to track.

Five competitors

They left gaps in integration, pricing clarity, and automation. Those gaps shaped how we positioned Keap Pay.

Two workshops

Together we defined the MVP scope and core user flows, and agreed on the long term direction and go to market plan.

  1. Walk me through how you get paid today, from sending an invoice to the money landing in your bank.
  2. Tell me about the last time a payment went wrong. What happened, and what did you do?
  3. How do you know when a payment will reach your account?
  4. Why did you choose your current processor? What would make you switch?
  5. What worries you most about moving to a new payment system?
  6. Which payment details do you check most often, and where do you look?

What we heard. Owners needed confidence during setup, and every one of them asked some version of the same question: when will the money arrive? Trust and transparency mattered most.

The questionHow might we move merchants from WePay to Keap Pay with as little friction as possible, while they keep trust and control?

Design stance

Give merchants confidence during setup, and one clear place to see where their money is.

Process

Make the migration understandable, not just compliant.

KYC rules and a new provider API shaped the work. I focused on clear progress, familiar payment patterns, and visible payout status.

01

Build trust where it matters

Business identity and security cues sit next to sensitive payment fields.

02

Make progress explicit

Verification is split into small steps, and the flow says what transfers from WePay, so merchants never enter the same thing twice.

03

Show the path to payment

Payments and payouts live in one view, so merchants can see the status of their money.

Phase 1

WePay merchants

  • Redesign the payment page
  • Create the Keap Pay sign-up
  • Design onboarding, payment, and deposit dashboards
  • Payments API integration through JS packages

Phase 2

Authorize.net users and new users

  • Fix technical debt and bugs
  • Add APIs, ACH, and tokenization
  • Migrate payment data

Phase 3

Thryv payment agents, concept

  • Move Keap Pay into the Thryv platform
  • Add agents for collections, retries, disputes, and payouts
  • Let owners choose how much each agent does alone

Product

More merchants finish setup, and they take their first payment sooner.

Business

Higher total payment volume, revenue, and attach rate.

Support

Fewer onboarding tickets and errors.

Platform

More WePay merchants migrated, and Keap owning the payment journey end to end.

Migration flow with two starting points converging on onboarding
Two starting points, one path. WePay merchants and users of other processors start differently, then meet on the same onboarding steps.

Product Design

One connected payment experience.

Setup, collecting payments, and reporting were designed together, with familiar Keap patterns around the provider integration.

Testing feedback from 7 merchants on the first version

What worked

Onboarding was straightforward.

One big issue
“There’s so much text on the sign-up page… it’s overwhelming.”
What I changed

Cut the content down and split the page into short sections.

Results

Shipped inside the migration window.

Moderated task-based sessions shaped the design through delivery. These launch results reflect the whole team’s work.

First quarter
$70M+

Processed through the new system.

Migrated on time
70%

Of affected WePay merchants, within the four month deadline.

Payment volume
+30%

Total payment volume growth within six months.

Payments revenue
+18%

Revenue lift from payments after launch.

SUS score
73.9

Above the 65 to 70 typical for payment products.

Impact

  • Keap owned the payment journey end to end, instead of depending on WePay.
  • Merchants kept getting paid through the switch. 95% took their first Keap Pay payment within a month.
  • Fewer setup questions after launch, because the flow said what moves over from WePay.

What I learned

  • Clarity builds trust. When money is involved, people need to know what happens next.
  • Align across teams early. Product, engineering, and payments needed the same picture before design started.
  • Constraints sharpen the MVP. A short window made it easier to say no.

Two questions stayed open after launch: when will the money land, and what happens when a payment fails. That is where the next phase starts.

After the acquisition

Next: payment agents in Thryv.

Thryv bought Keap in October 2024, and Keap Pay moved into the Thryv platform. Getting paid was now the easy part. The hard part was follow up: late invoices, expired cards, disputes. This concept adds agents to the Thryv Payments page. They find the problem, suggest a fix and say why, and follow up only as far as the owner allows. Everything they use already exists in the payment provider, like payout timing, card updates, and chargeback reports.

1. Detect

The owner sees what needs them, and nothing else.

The Keap Pay payment and deposit dashboards stay as they were. On top, the Overview shows three action items with the reason for each, and everything the agents already handled moves to Agent activity.

  • Say what went wrong. “Card expired Oct 31” instead of a risk score.
  • Only what needs a decision. Three items need the owner. The rest is in Agent activity.
  • Don’t cry wolf. A payout moved by a bank holiday is marked Info, with no button.

2. Recommend

A suggested fix, the reason, and what happens next.

Opening an item shows what happened, the fix, and why it should work, using this client’s own history. The email uses the Selected AI Response style from Thryv Reputation. A timeline shows which step waits for the owner.

  • Use the client’s own history. “Paid within a day of the final reminder, twice” is something an owner can check.
  • Show the exact email. The owner can edit it before it goes out.
  • Say what it won’t do. No late fee, because the invoice terms don’t include one.

3. Follow up

Each agent has one setting for how much it does alone.

Suggest, Ask first, or Auto. Every agent starts on Ask first. The Collections agent uses the reminder emails owners already set up in Thryv Automations, so emails are edited in one place. Its page shows every client in follow up, which step they are on, and what needs approval.

  • One set of controls. I first built follow ups as a separate tab, then merged it into the agent so two settings never fight.
  • Guardrails stay on Auto. The final reminder and retries over a limit still wait for the owner.
  • Pause, not undo. After approving, there are 10 seconds to undo before an email goes out. Once it’s sent, it can’t be taken back, so risky steps ask first and any agent can be paused.

The rules behind it

Where the agent stops and asks.

Before any screen, I mapped what the collections agent may do alone and where a person always decides. The merchant never sees this map. They see the result: one client’s timeline, with the step that waits for them.

PAID SOFT DECLINE: RETRY AT THE BEST TIME, UP TO 3 TIMES HARD DECLINE COLLECTIONS AGENT Invoice is dueFrom Thryv invoicing Pay link and QR codeOn every invoice, one tap to pay Email and text remindersYour schedule, quiet hours Card on file chargeOver $500 asks you first BANK You see it livePayments dashboard and activity Payment collectedBalance cleared, receipt sent Stop and ask youNo retry on an expired card
  • Soft decline: retry, with limits. Up to 3 retries, at the time this client usually pays.
  • Hard decline: never retry. An expired or stolen card stops the flow and becomes an action item with a fix ready.
  • Money above a limit: ask first. Card charges over the merchant’s limit wait for an OK, even when everything else runs on its own.

How I would know it works

  • Money recovered from failed payments, compared with today.
  • Problems fixed before the merchant noticed, and fewer “where is my money” tickets.
  • How often merchants approve a suggestion as is. If they keep editing, the agent is not ready to act alone.