πŸ’³[CLOSED] Q2 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 the Programmable Banking Cards!

  • Explore and build solutions that leverage the power of the Programmable Banking Card to create new payment experiences and business models.

  • Spark your creativity, collaborate and share with the community.

  • Showcase your skills and win rewards.

Check out the Card Quick Start Guide, to get up and running quickly. β˜„οΈ

What do I need to know?

  • ✊ Code Snippet Challenge | Tue 2 May -Mon 29 May 2023 23h59 SAST

  • ✊ Code Snippet Showdown | Mon 5 June - Mon 26 June 2023 23h59 SAST

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

View Winning Submissions Here

Your final bounty challenges can be submitted here anytime before the deadlines indicated above - and we'll ship off your swag!

What is the challenge?

πŸ’‘ Note: Participants must use the Programmable Banking Card, but can also include the Programmable Banking API in some fashion if they wish in their submissions for each challenge.

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!”.

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.

A few possible real-life use cases for Programmable Banking cards.

  1. Security Alerts: Create a solution that sends an alert to your mobile device or email whenever there's unusual activity, like large purchases, or foreign transactions. This could be a great way to enhance the security of your card and catch any fraudulent activity quickly.

  2. Budget Management: You could build a feature that helps manage your budget by setting spending limits on specific categories (like dining out, online shopping, etc.). The card could be programmed to decline transactions once you've hit your budget for that category, helping you stay within your financial goals.

  3. Parental Controls: Parents could control their children's spending by setting limits or approving certain types of purchases. For example, allowing only educational or necessary expenses, limiting spend on entertainment, or setting a daily or weekly spending limit.

  4. Business Expense Management: For those using their card for business expenses, creating a solution to automatically tag and categorise purchases for easy expense reporting could be a real-time-saver. For example, all purchases at office supply stores could be automatically tagged as "office supplies" for easy sorting and reporting later.

  5. Sustainable Spending: Create a solution that helps you align your spending with your values. For example, the card could decline transactions from businesses that don't align with your chosen sustainability criteria, or alert you when you're making a purchase at a business that exceeds your carbon footprint limit.

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.\

Are you ready to show off your coding skills and create something amazing with the Programmable Banking Card? Join our Q2 2023 Bounty Challenge now by saying "I'm in!" in the #bounties channel on Slack. Let's build together and have some fun!

Last updated