> 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-2025-bounty-challenge-or-every-day-money-hack.md).

# Q2 2025 Bounty Challenge | Every‑Day Money Hack

### \[UPDATED 08/07/25] This bounty challenge is now closed 👀.

{% hint style="danger" %}
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 %}

| Build Name | Coder        | Description                                                                                     | Link to Repo                                               |
| ---------- | ------------ | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| SweepPay   | Amery Winter | Automates monthly wage calculations and payments for employees like housekeepers and gardeners. | [GitHub Repository](https://github.com/Brodreger/SweepPay) |

***

Welcome to our **June 2025 community bounty**! Ship a bite‑sized automation or integration that *automatically* saves at least **5 minutes or R50 per month** for you (or someone else) using the **Investec Programmable Banking API**.

> **Low‑Ops Promise 🚀** — all you need to do is build, demo, and drop the link. No badge systems, no complex scoring; just share your progress in Slack and earn swag.

***

### Quick Facts

|                        | Detail                                                                                                                                               |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Kick‑off**           | **2 June 2025**                                                                                                                                      |
| **Deadline**           | **30 June 2025 – 23:59 SAST**                                                                                                                        |
| **Discussion Channel** | [#04\_community-bounties](https://investec-dev-com.slack.com/archives/C05MNBE2G3C) on Slack – start a thread for your build                          |
| **How to Submit**      | Post a public GitHub repo link **+** short Loom/YouTube/GIF demo to the [Bounty submission form](https://forms.office.com/r/CL3D9fJMaD).             |
| **Who Can Join**       | Any skill level, solo or team                                                                                                                        |
| **Rewards**            | <p>• Swag for <em>every</em> valid submission</p><p>• <strong>Top 3 “Most Helpful” hacks</strong> spotlighted in the community newsletter & wiki</p> |

***

### 1 · Objective

> **Build something small that makes money matters easier.**
>
> • ≤ 500 lines of code **or** ≤ 10 Zapier / Make.com steps\
> • Uses at least **one** Investec API or webhook endpoint\
> • Demonstrates a *clear* time‑ or cost‑saving benefit (≈ 5 minutes ➜ R50 per month)

***

### 2 · What Counts as a “Money Hack”? 💡

Here are four sample ideas - feel free to riff!

| Idea                              | Core Endpoint(s)                             | Impact                                                   |
| --------------------------------- | -------------------------------------------- | -------------------------------------------------------- |
| **Round‑up Auto‑Saver**           | `/za/pb/v1/cards/transactions`, `/transfers` | Sneak R5 into a Savings Pocket on every swipe ≥ R100     |
| **Duplicate‑Debit Alert**         | `/transactions`                              | DM me when identical merchant debits occur within 7 days |
| **Load‑Shedding Fuel Pocket**     | Webhook + EskomSePush API                    | Move R50 to a “Generator Fuel” pocket at Stage 4+        |
| **Low‑Balance Early‑Warning SMS** | `/balance`, webhook                          | SMS if tomorrow’s projected balance drops below R200     |

***

### 3 · Getting Started Kit 🔧

1. **API Quick‑Start & Sandbox Keys**\
   → [API quick start guide](/programmable-banking-community-wiki/get-started/api-quick-start-guide.md)
2. **Past Builds Gallery**\
   → [Past community projects](https://github.com/Investec-Developer-Community/Community-Projects)

```
# .env.example (don’t commit real keys!)
INVESTEC_API_KEY=YOUR_KEY
INVESTEC_API_SECRET=YOUR_SECRET
```

***

## 4 · How to Get Involved ✅

{% stepper %}
{% step %}
**Jump In:**

Head over to our[ Bounties Slack Channel](https://investec-dev-com.slack.com/archives/C05MNBE2G3C) and shout "**I'm In!**" to let us know you're participating.
{% endstep %}

{% step %}
**Need a Hand?**

Our community champions are ready to help in the [Slack channel](https://investec-dev-com.slack.com/archives/C05MNBE2G3C) if you have questions or want to team up.
{% endstep %}

{% step %}
**Submit Your Work:**

Share your solution via a public GitHub repository, under an MIT licence, and [submit the link](https://forms.office.com/r/CL3D9fJMaD) through our form by the deadline. Don't forget to include a short video (≤ 2 min) or GIF showing the automation in action.
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
**Environment Security**: Store Investec credentials in `.env`; never commit secrets.
{% endhint %}

***

### 5 · Judging & Rewards 🎁

| **Tier**                  | **Criteria**                              | **Reward**                                  |
| ------------------------- | ----------------------------------------- | ------------------------------------------- |
| **All Valid Submissions** | Passes checklist                          | Exclusive Investec socks and T‑shirt        |
| **Top 3 Most Helpful**    | Panel vote: *utility, creativity, polish* | Newsletter spotlight + Official GitHub repo |

> \*Panel review date: \****1 July 2025***\
> Winners announced in Slack & newsletter on **7 July 2025**.

***

### 6 · FAQ 🤔

**Q: Can I re‑use code from previous bounties?**\
A: Absolutely — remix, extend, or polish any prior work as long as this entry meets the checklist.

**Q: Do I have to host it live?**\
A: No. A short recorded demo proving it works is enough.

**Q: Is there a language/framework restriction?**\
A: Any stack is welcome — Node, Python, Go, Zapier, etc.

***

### 7 · Helpful Links

* 🔑 [Investec API Docs](https://developer.investec.com/za/api-products)
* 🎓 [API quick start guide](/programmable-banking-community-wiki/get-started/api-quick-start-guide.md)
* 💬 [Bounty Hunters Slack channel](https://investec-dev-com.slack.com/archives/C05MNBE2G3C)

***

> **Ready?** Spin up your favourite editor, give us a 🙋 in [#04\_community-bounties](https://investec-dev-com.slack.com/archives/C05MNBE2G3C), and start hacking. We can’t wait to see how you save the world (or at least R50/month)! 🚀


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events/q2-2025-bounty-challenge-or-every-day-money-hack.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
