Lithic

Lithic issues and manages payment cards programmatically: financial accounts, the cards issued under them, and the transactions those cards generate.

Authentication

• API key

Actions

Generic API request. Call any Lithic API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

• Get cardFetch one Lithic issued card by its token to check whether it is open or paused and how it was issued, before authorising spend or updating it.
• List accountsList accounts (GET /accounts).
• List cardsList issued cards (GET /cards).
• List transactionsList card transactions (GET /transactions).

Triggers

• New accountStarts when a new financial account is created in Lithic, so a workflow can react as cardholder accounts are provisioned.
• New cardStarts when a new card is issued in Lithic, so a workflow can react as virtual or physical cards are created.
• New card (webhook)Starts the moment a new card is issued in Lithic, delivered by a webhook instead of polling for newly created cards.
• New transactionStarts when a new card transaction is recorded in Lithic, so a workflow can react to spend activity as it happens.
• Transaction updated (webhook)Starts every time a Lithic card transaction changes state (authorization, clearing, settlement), delivered by a webhook instead of polling for new transactions.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.