# Q2 2024 Bounty Challenge | Card Code Snippets
### \[UPDATED] We had six amazing submissions. Check them out below:
| Name | Coders | Description | Link |
| --------------------- | --------------------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Swipe 'n Save | Peter Smythe | Demo code integrating the Private Banking API (OAuth2) with the Card API. | [GitHub Repository](https://github.com/petersmythe/investec-swipe-n-save), [Documentation](https://github.com/petersmythe/investec-swipe-n-save/blob/main/README.md) |
| CarbonCooler | Amery Winter & Peter Smythe | Tracks carbon footprint of fuel purchases and invests in carbon offset initiatives. | [GitHub Repository](https://github.com/Brodreger/CarbonCooler), [Documentation](https://github.com/Brodreger/CarbonCooler/blob/main/README.md) |
| Virtual Card Fortress | Peter Smythe | Shifts recurring subscription payments to a separate virtual credit card with a configurable shield. | [GitHub Repository](https://github.com/petersmythe/investec-virtual-card-fortress), [Documentation](https://github.com/petersmythe/investec-virtual-card-fortress?tab=readme-ov-file) |
| Payment Pinger 💸 | Roberto Aldera | Posts payment details to Telegram for card payments and includes anomaly detection for non-ZAR transactions. | [GitHub Repository](https://github.com/roberto-aldera/card-payment-notifier), [Documentation](https://github.com/roberto-aldera/card-payment-notifier) |
| Teleidop | Matt van Niekerk | Uses Investec's Programmable Card feature to send transaction notifications via Telegram. | [GitHub Repository](https://github.com/mattvanniekerk/teleidop/), [Documentation](https://github.com/mattvanniekerk/teleidop/blob/main/README.md) |
| Card To Sheet Sync | Dominic Santo | Sends card transactions to a Google Sheets document. | [GitHub Repository](https://github.com/dominicsanto/card-to-sheet-sync), [Documentation](https://github.com/dominicsanto/card-to-sheet-sync/blob/main/README.md) |
***
Get ready to flex your coding muscles once again! We're thrilled to announce the Q2 2024 Bounty Challenge, inviting developers to create innovative card code snippets that could be featured on the Low-code screens of the Investec banking portal.
{% hint style="info" %}
This is your chance to contribute to the community, showcase your skills, \
and earn some cool Investec Developer swag!
{% endhint %}
## What's the Challenge?
### Card Code Snippet Creation
**Objective:** Craft and share a code snippet that demonstrates the potential and use of Programmable Banking card integration.
{% hint style="info" %}
**Inspo**: [Card | Slack Integration](/programmable-banking-community-wiki/get-building/build-something-simple/card-or-slack-integration.md) or [Card | How to create a DIY petrol card](/programmable-banking-community-wiki/get-building/build-something-simple/card-or-how-to-create-a-diy-petrol-card.md)
{% endhint %}
#### **Considerations:**
* Identify a practical problem that your code snippet can address.
* Aim for innovation and creativity in your approach.
* Ensure your code is efficient, effective, and user-friendly.
#### Challenge Details
* **Start Date:** The challenge kicks off at the beginning of 1 May 2024.
* **End Date:** Submissions must be in by 30 June 2024.
* **Who Can Participate:** Open to all developers, regardless of skill level. Participate solo or as a team.
* **Submission Link:** [Submit your code snippet here](https://jf18emj1p49.typeform.com/to/ayGjRdGw) before the deadline to qualify for rewards.
## Rewards
* **Swag for All:** Every participant who submits a snippet will receive an Investec Developer swag shirt.
* **Top Picks:** The best two snippets, *as chosen by the API team*, will be featured on the Low-code screens on the Investec banking portal.
Possable swag rewards
## How to Participate
1. **Declare Your Participation:** Jump into our [Bounties Slack Channel](https://investec-dev-com.slack.com/archives/C05MNBE2G3C) and announce your entry with an "**I'm In!**"
2. **Need Help or Company?** If you have questions or want to collaborate, reach out in the [Bounties Slack channel](https://investec-dev-com.slack.com/archives/C05MNBE2G3C). Our community champions are ready to assist.
3. **Submit Your Snippet:** Use the [submission form](https://jf18emj1p49.typeform.com/to/ayGjRdGw) to send in your work by the end of Q2 2024.
## Support and Collaboration
* **Bounty Slack Channel:** Connect, discuss, and brainstorm with fellow participants and the Investec team in the [#bounties channel here](https://investec-dev-com.slack.com/archives/C05MNBE2G3C).
* **Knowledge Sharing:** If you discover something cool, add it to a `./knowledge` file with your submission to benefit the community.
## Submission Guidelines
* **GitHub Repositories:** Share your code via a public GitHub repository and submit the link through our form.
* **Documentation:** Include a README with an explanation of your snippet, how it works, and installation instructions.
* **Licensing:** All submissions should be open-sourced under the MIT License.
## FAQs
* **Multiple Challenges:** Feel free to participate in multiple challenges.
* **Team Participation:** Go solo or team up – it's your choice.
* **Existing Projects:** You can refine and submit projects you've previously worked on.
* **Skill Level:** All developers are welcome, and we're here to help you succeed.
* **Demos:** While not mandatory, we'd love to see demos of your projects.
* **Ownership:** You retain ownership of your ideas and code, but we ask that you share it with the community under the MIT License.
## Ready to Code?
Let's make Q2 2024 a season of innovation and collaboration. Declare your participation by saying "I'm in!" in the [#bounties channel on Slack](https://investec-dev-com.slack.com/archives/C05MNBE2G3C), and let's create something incredible together!
---
# Agent Instructions: 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-2024-bounty-challenge-or-card-code-snippets.md?ask=
```
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.