Urgent.News

What's breaking now, across thousands of outlets.

Tech

Interswitch Credentials, Portals and Environments - the test and live cheat sheet

Most failed first calls to Interswitch aren't code bugs. They're often caused by a test key being sent to a live endpoint, a token generated from the wrong Passport host, or a terminal ID that only exists in the sandbox environment. These configuration mix-ups can be frustrating, especially when your implementation looks correct. This guide brings together where to find your Interswitch…

Interswitch credentials can be obtained from various platforms based on the service being integrated. A common source of confusion is using credentials from the wrong platform, assuming they will work for another service. Credentials are issued during onboarding, typically through emails containing Quickteller Business, Merchant Wallets, Payouts, webhooks, and API Marketplace information.

When integrating with Interswitch products, developers must be aware of the test and live environments for each service. The credentials and endpoints differ depending on whether the application is in test or live mode. For example, Quickteller Business provides separate test and live keys, while the IMTO credentials are available at a specific URL for test mode and after go-live.

Tokens are generated using Passport hosts, with different endpoints for test and live modes. Older documentation and Postman collections may contain incorrect Passport URLs, leading to authentication issues. Developers should use the dedicated Passport hosts to avoid such problems.

Token lifetimes vary by product, with payment gateway tokens lasting 86,400 seconds, VAS tokens for 43,199 seconds, and IMTO tokens for 39,999 seconds. Developers should cache tokens and refresh them before expiration rather than generating new tokens for every API request. Inspecting claims within the access token, such as the aud claim, merchant code, terminal ID, and environment, can help identify issues and ensure proper provisioning.

Finally, the table provided in the source material summarizes the test credentials, endpoints, and live configurations for various Interswitch services, making it easier for developers to navigate and implement the correct configurations.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The count that refused to say zero

A delivery report counts the times a new build became live while a worker was still pointing at the old build. That number matters: a rising count is the trigger to roll the delivery mechanism back.

From a database to a YouTube Short with Pillow and ffmpeg (no video editor)

Every night our server writes a plain-language post about the day's data and turns it into a short vertical video for YouTube Shorts, Instagram Reels and Facebook.

  • Python Pillow creates vertical slides with bold text
  • ffmpeg stitches slides into YouTube Shorts format
  • Open-source tools and free cloud VM power the process

Tail sampling rules in the OpenTelemetry Collector: cost and pitfalls

Your second-tier Collector keeps restarting, or your trace bill refuses to fall: either way, it is your tail sampling rules that need another look, well before you touch the traffic.

  • Tail sampling rules impact memory usage and performance in OpenTelemetry Collector
  • Three types of sampling rules: exclusions, safety nets, and cost ceiling
  • Monitor key metrics to ensure tail sampling rules function properly

More from Friday 20 November →