Lithic builds two-layer monitoring with Retool

Diving deeper into

Ronnie Caspers, Product at Lithic, on using Retool for fintech ops

Interview
That two layer monitoring requirement made even robust tools struggle, so we built our own system in-house with Retool.
Analyzed 5 sources

The real edge here is not better dashboards, it is owning the exact risk logic of a complicated card program. Lithic sits between banks, networks, business customers, and those customers' end users, so it has to watch activity at both the business level and the cardholder level. Off the shelf monitoring tools usually expect one customer record and one stream of activity. Retool let Lithic stitch together its own databases, APIs, and approval controls so ops teams could investigate and act without waiting on engineers.

  • Lithic is an issuer processor and program manager. In practice that means configuring BINs, routing network messages, enforcing compliance rules, and managing card programs for fintech customers. A two layer model matters because the direct customer is a business, but the risky behavior may sit with that business's own users making card transactions.
  • The operational gap is that monitoring is not just seeing alerts. Ops staff need to open a case, inspect customer configuration, preview a change, validate inputs, and push an action into production safely. Retool was built for this kind of internal app, where engineers wire production data sources into tools that non engineers can use with guardrails.
  • This is a common pattern in fintech infrastructure. As card issuing and embedded finance spread, the hard part moves from basic processing to custom controls, reconciliation, and exception handling. Lithic positions around fine grained control and speed to market, which makes internal tooling part of the product, not just back office support.

Going forward, more issuer processors and embedded finance platforms will keep replacing generic ops software with custom internal systems around compliance, fraud, and reconciliation. The winners will be the ones that turn messy edge cases into fast, safe operator workflows, because that is what lets them support more complex customers without scaling engineering headcount linearly.