Investec Developer Community Wiki
  • 🏠Home
    • Investec Developer community wiki
  • ⚒️Get Started
    • Get started overview
    • Investec Developer Docs
    • Self-enrollment guide
    • API quick start guide
      • 🔑How to create your API keys
      • 👤How to authenticate against the Investec API
      • 🏦How to get your account, balance, and transaction data
      • 💸How to make transfers and payments
    • Programmable card quick start guide
      • 🙌How to activate your programmable card
      • 🚀How to add low-code snippets to your card on Investec Online
      • 🖥️How to add code to your card and run a simulation using the online IDE
      • 💳How to use the programmable card API
    • Sample apps
  • ⚒️Get Building
    • Get building overview
    • Community GitHub
    • Community libraries & tools
    • Build tutorials & guides
      • 💳Card | Slack Integration
      • 🚗Card | How to create a DIY petrol card
      • 🎯API | No-code Budget Expense App
    • Build challenges & hackathons
      • 🎯[Closed] Q1 2025 Bounty Challenge | Path to Financial Health
      • 🎁[CLOSED] Q4 2024 Bounty Challenge | Festive API Wrappers
      • 🚂[CLOSED] Q3 2024 Bounty Challenge | Everyday Solutions
      • ☄️[CLOSED] Q2 2024 Bounty Challenge | Card Code Snippets
      • 💰[CLOSED] Bounties Playground | banking.make.dev
      • 👩‍💻👩💻 [CLOSED] Mindjoy | Kid at Heart Build Challenge
      • ⚡[CLOSED] EskomSePush Build Challenge
        • EskomSePush Build Challenge Submissions
      • 💳[CLOSED] 2022 Hackathon | low-code/no-code
        • 2022 Hackathon | low-code/no-code | Submissions
      • 💰[CLOSED] Spreadsheet Banking | Bounties
        • 👩‍💻👩💻 Spreadsheet Banking | Basic Functions
      • 🏔️[CLOSED] Q1 2023 Bounty Challenge
      • 💳[CLOSED] Q2 2023 Bounty Challenge
        • 🗺️Checklist for Bounty Hunters 🏆
        • 🚀Bounty Challenge #2: Code Snippet Showdown 🚀
      • 🍕[CLOSED] Q1 2024 Bounty Challenge | The Tutorial Quest
    • Open-source projects
  • 🙌Community
    • Get involved
    • Community champions
    • Community events
    • Community manifesto
    • Blog posts
    • Community integration pros
    • Investec Developer's QRious Puzzle Challenge
  • 💬Feedback and Support
    • Get support
    • Community FAQs
    • Feature requests
    • Submit product issues
Powered by GitBook
On this page
  • Getting the support you need
  • Level 1: Reach out on Slack
  • Level 2: Feature requests & general discussions
  • Level 3: Reporting technical issues
  • Our commitment to you
  • Why GitHub?
  • Additional resources

Was this helpful?

  1. Feedback and Support

Get support

Community support framework for Programmable Banking API and card accounts.

PreviousInvestec Developer's QRious Puzzle ChallengeNextCommunity FAQs

Last updated 5 months ago

Was this helpful?

We're all about giving our community the superpowers they need to get creative and make something awesome. We believe in keeping things open, friendly, and clear because teamwork makes the dream work, right? So, we've cooked up a super simple support system to guide you through any bumps or questions you might run into.

Getting the support you need

Level 1: Reach out on Slack

For immediate assistance and to engage with fellow community champions and Investec developers, head over to our Slack channel:

  • Slack Channel:

Here, you can ask questions, share insights, or find out if there's an existing workaround for your issue.

Level 2: Feature requests & general discussions

If you have a feature request or want to start a general discussion about the Investec API and Card, please use our GitHub discussions section:

  • GitHub Discussions:

This is the perfect place to share ideas and collaborate on potential enhancements.

Level 3: Reporting technical issues

For technical issues that require attention, you have two options:

  1. GitHub Discussions: You can add your issue to the discussions for community input.

  2. GitHub Issues: For direct technical issues that need to be reported, please use the following link:

Our commitment to you

The API team is dedicated to reviewing all outstanding issues and discussion points. We will respond to and/or assign issues to the relevant team members for resolution.

  • Resolution Time: We aim to resolve in best effort all issues within 48 hours and will communicate the outcome back to the person who raised the issue.

Why GitHub?

We chose GitHub for its openness and transparency. It allows us to:

  • Connect directly with Investec's ticketing system, ServiceNow.

  • Maintain a searchable record of resolved issues and discussions.

  • Foster a collaborative environment where everyone can contribute and benefit.

Additional resources

Thank you for being a part of our community. Together, we can build something extraordinary.

For more information on the Investec API and Card, please visit our Community FAQs page or reach out to us on .

💬
#05_pb-api-support-feedback
Investec Developer community discussions
Start a Discussion
Report an Issue
Slack