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
  • The challenge
  • Step 1: Join #rooty on Investec Developer Community Slack
  • Step 2: Open Investec Programmable Banking
  • Step 3: Select the card you want to code
  • Step 4: Setup your main.js file
  • Step 5: Setup your env.json file and add your Slack ID
  • Step 6: Simulate a transaction in the programmable banking app!
  • Step 7: Celebrate when you see your notification on the Investec Developer Community Slack \o/
  • NB Step 8: Delete/edit your code

Was this helpful?

  1. Get Building
  2. Build tutorials & guides

Card | Slack Integration

PreviousBuild tutorials & guidesNextCard | How to create a DIY petrol card

Last updated 4 months ago

Was this helpful?

Purpose of this tutorial

This tutorial is meant to help you achieve 2 things as quickly as possible so that you can grasp the absolute basics of Investec’s Programmable Banking feature:

  1. Join OfferZen Community so that you can send a message to an external system

  2. Send a message to Slack from Investec Programmable Banking when you simulate a transaction to get a feel for how it works

The challenge

Step 1: Join on Investec Developer Community Slack

Step 2: Open Investec Programmable Banking

Log in to your online banking and select the Investec Developer option, under the Manage tab.

Step 3: Select the card you want to code

ProTip: You can enable and disable the code on each card using the toggle below the cards.

  • You can also use the mobile app to do that by tapping on your account, then on cards, and there you will see a toggle for programmable banking.

  • 💡 Often people forget they added code that blocks transactions, and their card is declined at the shops and they call the call centre - so if your card declines at the shop, remember that you can disable your code from the mobile app.

Step 4: Setup your main.js file

ProTip: Transaction log history

  • On the right-hand side, near the top of the screen, you will see “Event logs” you can click on that to get a history of transactions that you made with code enabled and the logs of those transactions - you can click on it to see this.

  • You will notice you have simulator logs and production logs.

  • Simulation transactions are fake transactions like the one we just ran, which you can use for testing.

  • Production transactions are the real transactions you make when you use your card.

Step 5: Setup your env.json file and add your Slack ID

Get your Slack ID from the Investec Developer Community Slack:

Step 6: Simulate a transaction in the programmable banking app!

Step 7: Celebrate when you see your notification on the Investec Developer Community Slack \o/

NB Step 8: Delete/edit your code

Replace all the code in your main.js file in the editor . Make sure you Deploy code to card when you're done.

Now replace all the code in your env.json file in the editor, and replace YOUR_SLACK_ID_HERE with your actual Slack ID. Deploy your code to card when you're done:

This code is now live on your card. Please make sure you clear it out or delete it to ensure that your live transactions aren't posted into .

⚒️
💳
with this code
with this code
#rooty
Slack
#rooty
Example feed :)