Retool Shifts BIN Allocation to Ops

This reveals that card issuing is not just an API business, it is a capacity allocation business where the hard part is deciding which program gets which slice of the underlying network setup. At Lithic, assigning a customer to a dedicated BIN or a shared sub-BIN range affects launch speed, compliance setup, product flexibility, and how much custom logic ops teams must manage later. That is why moving this workflow from engineers into Retool matters so much.

• A dedicated BIN is closer to a custom lane. It gives a customer more control over card behavior, bank and network configuration, and future product changes. Shared ranges are more like apartments in the same building, faster and cheaper to stand up, but with more coordination and tighter constraints.
  1 sacra 2 sacra
• Lithic sits below many fintech products as the issuer processor connecting banks, networks, authorization messages, settlement, and card manufacturing. Because customers range from simple gift card programs to complex neobanks and embedded finance products, customer placement has to match the actual job the card program is doing.
  2 sacra 3 sacra
• Retool changes who can operate this system. Instead of engineers editing production tables, ops teams can see a customer configuration, run guarded actions, and apply business rules with approvals and validation. In fintech, that turns internal software from a reporting layer into the control surface for money movement and compliance.
  1 sacra 4 sacra

The next step is more software defined card ops, where issuer processors expose flexible primitives and internal tools become the operating layer that packages them for program managers. That should let companies like Lithic support more customer types, with less engineering hand holding, while still giving larger programs room to move into more bespoke setups over time.