top of page

Remote Deposit Capture

Designing a scalable, multi-bank deposit platform from discovery to shippable flows

Note: Due to NDA constraints, I’ve modified a few details and visuals where necessary.

Hand and iPhone 16 Pro.png

At a Glance

Remote Deposit Capture (RDC) lets businesses and financial institutions deposit checks remotely via mobile device, without a branch visit. This case study covers the end-to-end discovery and UX design process behind a scalable RDC platform built to serve multiple banks across the US and Europe.

My Role & Constraints

Led end-to-end UX: discovery, flow design, wireframes, and stakeholder alignment across Product.

Operated under a constraint most consumer products don't face, every screen had to work for 12+ banks with different regulatory and operational rules, without forking the design.

No single decision-maker feature scope had to be negotiated across.

The Core Tension

Banks kept asking for custom features. But underneath nearly every request was the same handful of jobs, deposit faster, see status clearly, fix mistakes without calling support.
The job was to find the platform underneath the requests not build a feature for every ticket.

Deposit Entry & Account Selection

  • Used a "show instructions?" decision branch so first-time depositors get guided onboarding (signature, lighting tips, deposit limits) while returning users skip straight to the form.
     

  • Account selection surfaces available balance inline, so users can choose the right account without leaving the flow to check balances elsewhere.
     

  • An optional disclaimer slot was built into the interstitial, letting individual banks add their own compliance copy without redesigning the screen.

1.png

Amount Entry & Check Capture

  • Covers numeric amount input through front/back camera capture, including system permission and exit-intent states.
     

  • Used the device's native numeric keypad for amount entry to reduce input errors and keep the experience familiar.
     

  • Camera capture includes real-time corner-guide framing for both check sides, with captured thumbnails replacing the empty state once an image is taken.
     

  • Designed an explicit "discard deposit" confirmation for users who exit mid-flow, preventing accidental data loss without blocking quick exits.

2.png

Verification, Review & Exception Handling

  • A validation decision point splits successful checks straight to review, while uncertain reads route to an "unverified check" state instead of silently failing.
     

  • The unverified-check screen gives users two clear paths confirm and proceed, or edit/retake rather than forcing a blind resubmission.
     

  • Deposit limit messaging ("You have Y left of your X daily limit") is surfaced at the review step, before submission, so users aren't surprised after confirming.

3.png

 Deposit History & Rejection Detail

  • Deposit history groups items by status (pending vs. processed) so users can scan for what's still in progress versus settled.
     

  • Rejected deposits link directly to a reason screen written in plain language, closing the visibility gap identified in early research.
     

  • Front/back check images remain viewable from history at any time, giving users a record to reference if they need to dispute or resubmit.

4 - history.png

Common Error & Limit States

  • Standardized iconography and copy structure (icon, headline, supporting line, single action) across connectivity, loading, and limit-reached states for visual consistency.
     

  • The "Check deposit unavailable" state handles a business-rule edge case accounts that don't support check deposits rather than showing a generic error.
     

  • Daily and per-check limit values are templated as variables, so each bank can configure its own thresholds without a new design.

6.png

Designing the Flow

image.png
image.png
image.png

Note: Due to NDA constraints, I’ve modified a few details and visuals where necessary.

bottom of page