The small, sharp pieces our platforms are built from — factored out, hardened, and shipped as standalone libraries. Each one does a single job well, has no heavy dependencies, and drops into any stack: ours, yours, or a third party's.
When we solve a problem well inside one product — shortening a link for an SMS, matching a name against a sanctions list, scanning a UPI QR — we don't leave it buried. We extract it, give it a clean API, test it to death, and make it a library any team can use on its own.
Each library is genuinely standalone: small footprint, no platform lock-in, self-hostable, and documented. Use one without using anything else we make.
A self-hosted link shortener built for transactional messaging — the short links inside an OTP SMS, a statement email, a doorstep-visit confirmation. Deterministic short codes, optional expiry, click analytics, and a built-in QR for every link. No third-party shortener seeing your customers' traffic.
# shorten a link for an OTP SMS — expires in 10 min POST /v1/links { "url": "https://bank.in/verify?t=9f3b…", "ttl": 600, "once": true } # → response { "short": "https://q.bnk/aZ4x", "qr": "https://q.bnk/aZ4x.png", "expires": "2026-05-30T10:10:00Z" }
A fuzzy name-matching engine tuned for Indian names — the hard problem behind KYC dedup and sanctions screening. It handles transliteration across Indic scripts, initials and expansions, token reordering, honorifics and phonetic variants, and returns a calibrated confidence score instead of a blunt yes/no.
# compare an applicant to a watchlist entry match( "Rajesh Kumar Reddy", "R. K. Reddi" ) # → result { "score": 0.91, "decision": "review", "signals": [ "initials_expanded", "phonetic_match", "spelling_variant" ] }
An on-device camera scanner for the QR codes banking actually uses — UPI payment QRs, Aadhaar secure QR, and the document QRs Jansetu and EDMP stamp on every artefact. Decoding runs entirely on the device; nothing leaves the phone or browser. Ships as a web component and an Android module from one codebase.
// mount the scanner, parse a UPI QR scanner.on("decode", (raw) => { const upi = parseUpi(raw); // → structured, validated payload { "pa": "merchant@okbank", // vpa "pn": "Kirana Store", "am": "240.00", "valid": true } });
Every library follows the same contract — so adopting a second one feels exactly like the first.
Each library is a focused service or SDK with a minimal dependency tree — easy to audit, easy to run, easy to retire.
Ships as an OCI container with a Helm chart. Runs inside your boundary — no data leaves, no per-call fee to a vendor.
Use a library standalone, or let our platforms call it. The API is the same either way — no special-casing.
Nothing here is a toy. Each library already runs inside a pilot bank's LOS, Jansetu or EDMP deployment.
Tell us which one and where it'd fit. We'll spin up a sandbox you can hit the same afternoon.