All case studies
Ripple

Ripple · GTreasury · Bank connectivity

Every bank looked like its own project. Most of them were the same one.

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.

Connector builds
A two-person bottleneck
Bank 017Bank 042Bank 093Bank 005Bank 128Bank 064Bank 211Bank 009Bank 156Bank 077Bank 030Bank 184Bank 012Bank 240Bank 058Bank 101Bank 003Bank 199Bank 086Bank 147Bank 021Bank 233Bank 070Bank 115Bank 017Bank 042Bank 093Bank 005Bank 128Bank 064Bank 211Bank 009Bank 156Bank 077Bank 030Bank 184Bank 012Bank 240Bank 058Bank 101Bank 003Bank 199Bank 086Bank 147Bank 021Bank 233Bank 070Bank 115
Bank 009Bank 156Bank 077Bank 030Bank 184Bank 012Bank 240Bank 058Bank 101Bank 003Bank 199Bank 086Bank 147Bank 021Bank 233Bank 070Bank 115Bank 017Bank 042Bank 093Bank 005Bank 128Bank 064Bank 211Bank 009Bank 156Bank 077Bank 030Bank 184Bank 012Bank 240Bank 058Bank 101Bank 003Bank 199Bank 086Bank 147Bank 021Bank 233Bank 070Bank 115Bank 017Bank 042Bank 093Bank 005Bank 128Bank 064Bank 211
The long tail of banks · illustrative
Ripple
About the company
Ripple

Ripple is an enterprise payments and blockchain company. It acquired GTreasury, a treasury management platform for corporate finance teams.

Sector
Payments and treasury
HQ
San Francisco, CA

The long tail of banks

Every bank, its own project.

To the specialists, each bank looked bespoke. So each connector waited its turn in a two-person queue.

Template A
Template B
57%Standard configurable
28%Standard + certificates
13%Nonstandard flows
2%Manual access
Lanes 1 + 2 · ≈85% · covered by reusable templates
100 tiles = target banks · unnamed and illustrative
0%

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.

57% Standard configurable
28% Standard + certificates
13% Nonstandard flows
2% Manual access

Documentation in, connector out

Start from the bank’s own docs. End with a connector.

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

It reads the documentation and finds the flows.

Balances, transactions, payments: whatever the bank supports, identified from the bank’s own API reference.

Bank 042 · API reference

Endpoints

GET/accounts/{id}/balances
GET/accounts/{id}/transactions
POST/payments
Connector builder · Flows
BalancesGET /accounts/{id}/balances
TransactionsGET /accounts/{id}/transactions
PaymentsPOST /payments

02 · Auth template

It picks the auth template.

OAuth over mTLS is a known pattern. The builder selects the matching template, or reuses one already built for a similar bank.

Bank 042 · API reference

Authentication

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.

Connector builder · Auth template
Template A
OAuth / API key
Template BSelected
OAuth 2.0 + mTLS
Reused from a bank with the same pattern. Nothing rebuilt.

03 · Credentials

It lists exactly what to ask the bank for.

IDs, secrets, certificates and environment URLs, gathered as a checklist instead of rediscovered on every build.

Bank 042 · API reference

Authentication

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.

Environments

sandbox.api.bank042.example
api.bank042.example
Connector builder · Credentials
Client IDFrom bank
Client secretFrom bank
Client certificate (PEM)From bank
Private keyFrom bank
Sandbox base URLFrom docs

04 · Types & mappings

It writes the types and maps the fields.

Request and response types for every flow, with the bank’s fields mapped onto GTreasury’s.

Bank 042 · API reference

Balance object

{ "acctId": "string",
  "avlblBal": { "amt": "decimal", "ccy": "ISO 4217" },
  "valDt": "date" }
Connector builder · Types & mappings
type BalanceResponse = { acctId: string; avlblBal: Money; valDt: Date }
acctId→accountNumber
avlblBal.amt→availableBalance
avlblBal.ccy→currency
valDt→valueDate

05 · Connector

It generates the connector in GTreasury’s own format.

The connector, its mappings and its lifecycle artifacts land inside GTreasury’s existing connector architecture. No parallel system.

Connector builder · Connector package
├connector config
├auth · template B
├flows · balances, transactions, payments
├types and field mappings
└lifecycle artifacts
GTreasury connector formatReady for review

06 · The boundary

And it knows where to stop.

A bank-specific signing scheme is not forced through a template. The builder marks the boundary and hands that step to engineering.

Bank 093 · API reference

Request signing

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.

Connector builder · Boundary
!Escalate to engineering
Bank-specific request signing with session sequencing.
Outside every template. The routine parts are generated; this step goes to an engineer with the context attached.

The escalation boundary

A clear line between routine work and real engineering.

Routine · designed to need no engineer
Configuration
Field mappings
Parameters
Environment setup
Escalated · reserved for engineers
Complex auth
Request signing
Encryption
Sequencing

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

From a two-person queue to a guided workflow.

Who builds a connectorA small number of specialist engineersNon-engineers, guided by templates
Where a build startsA blank connectorThe bank’s own documentation
AuthenticationWorked out again for each bankSelected or reused from a template
Hard casesEvery case looked hardEscalated to engineering, explicitly
New team membersDependent on the specialistsOnboard through guided templates

Your company, next.

Bring the backlog only two people can clear.