🏔️[CLOSED] Q1 2023 Bounty Challenge

What's it all about?

Are you ready for your next challenge? We are excited to announce a new community bounty challenge using Programmable Banking APIs and Cards!

• Explore and build innovative solutions using the Programmable Banking API and Card.

• Spark your creativity, collaborate and share with the community

• Showcase your skills and win rewards.

What do I need to know?

The challenges are designed to be short and fun, something you can build on weekends, by yourself or working with friends (give Nick a shout if you're looking for a new buddy 🤗). There are three different challenges in total, each running for two weekends:

• ✊ Challenge 1: Linking Things | Friday 24 Feb - Monday 6 March 2023

• ✊ Challenge 2: Build Something Simple | Friday 10 March - Wednesday 22 March 2023

• 👉 Challenge 3: Building for a Social Good | Friday 24 March - Monday 3 April 2023

The challenges are open to developers of all skill levels and backgrounds. You can participate as an individual or as a team.

Your final bounty builds can be submitted here by the deadlines indicated above.

What are the challenges?

Challenge	Description	Things to consider
Linking Things	Integrate the Programmable Banking API and/or Card into an existing product or service.	Level of integration and impact on user experience.
Build Something Simple	Create and share a simple code snippet or connector for Programmable Banking API and/or Card.	Level of integration and impact on user experience.
Building for a Social Good	Build a solution that uses the Programmable Banking API and/or Card for social good.	Level of impact, originality and feasibility.

All submissions must have the minimum of documentation on; what it is, how it works and how to install it. As well as a link to the code demonstrating the build. Some challenges might have additional requirements - so watch out for them 😉

A few example projects for each challenge to ponder 🤔

Challenge	Build Examples
Linking Things	Integrate the Programmable Banking Card with a gym membership app to allow users to pay for their memberships and track their progress in one convenient place. A Community Example: Sync transactions to YNAB
Build Something Simple	Create a simple connector for Programmable Banking to another system. I.e. Connecting Programmable Banking to an Azure/ AWS/ Google Cloud instance. Community Examples: - Ruby Gem and Wrapper - Python CLI - Investec Bank GraphQL - Investec to Sage One - ynab-sync Or if you want to create something more fun: - Create an emotional connection to your spending habits.
Building for a Social Good	Build a crowdfunding platform that uses the Programmable Banking Card or API to allow people to donate to social causes and track the impact of their donations. Example: Putco Ticket System with Investec cards

💡 Note: Participants can choose to use either the Programmable Banking API, the Programmable Banking Card, or both in their submissions for each challenge.

What do I get - a part from some serious community 💟💟💟, of course?

If you meet the submission requirements, you'll be eligible to receive one of our awesome swag items. So make sure to submit your entry and claim your prize! 🤩

How do I get started?

1️⃣ To get started, simply let us know you’re in for the bounty challenge on our Bounties Slack Channel with an “I’m In!”.

Just type this in the Bounties chanel and you'll be in like MacGruber.

2️⃣ If you have any questions, need any build support or are just looking to have build buddies to chat with - ping us in the Bounties Slack channel and an awesome champ will be happy to jump in.

😜 Don’t worry, having issues is good! We are actually more interested in things that don’t work than things that do. 🤫

3️⃣Submit your final builds for each challenge by its due date via this submission form.

Where do I get support?

• In the Bounty Slack channel, you can connect with other participants, ask questions, and share ideas.

• We'll also explain the details of the bounty challenges and the criteria for winning rewards in that channel.

💡 ProTip: If you learn something interesting while building, be sure to add it in a ./knowledge file to your build submissions, so everyone can benefit!

What are the submission criteria?

Great question!

• We recommend using GitHub to share your code with the community.

• You can create a public repository and share the link with us via this submission form.

• This will give us easy access to your project, and it will allow other members of the community to review and comment on your work. 🥳

We will also be providing more detailed instructions on how to submit your projects closer to the submission deadline.

We hope this helps! If you have any more questions or concerns, please don't hesitate to reach out on our community Slack channel.

FAQs:

Q: Can I participate in more than one challenge?

A: Yes! You are welcome to participate in all three challenges.\

Q: Do I need to have a team to participate?

A: No, you can participate as an individual or as a team.\

Q: Can I submit an existing project for the bounty challenge?

A: Yes, you can update and clean up any existing build you might have worked on or shared before. \

Q: Do I need to be an expert in Programmable Banking to participate?

A: No, the challenges are open to developers of all skill levels and backgrounds. And we are here to support and help you!\

Q: Will I need to do a demo on this?

A: We would love it if you can! Your project will be added to a list of awesome things built by the community, and we might use it in some marketing materials and use cases. \

Q: Who owns the solution?

A: You and your team are the credited ‘owners’ of your ideas, code, and content. However, in the spirit of the community, you are required to open-source your code under the MIT License.\

We hope you're excited about this new challenge! We can't wait to see what you come up with. If you have any questions, don't hesitate to ask on our community Slack Channel. Let's build for the future with Programmable Banking!