Designing for friction to achieve 80% creator verification

I owned redesign of the creator verification experience, transforming a mandatory compliance requirement into a trust-building experience. By strategically staging friction and increasing transparency, the redesigned flow achieved an 80% verification completion rate after launch.

Role

Product Designer

Timeline

2 Months

Team

1 CEO, Co-Founder

1 CPO, Co-Founder

1 CTO

3 Engineers

Context

Creator verification requirements shifted from social authentication to ID verification.

Fanspark is a subscription-based platform where athletes and sports creators can publish exclusive content and monetize. To prevent fraud and meet compliance requirements, the business now required identity verification through Stripe Identity before creators could access these features.

The Problem

ID verification through Stripe introduced more friction to the creator verification process by asking for sensitive information (gov ID & selfie).

With Stripe Identity, creators were required to submit a government ID and take a selfie introducing significantly more friction than social authentication, which is familiar and low-friction.

Constraints

Timing was fixed

Fanspark required verification right after onboarding before creators saw any platform value

Every step was mandatory

No step could be removed or deferred for later

Stripe owned verification flow

Verification UI and flow were owned by Stripe limiting design changes to the entry point and surrounding experience

User journey of the creator onboarding experience

The Challenge

Make a mandatory compliance wall feel like an easy and transparent verification experience

With ID verification now required, I had to balance competing needs: make the experience feel trustworthy and easy to navigate for creators, while preserving the verification requirements needed for fraud prevention and compliance.

Business Goal

Prevent fraud and meet compliance

User Goal

Access services quickly and securely

Design Decisions

Ordering the steps from least to most sensitive

Based on the sensitivity of the ID verification requirement, I re-ordered the verification steps from least to most sensitive. Early steps are quick and low-risk, so creators build momentum and invest in the process before reaching the asks that require the most trust.

Tradeoff

Because every step was required and the timing was fixed, sequencing was my main lever. I couldn't remove or defer a sensitive step to reduce friction, only change the order creators encountered them in.

User journey of the creator onboarding experience

User journey of the creator onboarding experience

Proposed verification flow v. My recommendation

Increased transparency around sensitive information

I added context at each step, so creators know what we're asking for, why we need it, and who handles it.

Tradeoff

A modal overlay would keep users on the platform but a URL redirect was easier to build. The risk was that creators would lose control of the context around it so it was crucial to set expectations before directing creators off the platform and onto Stripe.

Partnering with engineering to account for edge cases

I partnered with engineering to account for what happens after creators finish verifying through Stripe, not just the happy path. Every outcome needed a clear next step so creators were never left guessing whether they were successfully verified or not.

Tradeoff

The team shipped generic error states instead of specific ones to keep the build small. There were too many possible failure cases to design for upfront, but I planned to track common edge cases post-launch to prioritize what errors required more specificity.

Solution

Integrating the new identity verification requirement

Creators verify their identity right after completing their profile, handing off to Stripe Identity and returning to Fanspark without losing context.

Highlight the benefits of verification to the creator

Led with what verification unlocks for creators, reframing the requirement from obligation to value.

Setting expectations before the handoff

Before leaving the platform, creators see what they need and what happens next, so the redirect feels expected rather than abrupt.

Platform-to-Stripe feedback after the handoff

Success, pending, process, expired and a generic error state that routes users back to Stripe to address the errors in greater detail.

Learnings

Since I couldn't control when creators would verify, I focused on how

Sometimes friction is necessary and inevitable. When you're asking users to provide sensitive information, the design opportunity is to make that friction clear, intentional, and trustworthy without treating the user experience as an afterthought.

SAY HI ☺

Copy component

Copied

mariama.abellera@gmail.com

SAY HI ☺

Copy component

Copied

mariama.abellera@gmail.com

SAY HI ☺

Copy component

Copied

mariama.abellera@gmail.com