Skip to main content

Submission requirements

Please submit the following as your final hackathon entry:

1. Presentation​

A presentation (PDF or PowerPoint) covering:

  • The problem statement and opportunity
  • Research and key insights (if applicable)
  • User stories, use cases, or user journeys
  • Information architecture, user flows, system architecture, or technical diagrams (where relevant)
  • Design decisions and solution process
  • Technical implementation and technology stack
  • Key features and functionality
  • Challenges encountered and how they were overcome
  • Expected impact and future improvements

2. Recorded presentation​

A 10–15 minute recorded presentation walking the judges through your project, demonstrating your solution, and explaining your design and technical decisions.

3. Working demo, prototype, or source repository​

A working demo, prototype, or source repository, submitted as a live link for the judges to review.

4. How to submit your project​

To make the judging process as smooth as possible, each team must create a shared cloud folder (Google Drive, Dropbox, OneDrive, or a similar service) containing all of their final submission materials.

Your submission folder should include:

  • Your final presentation (PDF or PowerPoint)
  • Your 10–15 minute recorded project presentation
  • A link to your live demo, prototype, or source repository (where applicable)
  • Any supporting documentation you would like the judges to review

Submission process​

Once your submission folder is complete:

  1. Ensure that all files are organised and clearly labelled.
  2. Verify that the folder and all included files are accessible to anyone with the link.
  3. Share the folder link in your team's dedicated Slack channel before the submission deadline.

Each team will be assigned a private Slack channel at the start of the hackathon. This channel will be used for announcements, communication with the organisers, and the submission of your final project.

Please note

It is the responsibility of each team to ensure that their shared folder is accessible. Submissions that cannot be accessed by the judging panel may not be eligible for evaluation.

Remember that each project should demonstrate a meaningful connection to Interledger or Open Payments technology - see the technical requirement.

A submission template will be linked from the Technology & Resources page once it is ready.

Finalists and the Grand Finale​

The judging panel will review all submissions and select the top five teams based on the judging criteria. These finalists will be invited to present their solutions live at the in-person Grand Finale, where the winners will be announced.