Corporate banking runs on connections. We're making them programmable.
Why we exist.
Lynqx is built by Cateina, our parent company — an integration and data engineering firm headquartered in Mumbai that has spent years connecting corporate banking, payments, and open-banking systems for enterprises. Lynqx is that work turned into a product: the bank adaptors, the consent model, and the API surface we kept rebuilding one client at a time, made into a platform you connect to instead of a project you have to run.
Every large company runs its money through a tangle of bank portals, host-to-host files, and one-off integrations that break when a format changes. For companies operating across borders — where a single group banks with eight institutions under five regulators — the tangle compounds with every market.
We started Lynqx to give that tangle an operating system: one consent-based layer where banks, ERPs, and treasury systems connect once, and payments, statements, and workflows become things you can compose, observe, and audit.
The team came from the two sides of this problem — bank connectivity engineering and corporate treasury — and we build for both: a console finance trusts, an API developers actually want.
Three principles, no exceptions.
01
Consent over convenience
Nothing touches a connected system without an explicit, visible, revocable grant — even when a silent default would be easier.
02
One layer, two audiences
Treasury and engineering look at the same system, not exports of each other's. Every feature ships for both or not at all.
03
Local rails first
We build for the hardest terrain — multi-bank, multi-regulator, multi-format — so global operations settle on the local rails of every market.
Build the layer underneath treasury.
We hire engineers who like protocols more than pixels, and finance operators who've felt the tangle first-hand. Remote-friendly across four continents.