Lithic review

Lithic is a hosted card issuer processing and money movement platform, not a library or server that a customer deploys in its own environment. It sits between a card program and the banking, card-network and payment operations the program depends on. Developers use Lithic’s API and dashboard to configure issuing, accounts, payment flows, ledgers and fraud controls.

The platform covers credit, debit and prepaid card programs for individuals and businesses. It also offers virtual and routable accounts, ACH and wire transfers, and debit and credit ledgers for tracking program money movement. Processing uses direct network connections, according to Lithic. For teams that want more than processing infrastructure, optional services include program management, cardholder support, disputes and chargeback handling, and fraud mitigation.

That combination can reduce the number of vendors a program has to coordinate. It also means Lithic becomes part of a financially critical stack: evaluate its bank and network relationships, operational responsibilities and exit terms alongside the API.

Lithic presents an API as the core developer integration surface, supported by a dashboard and documentation. The developer site lists a sandbox, API status page, changelog, libraries and SDKs, and guides for the ledger, ACH, digital wallets and quickstart setup. It also provides guides for generating an API key and using the Lithic MCP Server.

The homepage does not name an API protocol, SDK languages or a CLI. Confirm the API interface, supported languages, SDK maintenance status and any webhook or event delivery options in Lithic’s documentation before choosing an integration design. The sandbox gives teams a place to explore the platform before production, but confirm which flows and edge cases it models.

The integration work is likely to extend beyond calling endpoints: card programs also require decisions about authorization, ledgers, settlement, fraud rules and operational responsibilities. Use the documentation and vendor discussions to map those responsibilities and test failure handling before launch.

Lithic does not publish monthly or annual pricing. The available pricing information lists no plans, add-ons, starting price or free tier, and says terms are negotiated through sales and underwriting. There is no published free-trial detail either. That makes it difficult to estimate cost from a public rate card before sharing program details with the vendor.

The billing model and the way costs change with card volume, transactions, accounts, transfers or support services are not published in the pricing information. Do not assume that a sandbox means free production usage, or that a particular service is included in a processing quote. Ask sales for itemized pricing, minimums, implementation fees, volume bands, dispute costs and any charges for ACH, wires or program services. Also ask how pricing changes as the program scales and what happens if volume falls below a commitment.

Because there is no public starting price, teams should compare a written quote against their expected transaction mix and operational needs before selecting Lithic.

Lithic is presented as a hosted processing platform, not as software customers can deploy themselves. The product materials do not present an open-source edition or a source-code licence, so teams should treat the service as closed and hosted unless Lithic confirms otherwise in writing.

The vendor materials here do not establish what data can be exported, in which formats, or how a customer can retrieve it after ending service. Ask for the export process, retention period, fees and timing, along with the portability of ledger history, card and account records, and dispute data.

Migration is likely to involve more than replacing an API client: card programs depend on bank and network arrangements, authorization behavior, ledgers and operational workflows. Confirm which parts of those relationships and records can move, and plan for a parallel-run or transition period if the program cannot switch processors at once.

Lithic states that it has 99.99%+ uptime and no scheduled downtime. It also lists SOC 1 Type 1, SOC 2 Type 2, PCI DSS and ISO 27001. Treat these as vendor statements to validate against the current service commitments, audit materials and the specific products in your contract. Ask how availability is measured and what service credits or incident communications apply.

The published materials do not publish API rate limits, request quotas, retry guidance or production overage rules. Confirm those limits, along with authorization latency expectations, maintenance behavior, idempotency support and incident escalation paths. Test how your system handles timeouts, duplicate requests, delayed settlement data and downstream bank or network failures.

Lithic offers direct network connections and ledgering, but your program still needs reconciliation, monitoring and operational ownership. Before launch, verify which party handles disputes, fraud monitoring, cardholder support and compliance tasks; these services vary with the service option you choose.