Whitelabel Solution (Planned)

Proposed enterprise whitelabel solution for partners with AUM exceeding 100cr

Whitelabel Solution (Planned)

Vision

The proposed Wealthy whitelabel solution would enable larger partners (AUM > 100cr) to maintain their brand identity while leveraging the Wealthy platform infrastructure. Wealthy would operate as the backend platform while the partner’s brand remains visible to clients.

Business Overview (Proposed)

Target Partners

  • Partners with AUM exceeding 100 crores
  • Partners requiring brand preservation across all client touchpoints

Value Proposition (Proposed)

For Partners:

  • Maintain brand identity and client relationships
  • Reduced time-to-market with proven infrastructure
  • Focus on business growth while Wealthy handles technology
  • Built-in compliance and regulatory adherence

For Wealthy:

  • Expand platform reach through partner networks
  • Leverage existing infrastructure efficiently
  • Strengthen partner relationships

Proposed Client Experience

Partners would get complete branding across:

  • Mobile App: Partner-themed app (launched on Wealthy’s playstore or partner’s own playstore)
  • Communications: All SMS, WhatsApp, emails from partner identity
  • URLs: Onboarding, proposals, reports on partner domains
  • Legal Pages: T&C, Privacy Policy with partner branding
  • Reports: Partner-branded report templates and URLs

Client Journey:

  1. Discovery through partner app or onboarding links
  2. Signup via partner-branded URLs
  3. Complete app experience under partner branding
  4. All communications from partner identity
  5. Seamless partner-branded journey throughout

Partner Onboarding Process

  1. Qualification: AUM verification (>100cr), business assessment
  2. Setup: Domain configuration, brand assets collection, communication providers
  3. Configuration: Portal settings, DNS setup, template creation
  4. Testing: App, communication, URLs, end-to-end validation
  5. Launch: Deployment, migration (if applicable), monitoring

Operational Requirements

Marketing Team:

  • Create SMS/WhatsApp templates per partner (significant effort)
  • Content approval workflows
  • Compliance verification per partner

Technical Team:

  • Domain configuration support
  • SSL certificate monitoring
  • App deployment and configuration management

Business Team:

  • Partner qualification and enablement decisions
  • Commercial negotiations
  • Ongoing relationship management

Current Implementation Status

What’s Built (Proof of Concept)

  • One Partner Microsite: Single partner website implementation
  • Basic Authentication: Signup/login APIs on partner domain
  • SSL Management: Caddy with Let’s Encrypt for automatic certificates
  • Domain Routing: Basic custom domain support

What’s Not Yet Implemented

  • Multi-tenant communication system
  • Partner-branded mobile apps
  • Complete URL management system
  • Multi-partner configuration portal
  • Partner-specific push notifications
  • Whitelabel access control enforcement
  • Partner branding configuration UI

Proposed Technical Implementation

Planned Mobile Application Options

Option 1: Partner’s Own Playstore (Proposed)

  • React Native for remote code push
  • Partner manages app listing and distribution
  • Complete brand control

Option 2: Wealthy Common Playstore (Proposed)

  • Existing app with feature flags
  • Theme support for partner branding
  • Shared codebase with partner configurations

Planned Communication System

Multi-Tenant Architecture (Proposed):

  • New partner-client tenant model
  • Templates with dynamic placeholders (logo, footer, brand content)
  • Partner-specific SMS, WhatsApp, and Email providers
  • Communications sent through partner’s provider credentials

URL and Domain Management

Custom Domains:

  • Proposal URLs: Partner-specific generation links
  • Deep Links: mylinks.{partner-domain.com}/{url}
  • Onboarding Links: Custom branded signup flows
  • Report URLs: Partner-branded report templates and URLs

Domain Setup:

  • Wealthy manages domain access OR partner configures DNS
  • Configuration through Partner Branding section
  • SSL certificates automated via Caddy and Let’s Encrypt

Regulatory Pages

Partner Microsite feature manages:

  • Terms & Conditions
  • Privacy Policy
  • Regulatory disclosures
  • Used in app links, communications, and web platform

Access Control

  • Wealthy app login disabled for whitelabel clients
  • Enforced partner app usage only
  • Clean separation between standard and whitelabel clients

Push Notifications

Skynet Integration:

  • Token storage system for multiple apps
  • Partner-specific notification routing
  • Supports simultaneous whitelabel apps

Authentication Architecture

Partner Microsite System:

  • Manages partner websites (Go-based)
  • Extended for signup and login APIs
  • Caddy handles SSL via Let’s Encrypt
  • Multi-domain support with automatic certificates

Authentication Flow:

Signup/Login: Partner Microsite APIs (partner domain)

  • Initial authentication through partner-branded URLs
  • Token generation via partner domain

Post-Authentication: Direct Wealthy API calls

  • All product APIs call api.wealthy.in directly
  • No data separation - data resides with Wealthy
  • Token-based authentication for all subsequent requests

Broking Login: Web-based flow

  • Web login generates token
  • Native app calls with generated token

Configuration Management

Partner Portal Settings (Partner Branding section):

  • Domain settings
  • Brand assets (logos, colors, themes)
  • Communication preferences
  • App configuration

Enablement Process:

  1. Business team evaluates partner (AUM, value)
  2. Whitelabel enabled for partner
  3. Configuration settings visible in portal
  4. Partner completes setup
  5. Technical validation
  6. Activation

Key Services Modified

  • Partner Microsite: Authentication APIs
  • Communication System: Multi-tenant templates and providers
  • Skynet: Multi-app push notifications
  • Caddy: SSL and domain routing
  • Mobile Apps: Theme and feature flags

Security & Compliance

  • Data stored centrally with Wealthy (no data separation)
  • Partner-specific access controls and audit trails
  • Separate authentication flows per partner domain (signup/login only)
  • All subsequent API calls to api.wealthy.in with token-based auth
  • Regulatory compliance per partner

Infrastructure

  • Cloudflare-backed API (api.wealthy.in) for global performance
  • Only frontends and communication system are whitelabel-specific
  • Backend APIs and data storage remain consistent
  • Configuration-driven customization reduces development overhead