Context
As MillionBridges matured into a regulated, multi-market remittance service, its brand and app needed to match. The platform was rolling out a new corporate identity and a redesigned experience across web and mobile, and, because people were about to trust it with their money and their identity documents, it needed authentication that was both genuinely secure and effortless enough for everyday use.
The challenge
- Roll out a new corporate identity and UI/UX consistently across both the web platform and the mobile app, against a single agreed design source of truth.
- Replace password-only access with biometric authentication that stays usable on the full range of real devices, including those with no biometric hardware or no enrolled biometrics.
- Make sure the security model covered the unglamorous but critical edge cases: failed reads, changed fingerprints or faces, lockouts, inactivity timeouts, and payment confirmation, not just the happy path.
- Surface regulatory trust signals (for example, verifiable registration with the Bank of Spain) directly in the product.
My role
As Product Manager and Product Owner on this work, the product definition was owned here, working with the design team, the development team, and the client. The role covered aligning the app and web redesign to a single design specification and authoring the biometric security framework as a detailed FSD with exhaustive, testable acceptance criteria. Every state and edge case was specified, then driven through delivery and acceptance testing that the team carried to release.
As on the other work here, AI tools were part of the workflow to speed up specification writing and to prototype flows for stakeholder validation before build. For a security framework, that mattered: it made it possible to pressure-test the full decision tree of states early, so the edge cases were designed in rather than discovered in production.
Approach
- One design source of truth. The spec required every screen and component on both web and app to adhere strictly to the agreed design file, so the new identity landed consistently rather than drifting between platforms.
- Device-aware biometric setup. The design defined distinct flows for the three real-world cases: devices with no biometric hardware, devices that support biometrics but have none enrolled, and devices with biometrics ready, each guiding the user to the right setup, always with a passcode fallback.
- Security in the edge cases. The spec covered behavior for failed biometric reads, OS-level biometric changes (which invalidate biometric login until password re-auth), consecutive-failure lockouts, password reset to regain access, and automatic logout after background inactivity, including not restoring an in-progress payment after a session expires.
- Biometric payment confirmation. The spec required a transfer to trigger biometric (or passcode) confirmation before anything is submitted, so no payment leaves the app without the user's explicit, verified approval, with clear fallback and cancellation behavior.
- In-product trust signals. The design added an in-app verification screen letting users confirm the platform's regulatory registration directly, turning a compliance fact into visible user trust.
- KYC onboarding UX. The redesigned onboarding was aligned with the identity-verification flow, including moving from static photo upload to guided video capture, and reflecting the clear account states (registered, then active only after verification passes) so users always knew where they stood, rather than treating verification as a bolt-on.