Search

eSewa x WWF Hackathon 2026: Submission Guidelines

eSewa x WWF Hackathon 2026: Submission Guidelines

 

  1. Overview

Welcome to the Hackathon! Participants are invited to build innovative solutions addressing the defined problem statements. This document outlines the submission requirements, format, and evaluation criteria.

  1. Challenges

Participants must choose one of the following challenges:

Challenge 1: Develop an AI/ML solution that automatically detects and identifies images with wildlife species and without any species

Build an AI/ML solution that can automatically process and analyze large volumes of camera trap images to differentiate between images containing wildlife and those without any species. The system should reduce manual effort by filtering irrelevant images (e.g., leaves, shadows) and, if possible, identify the type of wildlife present.

Challenge 2: Real-Time KYC Document Quality Detection

Build a real-time system that detects issues like blur, glare, and improper framing while users capture identity documents, ensuring high-quality submissions from the start. The goal is to reduce repeated uploads and accelerate KYC verification.

Challenge 3: Adaptive KYC Flow Based on User Type

Design a dynamic onboarding experience that adapts KYC requirements based on different user types such as domestic users, NRAs, foreign nationals, and others. The aim is to simplify onboarding and reduce confusion across diverse user groups.

Challenge 4: Intelligent KYC Experience - Smart Form Assistance and Support Ticket Reduction

Create an intelligent KYC journey that simplifies form filling, minimizes user errors, and clearly communicates verification progress. The focus is on improving user experience while reducing support queries and onboarding friction.

Challenge 5: Detecting and Preventing Fraudulent KYC Submissions

Develop a system to identify forged documents, duplicate identities, and suspicious onboarding behavior before account approval. The goal is to strengthen platform security without increasing friction for legitimate users.

Challenge 6: Risk-Based Security for MPIN Reset

Design a risk-based authentication system that evaluates context and behavior during MPIN reset requests. The solution should dynamically apply additional verification to prevent account takeovers while maintaining a smooth user experience.

Challenge 7: Context-Aware OTP Security Warnings

Build a dynamic OTP warning system that adapts messaging based on risk context and user behavior. The objective is to prevent OTP sharing by making security alerts more relevant and effective.

Challenge 8: Authentication Anomaly Detection

Create a system that detects unusual login patterns such as device changes, rapid attempts, or location anomalies. The goal is to identify potential account takeover attempts early and trigger protective actions.

Challenge 9: Interactive Scam Awareness and Simulation

Design an interactive system that educates users on fraud and scam patterns through simulations and real-world scenarios. The aim is to improve user awareness and reduce susceptibility to social engineering attacks.

Challenge 10: Enabling Smart Group Expense Management for Shared Financial Activities

Build a social expense management system that enables users to connect, split bills, track balances, and settle payments seamlessly within the platform. The focus is on simplifying shared financial activities and increasing engagement.

Challenge 11: Intelligent Payment Scheduling and Recurring Payment Automation

Develop a system that allows users to schedule recurring payments, receive reminders, and automate regular transactions. The goal is to help users manage financial obligations while reducing missed payments.

Challenge 12: Develop an early warning system that detects animal movement using sensors, processes data and sends timely alerts to local communities via SMS, mobile apps, sirens, or other accessible technologies

Develop a real-time early warning system that detects animal movement using inputs such as camera traps, motion sensors, acoustic sensors, or drones. The system should process the data and send timely alerts to nearby communities and authorities through accessible channels like SMS, mobile apps, or sirens, enabling preventive action and improving safety.

 

📌 Note: Each team can submit only one solution for one problem statement.

  1. Eligibility Criteria
  • Open to: Bachelor and Master’s Students, Working Professionals (1 - 3 years experience only)
  • Team size: 4 members
  • Cross-functional teams are encouraged
  1. Mandatory Technology Stack

Participants must use (or align closely with) the following stack:

🔹 Frontend

  • Web: React.js / Next.js / AngularJS
  • Mobile (optional): Flutter / Kotlin / React Native / Swift

🔹 Backend

  • Node.js (Express.js / NestJS)
  • PHP, JAVA, Python

🔹 Database (optional)

  • PostgreSQL / MongoDB

🔹 AI / ML (for applicable challenges)

  • Python (TensorFlow / PyTorch / OpenCV)

🔹 Cloud / Deployment (optional)

  • AWS / GCP / Azure / Firebase (or local simulation if needed)

🔹 Version Control (mandatory)

  • GitHub / Gitlab / Bitbucket
  1. Submission Requirements

Each team must submit the following:

    1. Solution Deck (Mandatory)

A presentation (PDF/PPT) covering:

  1. Problem Understanding
    • What challenge/problem are you solving?
    • Why do you think it is important?
  2. Proposed Solution
    • Overview of your idea
    • Key features
  3. In-Scope & Out-Scope
    • What aspects solution will cover
    • What the solution will not cover
  4. User Journey / Flow
    • End-to-end experience
    • (Diagram preferred)
  5. Technology Stack
    • Tools, frameworks, APIs to be used
  6. Architecture Diagram
    • High-level
  7. Wireframes or UI/UX Designs
    • Sketches or high-fidelity designs that illustrate the user experience.
    1. Working Prototype (Optional)
  • Hosted on GitHub
  • Must include:
    • Clean, structured code
    • README with setup instructions
    • Tech stack justification (if extended)
    1. Demo Video (Good to Have)
  • Duration: 3–5 minutes
  • Must include:
    • Problem explanation
    • Solution walkthrough
    1. Submission Form Details

Each team must provide:

  • Team Name
  • Team Members (Name, Email, Role)
  • Selected Challenge
  • Solution Summary (max 200 words)
  • PDF/PPT
  • GitHub / Product Link (optional)
  • Demo Video Link (optional)
  1. Submission Format
  • Deck: PDF (Max 15 slides recommended)
  • Video: YouTube / Drive (public access)
  • Code: GitHub / GitLab
  • File naming convention:
    • TeamName_ChallengeName_Submission
  1. Evaluation Criteria

Submissions will be evaluated based on:

Criteria

Weightage

Problem Understanding

10%

Innovation & Creativity

20%

Technical Implementation

25%

User Experience (UX/UI)

20%

Scalability & Feasibility

15%

Demo & Presentation

10%

 

  1. Timeline
  • Registration Deadline: 28th March 2026 – 28th April 2026
  • Hackathon Start: 3rd June 2026
  • Idea Submission Deadline: 28th April 2026
  • Evaluation: 28th March – 2nd June 2026
  • Final Pitch / Demo Day: [Date]
  1. Rules & Guidelines
  • Plagiarism will lead to disqualification
  • Teams must build solutions during the hackathon period
  • Pre-built modules/libraries are allowed, but core logic must be original
  • Judges’ decision will be final
  1. Registeration Link

Register via:

👉 [Insert Registration Link]

  1. Submission Link

Submit your project here:

👉 [Insert Submission Link]

  1. Support & Queries

For any questions, contact:

  • Email: [Insert Email]
  • Discord/Slack: [Insert Link]
  1. Bonus for Participants
  • Focus on real-world impact
  • Keep your solution simple but scalable
  • Show a working demo, even if basic
  • Clearly communicate your idea