Lithic Two-Layer Compliance Model
Ronnie Caspers, Product at Lithic, on using Retool for fintech ops
The key implication is that Lithic’s hardest compliance work sits above simple card transaction screening, because it has to understand both the business running the program and the end users spending through it. In practice that means rules cannot just ask whether one account looks suspicious. They have to connect sponsor bank requirements, network rules, card program setup, and downstream customer behavior across two linked entities, which is why generic monitoring tools broke on Lithic’s data model.
-
Lithic operates as an issuer processor and sometimes as a program manager, connecting sponsor banks to card networks and handling program setup, BIN strategy, compliance, and transaction flows. That role gives it visibility into the business customer’s card program and the end cardholder activity beneath it, not just one account layer.
-
Most off the shelf monitoring systems were designed for one customer record and one stream of activity. By contrast, modern compliance platforms now sell flexibility around custom schemas, partner specific rules, and case management, because fintech programs often need rules by product, partner, rail, or behavior pattern rather than one static bank template.
-
This also explains why Lithic built internal ops software around Retool. The need was not only dashboards, but safe action taking across live systems, with role based controls, validation, and links across Snowflake, Postgres, DynamoDB, and APIs. The operational challenge was joining fragmented systems into one review and decision surface for compliance teams.
Going forward, the winners in embedded finance will be the platforms that can turn messy, partner specific compliance logic into reusable internal tooling and configurable products. As larger banks and brands demand tighter controls and more standardized oversight, two layer monitoring will move from edge case to core requirement for card and BaaS infrastructure.