System Requirements Document for ajopay

1. Introduction

Ajopay is a mobile-first fintech application designed to digitize the traditional African rotating savings and credit system known as Esusu, Ajo, Tontine, or Stokvel. The application aims to facilitate group savings and business funding by automating the role of the treasurer, thus enhancing transparency and reducing the risk of fraud. The target audience includes Nigerian and broader African/diaspora communities, small business starters, artisans, traders, and gig workers, many of whom have low-to-moderate digital literacy. The application is optimized for low-bandwidth environments and entry-level smartphones.

2. System Overview

Ajopay provides a platform for users to create and manage savings groups, contribute to pooled funds, and receive payouts. It replaces the traditional treasurer with an automated digital ledger, ensuring transparency and trust. The application supports various user roles, including Members, Group Admins/Treasurers, Guarantors, and Platform Admins, each with specific responsibilities. Key features include group creation and management, contributions and payments, a payout engine, trust and risk management, financial growth tools, a business support layer, notifications, and an admin dashboard. The application integrates with payment gateways and KYC verification APIs to facilitate transactions and compliance.

2a. Product Interpretation and Delivery Boundary

Ajopay is delivered as a mobile-first application with a responsive web companion for admin users. It is designed to operate in low-bandwidth environments and supports multiple languages, including English, Nigerian Pidgin, Yoruba, Igbo, and Hausa. The application ensures security through end-to-end encryption, two-factor authentication, and biometric login where supported. It integrates with regional payment gateways and KYC verification services to ensure compliance and facilitate transactions. The application does not support blockchain or smart-contract features in its current phase but may consider these in future expansions.

2b. Source Content Inventory

Not applicable as no explicit content_source directive was provided.

2c. Page Content and Component Coverage

Home

• Overview: Displays user's groups, upcoming contributions, and payouts.
• Actions: Quick access to join/create groups, view wallet, and community.
• Components: Group summary cards, contribution reminders, payout countdowns.

Groups

• Overview: List of user's groups with status and next actions.
• Actions: Create new group, manage existing groups, invite members.
• Components: Group detail view, member list, contribution status dashboard.

Wallet

• Overview: Displays current balance, transaction history, and linked accounts.
• Actions: Link new account, view transaction details, manage auto-debits.
• Components: Balance summary, transaction list, account linking interface.

Community

• Overview: Access to forums and resource hubs by business type.
• Actions: Join discussions, access business resources, share tips.
• Components: Forum threads, resource articles, business plan templates.

Profile

• Overview: User's personal information, trust score, and guarantor details.
• Actions: Edit profile, view trust score details, manage guarantor.
• Components: Profile information, trust score breakdown, guarantor management.

3. Functional Requirements

• As a Member, I should be able to join or create savings groups, contribute to the pool, receive payouts, and track my contribution history. (explicit)
• As a Group Admin/Treasurer, I should be able to create groups, set rules, manage membership, and resolve disputes. (explicit)
• As a Guarantor, I should be able to vouch for a member, and my reputation should be visible in that member's profile. (explicit)
• As a Platform Admin, I should oversee compliance, monitor disputes, and approve KYC processes. (explicit)
• As a Member, I should be able to receive automated reminders for upcoming contributions and payouts. (explicit)
• As a Group Admin, I should be able to set the payout order method, including balloting, needs-based ranking, or bidding/auction system. (explicit)
• As a Member, I should be able to access a business support layer with resources and forums specific to my business type. (explicit)
• As a User, I should be able to use the application in multiple languages, including English, Nigerian Pidgin, Yoruba, Igbo, and Hausa. (explicit)
• As a User, I should have secure access to the application through end-to-end encryption, two-factor authentication, and biometric login. (explicit)

4. User Personas

1. Member

   • Responsibilities: Join/create groups, contribute, receive payouts, track history.
   • Outcomes: Successful participation in savings groups, timely contributions, and payouts.

2. Group Admin/Treasurer

   • Responsibilities: Create groups, set rules, manage membership, resolve disputes.
   • Outcomes: Efficient group management, fair payout distribution, dispute resolution.

3. Guarantor

   • Responsibilities: Vouch for members, maintain a visible reputation.
   • Outcomes: Support trusted members, enhance group trust dynamics.

4. Platform Admin

   • Responsibilities: Oversee compliance, monitor disputes, approve KYC.
   • Outcomes: Ensure platform integrity, compliance with regulations, user trust.

5. Core User Flows

Member Joining a Group

1. Initiate: Member selects "Join Group" from the Home page.
2. Input: Member enters group code or scans QR code.
3. Verification: System verifies group details and member eligibility.
4. Confirmation: Member confirms joining, receives welcome message.
5. Outcome: Member is added to the group, visible in the Groups page.

Group Admin Creating a Group

1. Initiate: Admin selects "Create Group" from the Groups page.
2. Input: Admin enters group details (name, purpose, contribution amount, etc.).
3. Configuration: Admin sets payout order method and visibility.
4. Invite: Admin invites members via phone number, link, or QR code.
5. Outcome: Group is created, members are notified, visible in Admin's Groups page.

Member Contributing to a Group

1. Initiate: Member receives a reminder notification for contribution.
2. Action: Member selects "Contribute" from the notification or Groups page.
3. Payment: Member chooses payment method (auto-debit, manual).
4. Confirmation: System processes payment, updates contribution status.
5. Outcome: Contribution is recorded, member receives confirmation.

Platform Admin Resolving a Dispute

1. Initiate: Admin receives a dispute flag from a member.
2. Review: Admin reviews transaction audit trail and member statements.
3. Mediation: Admin mediates between involved parties.
4. Resolution: Admin decides on the resolution, updates dispute status.
5. Outcome: Dispute is resolved, parties are notified, audit trail updated.

6. Visuals Colors and Theme

• Muse: Haraldur Thorleifsson
• Palette:
  • Background: #FFFFFF
  • Surface: #F6F6F6
  • Text: #333333
  • Primary: #006D40
  • Accent: #FFD700
  • Muted: #D9D9D9
• Typography:
  • Headings: Sora — Bold, large, wide tracking
  • Body: Outfit
  • Scale: 1.25 modular, 48/32/24/16/14
• Shape Language: Chunky rounded cards with color-blocked sections
• Layout: Mobile-first with bottom tab navigation, generous spacing
• Imagery: Custom character and spot illustrations, bold iconography

7. Signature Design Concept

The public entry page features a large illustration-led hero with bold color blocks, dominated by emerald green with gold accents for buttons. The design emphasizes community themes with character illustrations representing different business types. The layout is mobile-first, with rounded cards for user actions and lively entrance animations for buttons and tabs.

8. Interaction Model & Motion Direction

• Interaction Model: Animated
• Motion Tempo: Expressive
• Hero Dimensionality: Layered_2d
• Landing Hero Motion Brief: The hero features a large illustration of a community gathering, with animated transitions highlighting different business types. The motion vocabulary includes lively entrance animations for buttons and tabs, with a reduced-motion state for accessibility.

9. Non-Functional Requirements

• Performance: The application must perform efficiently on entry-level smartphones and in low-bandwidth environments. (explicit)
• Security: End-to-end encryption, two-factor authentication, and biometric login must be implemented. (explicit)
• Compliance: The application must comply with CBN regulations for fintech operations. (explicit)
• Localization: Multi-language support must be provided, including English, Nigerian Pidgin, Yoruba, Igbo, and Hausa. (explicit)

10. Tech Stack

• Frontend: React Native for mobile, React for admin web dashboard
• Backend: Node.js/Express or NestJS, PostgreSQL for transactional data
• Payments: Paystack/Flutterwave SDKs
• Hosting: AWS or GCP with Nigeria-adjacent CDN edge nodes
• Notifications: Firebase Cloud Messaging (push), Termii (SMS/USSD)

11. Assumptions and Constraints

• The application will initially focus on the Nigerian market, with potential expansion to other African regions.
• Blockchain and smart-contract features are not included in the current phase but may be considered for future expansions.
• The application will not support deep menu nesting to maintain simplicity and accessibility.

12. Glossary

• Esusu/Ajo/Tontine/Stokvel: Traditional African rotating savings and credit systems.
• KYC: Know Your Customer, a process of verifying the identity of users.
• CBN: Central Bank of Nigeria, the regulatory authority for financial operations in Nigeria.
• BVN/NIN: Bank Verification Number/National Identification Number, used for identity verification in Nigeria.