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.
Executive Summary
ProductBhairav 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 toolsFrontend
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 applib/ ├── core/ ├── models/ ├── services/ ├── providers/ ├── screens/ ├── widgets/ ├── routes/ ├── themes/ ├── utils/ ├── constants/ └── main.dart
Keep UI and business logic separate. Build reusable components for buttons, cards, dialogs, bottom sheets, inputs, and loading states.
Airtable Database
Data layerAirtable will store merchant data, transactions, activation codes, app settings, feature flags, app version, and notifications for Version 1.0.
| Table | Purpose |
|---|---|
| Merchants | Store merchant profile, UPI ID, status, and business data. |
| Transactions | Track every collected payment and status. |
| Activation Codes | Control onboarding and manual activation. |
| Settings | App-wide configuration and merchant preferences. |
| Version | Force update and release information. |
| Notifications | Announcements and messages for merchants. |
| Feature Flags | Turn features on or off without app release. |
| Support | Help information and contact support data. |
Merchant Fields
- Merchant ID
- Store Name
- Owner Name
- Phone Number
- UPI ID
- Address
- GST Number
- Logo URL
- Status
- Created Date
Firebase Authentication
LoginFirebase 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
NotificationsOneSignal 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 APIAll 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 hostingUse 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| Screen | Purpose |
|---|---|
| Splash | App launch and branding |
| Login | Phone OTP authentication |
| Dashboard | Collections and overview |
| Merchant Terminal | Enter amount and generate QR |
| Transactions | View payment history |
| Profile | Merchant details and business info |
| Settings | Preferences and security |
| Legal | Privacy, Terms, Refund policy |
API Plan
Backend routes| Endpoint | Purpose |
|---|---|
| /login | OTP login and session creation |
| /merchant | Merchant profile and UPI details |
| /transactions | Transaction list and details |
| /generate-qr | Generate payment QR |
| /version | Version and force update check |
| /notification | Announcements 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 controlThe 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
Legal Pages
Policy- Privacy Policy
- Terms & Conditions
- Refund Policy
- Cancellation Policy
- Contact Us
- About Us
Roadmap
FutureVersion 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
GrowthBhairav 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 byBhairav One™
Product Development Blueprint
Prepared by Krish Jain
Version 1.0 planning document for the Bhairav One merchant application.