[CLOSED] 2022 Hackathon | low-code/no-code
Last updated
Was this helpful?
Last updated
Was this helpful?
⏰ Closed:22 July 2022, 23h59 SAST
Check out the and
Hey Peeps!!!
We were blown away by all the amazing projects you built and submitted for and hope you are ready for the next one!
Starting in quarter two this year, our hackathon theme is Low-code/ No-code with (Read the origin ).
Our goal for this Hackathon is to show the power of programmable banking and how it can be made more accessible for non-tech users.
If you're keen to jump in already, .
This is a virtual community hackathon. The challenge is to create useful solutions for non-technical peeps using with .
Stay updated with the Spreadsheet Banking build and in our .
You and your team are the credited ‘owners’ of your ideas, code and content. However, in the , you are required to open source your code under the ; see Rules and FAQs for more info. You can chat with us in the dedicated or email us at .
You may participate alone, but we highly recommend working in a team.
Please note that at least one person on your team must have access to an and have Programmable Banking activated on their account () - as you need to build a solution that is integrated with it.
The closing date for your final solution is Friday 22 July, 23:59 SAST.
Each submission must include:
Your team should build a solution that uses the Spreadsheet Banking app as part of your Investec's Programmable Banking solution to show how businesses can make life easier or create efficiencies for others.
Make sure you understand the Primary Criteria (below) before coming up with ideas.
Focus on the use case - you should explain the problem you are trying to solve, how someone would use your solution and why.
Please keep it simple. If your solution saves someone 5 minutes a week - that's a meaningful impact on a real person's life!
Try to find smart workarounds if a platform limits you. Your solution doesn't need to be rolled out at scale to score well.
Ensure it works in production. For example, if you need to demonstrate a payment with a card, use SnapScan and donate R1.00 to a good cause.
Team size 1- 6 with one submission per team**.**
You can be in multiple teams - it's all about the submitted solutions.
✅ Hackathon teaser at the Meetup: Thur 21, April 222
✅ Ideation meetup: Thur 26 May @ 18h30 - Play around with an alpha version
✅ 🎉 Winners Demos: Thur 28 July
Two end-user sponsors will have Ziggy bags filled with R45k of hard-grazed cash each to invest in submitted projects and the amounts they see fit.
Each Zebra will bid and offer cash to as many submissions as they want to invest in, and each submission chosen will be granted a good faith agreement.
The participants can choose to get half the cash for just sharing the idea/ POC build with the community OR can choose to build their project out further for the other half - it’s up to them. 🤑
If the team decides to carry on building on their solution and take the full offered amount, they will have a 1:1 with the Sponsor to discuss the next steps as needed for the project.
The general Programmable Banking community will also have the opportunity to vote for their favourite solution.
The solution with the most votes will win a “Community Prize” bonus, over and above any other prizes.
All team members who submitted a complete application will receive Programmable Banking swag 🤩
You will be asked to provide the following when submitting your build:
The End-User Sponsors will be looking for a few things when considering how they will invest their hard grazed cash, including:
Quality of the idea: simplicity, creativity and originality of the idea
Potential strategic impact: potential for improving businesses
Implementation of the concept: ease of use, documentation and source code
It is up to the Investor to decide to view the submitted projects in light of each criterion. Their decisions are at their discretion.
We'll be contacting and announcing winners throughout the week after submission closes.
NB! To qualify as a winner, each team must perform a live demo of how their solution works and answer questions from the audience in a 10-minute slot at the Programmable Banking Meetup at 6:30 pm on 28 July 2022. We will let winners know by 27 July that they have won to prepare for the demo.
If no one from a winning team attends the meetup and demos their solution, that team will forfeit and will not be awarded their winnings - please carefully read “Forfeit of teams” in the Rules section.
Here's a collection of resources that will help you start building with Investec’srogrammable Banking API/ Card:
Any intellectual property developed during the hackathon will belong to the team that created it. We expect each team to agree with themselves regarding the IP, but this is not required.
By submitting, you grant OfferZen & Investec permission to use screenshots, code-snippets and links to your project or content of your submission on our Twitter, blog, website, email updates, and in OfferZen slack channels. OfferZen and Investec do not make any claims over your IP.
Prizes for teams - the full prize amount will be deposited into the selected bank account supplied by the winning team's Team Lead. Teams are responsible for dividing prizes amongst themselves.
Forfeit of teams - if a winning team does not present their solution at the Winners and Demos Meetup on 28 July 2022, winnings will be forfeited. Exceptions may be made under extenuating circumstances and at the discretion of the OfferZen Community Management team.
Disqualification - you may be disqualified and forfeit any prizes you may be eligible to receive if OfferZen or Investec reasonably believes that you have not complied with or attempted to undermine the legitimate operation of the Programmable Banking Hackathon.
Sponsors scoring - Sponsors will assess submissions completely at their discretion and are not required to provide explanations for their decisions.
and let us know in the entry form if you also require access to a live demo/ community account - rather than using your own Investec account.
Please reach out to with any questions.
You must use the in some way in your solution.
, but credit sources.
Teams must have access or a way to access the Programmable Banking API / card functionalities to leverage them for the hackathon. (You can also or .)
✅ : Thur 30 June @ 18h30 - All the deets and how to get started
✅ : Thur 30 June ( <-- START CODING)
✅ : Fri 22 July 23h59 SAST ( <-- STOP CODING)
✅ deliberation between Mon 25 - Wed 27 July
A link to an app/system solution that has been released under the and uses the Spreadsheet Banking app in some way [you can also use the and other features on ].
A brief description of how you used Spreadsheet Banking and Programmable Banking (see )
Hang out with participating teams and the if you need help/ advice when building or find other people to join your team. Join us even if you just want to chill and watch other people build!
Join the Hackathon Slack channel: .
[Docs]
[Snippets]
[Blog]
[Video]
[Miro board]
[Blog]
It is a requirement to open source your submission under the .
Things we didn’t think of - SPOILER ALERT! We are humans. The OfferZen Community Management Team will try to be fair and inclusive. We reserve the right to have the final say in unforeseen circumstances. Please email us regarding any issues: c.
You will need to get access to an account either by opening one, getting permission to access one from an account holder, or working in a team with someone who does have access. You can find out more about opening an account and accessing Programmable Banking here: P.
If you prefer access to a general community live test account, please in the Hackathon before submissions open.
OfferZen may reach out to you about publishing your solution pitch and demo on the to showcase it to the and that use OfferZen.
You can reach out to us at , and we will do our best to help you get started or answer your questions.
You own your ideas, code, and other content you create; however, it is required to open source your submission under the .
Your submission is subject to the .