Build UPI Bill Splitter App

PROJECT REQUIREMENTS DOCUMENT (PRD)



1. EXECUTIVE SUMMARY

The proposed product is a utility application (available on Web and Mobile) designed to help merchants seamlessly split large UPI payments (typically above ₹2,000) into smaller, sequential parts. By splitting bills, merchants can optimize transaction routing and avoid standard Merchant Discount Rate (MDR) fees associated with high-value transactions. The app acts merely as a QR code and payment link generator. It does not process payments, require account creation, or store sensitive user data on any backend servers.



2. PRODUCT GOALS & OBJECTIVES

- Provide an easy-to-use calculator and QR generator for splitting bills.

- Eliminate the need for merchant onboarding or account creation.

- Ensure 100% privacy by keeping all UPI IDs and bill histories local to the device.

- Support multiple payment collection methods: in-person, remote (link sharing), and static QR stickers.

- Educate merchants on potential fee savings through an integrated calculator.



3. TARGET AUDIENCE

- Primary: Small to medium-sized business owners, retail shopkeepers, and service providers in India who accept payments via UPI.

- Secondary: Consumers (customers of the merchants) who need a frictionless way to pay these split bills without downloading any new apps.



4. CORE FUNCTIONAL REQUIREMENTS (Shared across Web & Mobile)



4.1. Split Calculator & Logic

- The system must accept a total bill amount input from the merchant.

- The system must automatically split the amount into parts where no single part exceeds ₹2,000 (e.g., a ₹5,500 bill becomes ₹2,000, ₹1,999, and ₹1,501).

- The split logic must be visually presented to the user before generating the payment codes.



4.2. Payment Collection Modes

- Mode 1: "At the Counter" (Sequential QR)

- The app generates a dynamic QR code for the first part of the payment.

- The merchant UI includes a manual "Received" button to reveal the QR code for the next part.

- Mode 2: "Over Messaging" (Payment Links)

- The app generates a unique URL containing the merchant's UPI ID, shop name, and the split amounts.

- The link must be shareable via WhatsApp, SMS, etc.

- Clicking the link opens a customer-facing web page guiding them to pay part-by-part. Tapping a part opens their default UPI app with pre-filled amounts.

- Mode 3: "With a Sticker" (Static QR)

- The app generates a printable, static QR code for the merchant's counter.

- Customers scan this with a standard phone camera (not a UPI app), which takes them to a web interface where they enter their total bill and pay in parts.



4.3. Merchant Fee Estimator

- Include a calculator that shows estimated standard MDR fees (e.g., 0.4% above ₹2,000) and displays the potential monthly/yearly savings the merchant achieves by using the app.



4.4. Customer-Facing Web Interface (For Links & Stickers)

- Must be a lightweight, mobile-optimized webpage.

- Displays merchant name, UPI ID, total amount, and clear steps (e.g., "Part 1 of 3").

- Integrates deep-linking (upi://pay) to launch installed UPI apps (GPay, PhonePe, Paytm, etc.).

- Includes manual checkboxes/buttons for the customer to mark a part as "Paid" before moving to the next.



5. PLATFORM-SPECIFIC REQUIREMENTS



5.1. Mobile Application (Android)

- Must function offline-first where possible.

- Local Storage: Use encrypted local device storage (e.g., SharedPreferences or local SQLite/Room) to save the merchant's UPI ID and shop name so they don't have to enter it every time.

- Share Intent: Native integration with Android's share sheet to easily send payment links via installed messaging apps.

- Form Factor: Optimized for one-handed use at a busy checkout counter.



5.2. Web Application

- Progressive Web App (PWA) capabilities recommended for "Add to Home Screen" functionality.

- Responsive Design: Must work flawlessly on mobile browsers (merchant using it on phone) and desktop browsers.

- URL State Management: Payment links must encode the transaction details securely in the URL parameters or payload without relying on a database.

- Cross-Browser Compatibility: Deep-linking to UPI apps must work across Chrome, Safari, and custom Android webviews.



6. NON-FUNCTIONAL REQUIREMENTS



6.1. Privacy & Security

- Zero Data Retention: The application must not send customer payment data, merchant UPI IDs, or transaction volumes to external servers. All generation happens client-side.

- The app must clearly state in its UI and Terms that it does not verify payment success (merchants must rely on their existing bank SMS or soundbox for confirmation).



6.2. Usability & Performance

- The interface must be highly intuitive, requiring minimal taps to generate a QR code.

- Multi-language support (e.g., English, Hindi) is required to cater to the target demographic.

- The customer-facing payment page must load in under 2 seconds on 3G/4G networks.



7. USER FLOWS



7.1. Merchant "At Counter" Flow

1. Merchant opens app/web.

2. Enters total bill amount (e.g., ₹4,500).

3. App displays split (₹2,000, ₹1,999, ₹501).

4. Merchant selects "At Counter".

5. App shows QR for ₹2,000. Customer scans and pays. Merchant hears soundbox confirmation and taps "Received".

6. App shows QR for ₹1,999. Customer scans and pays. Merchant taps "Received".

7. App shows QR for ₹501. Customer scans and pays. Transaction complete.



7.2. Customer "Remote Link" Flow

1. Customer receives link via WhatsApp and taps it.

2. Webpage opens, showing "Paying ₹5,500 to Sharma Electronics in 3 parts".

3. Customer taps "Pay part 1 - ₹2,000". UPI app opens, user authenticates.

4. User returns to browser, taps "Yes, next part".

5. Process repeats until all parts are marked paid.

---
來源：Freelancer.com | 出價次數：2 | 剩餘時間：6 日 | 專案類型：固定預算