💵Q2 2026 Bounty Challenge | API Side Hustle
Build something people would actually pay for.
Not just a cool demo. Not just “look, it returns JSON.” Build something with a real use case, a real customer, and a real reason to exist.
This bounty is all about API monetisation using Investec Programmable Banking.
Keep it practical, make it weird, or land somewhere in the middle.
👀 TL;DR
📅 Duration: 2 April – 2 June 2026
🖐 Who: Anyone in the Investec Developer Community
🏁 Goal: Create something with a clear use case and monetisation angle using Investec Programmable Banking
💬 Join the chat ask questions: #bounties Slack Channel
📍Submit your final build: Submission Form →
🛠️ The Challenge
Build something that:
solves a real problem
has a clear user or customer
has a believable monetisation angle
uses Investec Programmable Banking in a meaningful way
That’s it.
It can be:
practical
unexpected
playful
or all three
Think useful first. Fancy second.
🚦 Build Paths
There’s no single right way to do this.
💼 Practical
Build something useful with a clear customer, problem, and monetisation angle
Fraud alerts, subscription tracking, SME cash flow tools, family approval flows
🤪 Wild but Useful
Build something unexpected, fun, or slightly ridiculous, but still genuinely useful
Smart mirror money briefings, voice assistants, games, quirky card-powered experiences
🔀 Hybrid
Mix both worlds: a solid product idea with a creative delivery or interface
A monetised product wrapped in a game, a card-powered savings experience, a weird-but-viable fintech tool
🔌 What You Can Build With
You can use:
Investec API
Programmable Banking cards
or any combination of the above
🚦 Before You Start
Who can join?
Anyone in the Investec Developer Community
Solo or team?
Either is fine
Sandbox-only builds?
Yes
Does it need to be production-ready?
No
New or existing projects?
Either, as long as you clearly show what you built for this bounty
What counts as meaningful use?
Investec Programmable Banking should be a real part of the build, not just added for show
What makes a submission valid?
A repo, README, and a build that aligns with the bounty theme
✅ What Counts
To qualify, your build should:
align with the API Side Hustle theme
use Investec Programmable Banking in a meaningful way
solve a real problem or explore a genuinely useful idea
include a clear use case and who it’s for
show how someone might pay for it, use it, or benefit from it
include the required submission items
You do not need a polished startup, a production launch, or a perfect UI.
A solid idea, a working build, and a clear explanation are enough.
🎁 Rewards
Everyone who submits a valid build that aligns with the theme, goals, and spirit of the bounty will receive:
👕 Exclusive Investec Dev Swag
🚀 Shoutout in the Community Newsletter
🏆 Community bragging rights
A few standout builds will also get a little extra 😉 Think featured spots, extra visibility, more swag, and some added love from the community team.
📦 Submission Guidelines
GitHub Repo
Share your working code via a public repo
README
Include setup instructions and explain how your solution works
License
Must be MIT Licensed
Demo (Optional)
Screenshots, videos, or GIFs are welcome
Knowledge File
Add a ./knowledge file with tips, gotchas, or learnings (optional but awesome)
🙋 Need Help?
Ask anything in #bounties
Pair up with another dev
Chat with a Community Champion for guidance or reviews
🧯 A Few Friendly Guardrails
Please:
start in Sandbox for anything that moves money
be clear about what your build does and does not do
avoid financial advice claims
handle privacy and permissions properly
add sensible checks if your build triggers actions
if you use AI, explain what it does and where a human should still be involved
In short:
Be clever. Don’t be reckless.
👋 Final Word
This doesn’t need to be the next unicorn.
It just needs to be something that makes another developer say:
“I’d actually use that, and put money on the table.”
Happy building.
Last updated