Coming Soon

Bhairav One

Blueprint Portal

This project portal is coming soon.
Admin access is required to open the full documentation.
Enter password to view the full Bhairav One blueprint.

Bhairav One Blueprint

Private planning portal for the Bhairav One merchant application.

Project Progress 52%

Product Development Blueprint

Bhairav One is a merchant payment platform for Bhairav Group. This website collects the entire product direction in one place: product goals, stack, architecture, screens, database, APIs, legal pages, testing, launch checklist, and future roadmap.

v1.0
Launch Scope
Flutter
Android First
Airtable
Database
Firebase
OTP Login

Executive Summary

Product

Bhairav One is a merchant payment platform for shop owners. The first version focuses on secure login, QR collection, transaction history, merchant data, update control, legal pages, and a polished fintech user experience.

The goal is to launch a reliable and premium Version 1.0, then expand into analytics, inventory, staff management, reports, and other business tools.

Vision

Why it exists
  • Create one elegant merchant platform for Bhairav Group.
  • Keep the experience fast, secure, simple, and trustworthy.
  • Build a scalable foundation for Android first, then iOS and web.
  • Use one backend for all future modules and products.

Technology Stack

Core tools

Frontend

Flutter for Android first. Reusable codebase for future iOS release.

Authentication

Firebase Authentication with phone OTP for simple, secure merchant login.

Database

Airtable for Version 1.0 data management, configuration, and rapid updates.

Notifications

OneSignal for announcements, version alerts, maintenance notices, and campaigns.

Backend

Secure API hosted on Bhairav infrastructure to protect secrets and control access.

Storage

Own hosting for images, documents, receipts, invoices, and uploaded files.

Flutter Architecture

Mobile app
lib/
├── core/
├── models/
├── services/
├── providers/
├── screens/
├── widgets/
├── routes/
├── themes/
├── utils/
├── constants/
└── main.dart
State Management: Provider / Riverpod Navigation: Named Routes Reusable Widgets Responsive Layout

Keep UI and business logic separate. Build reusable components for buttons, cards, dialogs, bottom sheets, inputs, and loading states.

Airtable Database

Data layer

Airtable will store merchant data, transactions, activation codes, app settings, feature flags, app version, and notifications for Version 1.0.

TablePurpose
MerchantsStore merchant profile, UPI ID, status, and business data.
TransactionsTrack every collected payment and status.
Activation CodesControl onboarding and manual activation.
SettingsApp-wide configuration and merchant preferences.
VersionForce update and release information.
NotificationsAnnouncements and messages for merchants.
Feature FlagsTurn features on or off without app release.
SupportHelp information and contact support data.

Merchant Fields

  • Merchant ID
  • Store Name
  • Owner Name
  • Phone Number
  • Email
  • UPI ID
  • Address
  • GST Number
  • Logo URL
  • Status
  • Created Date

Firebase Authentication

Login

Firebase OTP login will be used for secure merchant authentication. It keeps the login flow simple for shop owners and supports future upgrades like biometric login, Google login, and Apple login.

  • Phone number OTP login
  • Session management
  • Auto login after trusted device
  • Future biometric support

OneSignal

Notifications

OneSignal will power app notifications, update alerts, maintenance notices, important announcements, and future merchant campaigns.

This keeps communication fast without requiring users to manually check for updates.

Backend

Secure API

All app requests should go through a secure backend API. The app should never talk directly to Airtable or expose private keys in the client.

  • Authentication validation
  • Merchant data read/write
  • QR generation support
  • Version checking
  • Notification configuration
  • File upload handling

File Storage

Own hosting

Use Bhairav hosting for file storage. Store merchant logos, QR images, receipts, PDFs, invoices, and supporting documents on your own server.

/uploads
/logos
/receipts
/documents
/invoices
/temp

App Screens

UI plan
ScreenPurpose
SplashApp launch and branding
LoginPhone OTP authentication
DashboardCollections and overview
Merchant TerminalEnter amount and generate QR
TransactionsView payment history
ProfileMerchant details and business info
SettingsPreferences and security
LegalPrivacy, Terms, Refund policy

API Plan

Backend routes
EndpointPurpose
/loginOTP login and session creation
/merchantMerchant profile and UPI details
/transactionsTransaction list and details
/generate-qrGenerate payment QR
/versionVersion and force update check
/notificationAnnouncements and alerts

Security

Must-have
  • HTTPS only
  • OTP login
  • No secrets in app code
  • Server-side validation
  • Daily backup
  • Error logging
  • Audit logs
  • Version enforcement when needed

Update System

Version control

The app will check the latest version on launch. If a newer version exists, it should show a soft update or force update message depending on the release type.

  • Latest version
  • Minimum supported version
  • Force update flag
  • Update notes
  • Play Store link

Roadmap

Future

Version 1.0

Login, terminal, QR, dashboard, transactions, settings, notifications, legal pages.

Version 1.1

Analytics, better notifications, merchant enhancements, smoother onboarding.

Version 2.0

Inventory, staff management, customer database, reports, and advanced business tools.

Later

iOS app, web dashboard, multi-branch support, AI insights, export tools.

Testing

Checklist
  • OTP login works
  • Merchant terminal works
  • QR generation works
  • Transaction storage works
  • Version update check works
  • Notifications work
  • Legal pages open correctly

Launch Checklist

Release
  • Flutter build signed
  • App icon and splash prepared
  • Privacy policy published
  • Terms published
  • Play Console listing ready
  • Internal testing completed
  • Production release approved

Future Versions

Growth

Bhairav One should grow into a merchant operating system with modules for inventory, staff, analytics, reporting, and more.

Coding Standards

Dev rules
  • Write clean and readable code.
  • Use reusable widgets.
  • Keep business logic separate from UI.
  • Use meaningful variable names.
  • Comment only complex code.
  • Optimize for performance.
  • Never hardcode sensitive data.
  • Always validate API responses.
  • Follow Flutter best practices.

Folder Structure

Backend
/api
/auth
/config
/controllers
/models
/routes
/uploads
/logos
/receipts
/documents
/utils
/logs
/backups

Credits

Prepared by

Bhairav One™

Product Development Blueprint

Prepared by Krish Jain

Version 1.0 planning document for the Bhairav One merchant application.