Ripple · GTreasury · Bank connectivity
Ripple acquired GTreasury, a treasury management platform. Every bank it connects to needs a connector, and building connectors depended on a small number of specialist engineers. LightCI built an AI connector builder that reads a bank’s documentation and generates the connector inside GTreasury’s existing architecture.
Ripple is an enterprise payments and blockchain company. It acquired GTreasury, a treasury management platform for corporate finance teams.
The long tail of banks
To the specialists, each bank looked bespoke. So each connector waited its turn in a two-person queue.
of target banks fit three or four common auth patterns.
That is the part a template can carry. The connector builder is designed around it: reuse the pattern, configure the bank, and save engineering for the cases that genuinely need it.
Documentation in, connector out
The connector builder does the reading, the matching and the writing. What it produces is a GTreasury connector, built the way GTreasury already builds them.
01 · Flows
Balances, transactions, payments: whatever the bank supports, identified from the bank’s own API reference.
02 · Auth template
OAuth over mTLS is a known pattern. The builder selects the matching template, or reuses one already built for a similar bank.
All requests use OAuth 2.0 client credentials over mutual TLS. Register a client certificate in the developer portal, then request a token from /oauth/token with your client ID and secret.
03 · Credentials
IDs, secrets, certificates and environment URLs, gathered as a checklist instead of rediscovered on every build.
All requests use OAuth 2.0 client credentials over mutual TLS. Register a client certificate in the developer portal, then request a token from /oauth/token with your client ID and secret.
04 · Types & mappings
Request and response types for every flow, with the bank’s fields mapped onto GTreasury’s.
{ "acctId": "string",
"avlblBal": { "amt": "decimal", "ccy": "ISO 4217" },
"valDt": "date" }type BalanceResponse = { acctId: string; avlblBal: Money; valDt: Date }05 · Connector
The connector, its mappings and its lifecycle artifacts land inside GTreasury’s existing connector architecture. No parallel system.
06 · The boundary
A bank-specific signing scheme is not forced through a template. The builder marks the boundary and hands that step to engineering.
Every request carries a bank-specific signature over the canonicalised body, plus a sequence counter that must increment within each session. Out-of-order requests are rejected.
The escalation boundary
The builder never guesses its way through a hard case. When a bank needs genuinely complex auth, signing, encryption or sequencing, it says so, and the work goes to the people who should do it.
What it was built to change
More work