> For the complete documentation index, see [llms.txt](https://investec.gitbook.io/programmable-banking-community-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/q2-2026-bounty-challenge-or-api-side-hustle.md).

# Q2 2026 Bounty Challenge | API Side Hustle

{% hint style="info" %}
These builds are created with ❤️ by our community. They are open for use, contributions, and sharing. \
Please note these repos are **not officially supported by Investec**. **Exercise caution** when engaging with community-driven projects.
{% endhint %}

### \[UPDATED 03/06/26] This bounty challenge is now closed 👀.

| Build Name      | Coder                       | Description                                                                 | Link to Repo                                                                                                      | Rating                                                                                                               |
| --------------- | --------------------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Qualis          | Bandile                     | SME payment intelligence that flags late payments and cash-flow risk.       | [GitHub Repository](https://github.com/bandilleee/qualis)                                                         | 5/5 — Strong commercial use case; very bounty-aligned.                                                               |
| FIN-GATE        | Kimberley Bezuidenhout      | Real-time financial rules engine for risk, spend control and approvals.     | [GitHub Repository](https://github.com/Kimmicorn-glitch/FIN-GATE)                                                 | 5/5 — Practical, programmable, and monetisable.                                                                      |
| PayGuard        | Innocent Jackson            | Approval workflow for high-risk payments before money moves.                | [GitHub Repository](https://github.com/STHB2025/payguard-family-approval)                                         | 5/5 — Clear real-world problem; strong safety and trust angle.                                                       |
| TshepoVault     | Lehlohonolo Sehako          | Bank-backed proof of income without sharing full bank statements.           | [GitHub Repository](https://github.com/Lehlohonolo-Sehako/tshepo-vault)                                           | 4.5/5 — Strong privacy use case; highly relevant local problem.                                                      |
| Investec Runway | Sean Gordon                 | Private finance dashboard that predicts runway and answers money questions. | [GitHub Repository](https://github.com/sean-gordon/investec_runway)                                               | 4.5/5 — Clear user pain and strong API use.                                                                          |
| Investec-AI-SDK | Happy Mahlangu              | TypeScript SDK for AI-native banking features using Investec APIs.          | [GitHub Repository](https://github.com/HappyDevs1/investec-ai) · [npm](https://www.npmjs.com/package/investec-ai) | 4.5/5 — Excellent dev-enablement angle; slightly more platform than direct side hustle.                              |
| ZentaraApp      | Mahlatse Charmaine Sekulane | Income intelligence for freelancers and side hustlers.                      | [GitHub Repository](https://github.com/charmainesekulane232/ZENTARAAPP-.git)                                      | 4/5 — Good target market and fit; needs proof of product depth.                                                      |
| GigGuard        | Nevin Tom                   | Income smoothing and spend control for gig workers and fleets.              | [GitHub Repository](https://github.com/Nevvyboi/GigGuard)                                                         | 4.5/5 — Strong real-world use case; great use of programmable banking beyond tracking with clear platform potential. |

***

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](https://investec-dev-com.slack.com/archives/C05MNBE2G3C)

**📍Submit your final build:** [Submission Form →](https://forms.office.com/r/CL3D9fJMaD) 

***

### 🛠️ 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.

| Path                   | What it means                                                                       | Example ideas                                                                                             |
| ---------------------- | ----------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| 💼 **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

| Question                                 | Answer                                                                                    |
| ---------------------------------------- | ----------------------------------------------------------------------------------------- |
| **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

| 🧾 Requirement      | ✔️ What to Do                                                                      |
| ------------------- | ---------------------------------------------------------------------------------- |
| **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? <a href="#need-help" id="need-help"></a>

* Ask anything in [#bounties](https://investec-dev-com.slack.com/archives/C05MNBE2G3C)
* Pair up with another dev
* Chat with a **Community Champion** for guidance or reviews

***

{% hint style="success" %}

#### **🧯 A Few Friendly Guardrails**

**Please:**

* start in [**Sandbox**](https://github.com/Investec-Developer-Community/Community-Projects?tab=readme-ov-file#-sandboxes--local-development) 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.`
> {% endhint %}

***

### 👋 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.