PAYMENTS · 0→1 · STRIPE · B2B

Getting paid faster without changing how anyone works

Filevine's ecosystem had multiple products that sent invoices but no way to actually collect payment on them. I designed the full payment lifecycle from zero, integrated across the platform.

The obvious gap

Filevine's platform had a clear hole: users could generate and send invoices across multiple products, but there was no way to collect payment on those invoices. Customers were leaving the ecosystem to get paid, adding steps and losing visibility into their finances.

Build a way to send an invoice and collect payment on it, on behalf of our customers, without pulling anyone out of their existing tools.

Designing for the person who never sees the UI

Most users of the payments functionality would send invoices from other Filevine applications and never visit the payments interface directly. That constraint shaped everything. The standalone UI needed to serve the accountant or managing partner who tracks cash flow across the firm.

I kept it close to the design system and component library, worked within the constraints imposed by Stripe's integration requirements, and prioritized features that accounting personas told me they'd actually use: quick cash flow visibility, standard net-30/60/90 filters, and data export for third-party accounting tools.

Secondary navigation left room for future needs. That foresight paid off quickly. We've since added payment option settings, account management, portal customization tools, and more without restructuring the layout.

The client-facing payment portal

The most trust-sensitive surface was the one our customers' clients would see: a payment form asking for credit card information. Two things had to be clear: you're paying this law firm, not Filevine, and your payment information is safe.

I built a clean, brandable form using design system components. Customers could add enough of their own branding to instill confidence without Filevine's interface getting in the way. Stripe handled the sensitive data under the hood.

Why this project matters

This was a 0→1 build with real constraints: Stripe's requirements, multiple internal applications that needed to trigger payments, and an end-user (the law firm's client) who needed to trust a form they'd never seen before. The design didn't try to be clever. It stayed close to established patterns, kept surfaces familiar, and focused on the operational needs of the people managing money. The result was something that integrated across the ecosystem and immediately reduced outstanding invoices.

NEXT PROJECT

Cross-Product Design System

Building the component foundation for an ecosystem of legal tech applications, with WCAG accessibility and multi-theme support baked in.

Read case study →