Home
Get in touch
Andrés Vanegas
CASE STUDY

Case Study: Automating Regulatory Logic with "Smart Split

Transforming Regulatory Fricition into a Seamless user anatomy Experience

Impact

I architected a logic-driven withdrawal engine that transformed a high-friction regulatory constraint into a seamless self-service experience. By automating complex "Closed Loop" logic, we successfully boosted withdrawal automation from 45.6% to 85.7% and reduced support tickets by 40%, significantly lowering the cost-per-transaction.

Role

Product Designer (Strategy, UX/UI, Logic Architecture), Research, Cross-functional Leadership.

Strategy

Understanding the “Net Deposit” rule. Map out in order to let Engineering knows I understand the backend constraints

WHERE WE STARTED

Withdrawal 1.0

In the high-stakes Fintech and iGaming industries, the "Closed Loop" policy is a non-negotiable anti-money laundering regulation. It mandates that users must withdraw funds back to their original deposit sources before claiming profits. Historically, our platform treated this as a manual, high-friction process. We believed that as long as the funds eventually reached the user, the manual intervention from our finance team was just a "cost of doing business."I directed the initial design strategy, treating the problem as a "Revenue Leak" and a "Trust Killer". Our initial interface was a static, sterile form that often left users confused when a withdrawal was partially denied or split across multiple cards. We were operating as "order takers" for legal requirements rather than designing for the human experience.

User Frustation: Some companies explicitly state that if a user tries to withdraw to the  "wrong" method, they receive an error message that "will state which card/method you need  to withdraw to, and the amount required.

RESETTING OUR VISION

But Then

Automation stalled, and support overhead spiked. We were losing user trust

I looked for clues in our "Data Portrait" and analyzed the "Support Overhead Cost". The numbers were alarming: over 54% of withdrawals required manual back-office intervention. Users were met with generic "Something went wrong" error messages that failed to explain the regulatory "why" behind the friction.

This lack of transparency meant users felt policed rather than supported. The "Accepted Friction" of waiting days for a manual review was driving a 10% dip in user trust. I needed to find a way to turn a complex financial obligation into a manageable, transparent "task list" that users could complete themselves.

Running rapid discovery on automated compliance

A small strike team gathered, and I facilitated an "Opportunity Scraper" audit of our backlog. Our hypothesis was to move "Upstream" into the planning cycle and design a 3-Tier "Smart Split" algorithm that could handle the logic in real-time.

Armed with this vision, I architected a logic-driven system categorized into three levels: Tier 1 (Settlement), Tier 2 (Priority), and Tier 3 (Profit). Working with the Lead Engineer and QA, I delivered an "Edge-Case Blueprint" and a "Logic Matrix" to ensure the automation was 100% reliable even in complex scenarios where debt exceeded the current balance.

The service felt more like a financial tool than an entertainment experience. To break the cycle, I needed to engineer an “emotional moat” — a reason for users to stay that went beyond the next promotion.

Innovation: I replaced the static withdrawal form with a Progressive Disclosure Tracker, turning a complex financial obligation into a manageable "task list".

CASE STUDY
FINDING INSIGHT

A few thing were clear earlier

  • Logic Over Aesthetics: 97% of users successfully completed their withdrawal on the first attempt when provided with real-time feedback on where "every cent" was going.
  • Human-Centric Microcopy: Translating technical jargon like "Net Deposit Settlement" into terms like "Returning to Source" instantly reduced user anxiety.
  • Mobile-First Interaction: With 80% of traffic on mobile, a "Stacked Card Layout" was essential for one-handed efficiency and high data density management.

“When we tested the Smart Spli calculator, users felt a sense of Proactive Resolution rather than frustation.”

— A strong signal that we were building an "Emotional Moat" around a previously sterile process

Transforming to automation

Finding traction and setting up scale

I rapidly adjusted our design system to support this new "Logic-First" architecture. Based on our "Disruptive Diagnosis," I identified three primary experience patterns to validate:

Predictive Splitting: "Quiet AI" to analyze historical behavior and suggest the most likely withdrawal configuration before the user even clicks.

Visibility of System Status: Providing real-time feedback through the calculator to prevent the dreaded "Withdrawal Failed" generic error.

Results

As a result of this strategic redesign, the platform moved from a high-friction manual process to an automated leader in the industry. We successfully surged automation from 45.6% to 85.7% and reduced the "Cost-per-Transaction" by 40%. We didn't just fix a form; we engineered a self-service engine that respects the user's time and trust.

The outcome

Final Screens

CASE STUDY