Project Title: Develop KistiPay – BNPL “Pay in 4 Weekly” App + Merchant/Admin System (Bangladesh) About KistiPay KistiPay is a Bangladesh-first fintech product offering Pay-in-4 weekly installments for everyday purchases (starting with food delivery apps like Foodpanda/Foodie and expanding later). We will launch with manual approvals, and move to instant approvals after ~1 year based on scoring and repayment history. We are looking for an experienced team/company who can deliver a production-ready MVP with proper documentation and a scalable architecture. What we need (Scope) 1) Customer App (Android & iOS) • User registration/login (phone OTP) • KYC (NID + selfie + basic info) • BNPL checkout flow (Pay-in-4 weekly) • Installment schedule, payment reminders, due dates • Payment status tracking, receipts, transaction history • Wallet/limits view (available limit, used limit) • Support/ticket/complaint module 2) Admin Dashboard (Backoffice) • Customer management, KYC review/approval • Manual approval workflow (at launch): approve/decline limit + transactions • Risk controls: set customer limit, freeze account, blacklist • Installment monitoring dashboard (on-time/late/default) • Collections view: due today, due in 7 days, overdue buckets • Penalty rules automation • Reporting: daily disbursement, collections, outstanding, default rate, cohort performance • Role-based access (Admin/Operations/Collections) 3) Core BNPL Rules • New customer max ticket: ৳500 • Repeat customer ticket: ৳1,000 (based on history/admin rules) • Pay-in-4 weekly installments • Platform revenue: ৳50 per successful transaction (from merchant side or internal accounting; PSP fees excluded) • Bad debt assumption: 1% users will not pay (system should track/write-off category) • No extra profit/penalty for first 3 months of payment failure • After 3 months overdue: ৳100 penalty per week until paid (configurable rule engine preferred) 4) Payments (Bangladesh) • PSP to support: bKash, Nagad (payment collections; and disbursement if needed) • PSP charges will be handled separately 5) Merchant/Partner Side Option A (Preferred for MVP): • Start with manual merchant order entry in admin (Food delivery order ID + amount + customer phone), then approve & create repayment plan. Option B (If feasible): • Merchant portal + API integration for partners later. Deliverables required in your proposal (Mandatory) A) Technical Proposal 1. SRS Document (full requirement spec with user stories + acceptance criteria) 2. Proposed System Architecture (diagram + components) 3. Database schema (high level) and key entities (Users, Orders, Installments, Payments, Penalties, Limits, Risk flags) 4. API list (REST/GraphQL) 5. Security approach (PII protection, encryption, RBAC, audit logs) 6. Deployment approach (cloud recommendation + CI/CD) 7. Timeline with milestones (MVP → pilot → production) B) Financial Proposal • Full cost breakdown: UI/UX, mobile app, backend, admin panel, QA, deployment • Monthly maintenance/support cost • Optional add-ons cost (iOS app, merchant portal/API, scoring engine, analytics, SMS/WhatsApp automation, etc.)