QuickBooks Payment Portal

Intuit


QuickBooks' online payment portal facilitates transactions between customers and merchants. Moving over $300 million USD every day, it is a crucial component of Intuit's technology platform.

Role: Lead product designer

Teammates: 1 product designer, 1 content designer, 3 software engineers, 2 product managers, and 1 business analyst

Duration: 4 weeks

Status: Shipped 🚢

Context

On top of serving as an all-in-one bookkeeping package, QuickBooks streamlines invoicing for small and medium-sized businesses (SMBs) through monitoring cash flow and offering a wide range of payment solutions to customers.

The QuickBooks Payment Portal empowers small and medium-sized business owners by providing easy ways to get paid.

The Challenge

Analytics displayed subpar conversion rates for payment automation (Autopay), which might indicate poor discoverability or low receptiveness from users. The payment portal's interface will also need to facilitate the introduction of two new transaction channels for invoice checkouts.

How can we better surface QuickBooks Autopay while incorporating new transaction channels?

Due to an NDA, I can't go through an in-depth discussion of this initiative at the moment. If you'd like to learn more, please don't hesitate to get in touch↗︎.

Reflection


Introduce without interfering

Customer-facing platforms such as QuickBooks are in a constant state of evolution, resulting in frequent design changes that must be approached with care. New features should be incorporated into an experience without interrupting the completion of its most critical tasks.

Balance maximizing education and minimizing interaction cost

Another implication of continuous refinement is the unfamiliarity of new features to even the most seasoned users. In the context of the QuickBooks payment journey, there was a compromise to be made between preserving the simplicity of the checkout workflow and surfacing important information about what payment automation entails.