Types of Events

We currently send the following types of events. However, it's essential to note that we may introduce new ones at any moment. When designing and updating your code, be cautious not to assume this list is exhaustive.

Event Types

Event TypeDescription
account_holder.createdNotification of the successful creation of an accountholder. See Create Webhook for KYC/KYB Status.
account_holder.updatedNotification of the update of an accountholder. See Create Webhook for KYC/KYB Status.
account_holder.verificationNotification of a verification result for an accountholder. See Create Webhook for KYC/KYB Status.
balance.updatedNotification that the balance for an ISSUING, OPERATING, or RESERVE financial account has been updated
book_transfer_transaction.createdNotification that a book transfer between your financial accounts has occurred.
book_transfer_transaction.updatedNotification that a reversal of a book transfer between your financial accounts has occurred.
card.createdNotification that a card has been created.
card.convertedNotification that a card has been converted from VIRTUAL to PHYSICAL.
card.renewedNotification that a card has been renewed.
card.shippedPhysical card shipment notification. See Physical Card Shipping Webhook.
card_transaction.updatedNotification that a transaction object has either been created or updated with a new event.
card_transaction.enhanced_data.updatedNotification that enhanced commercial data (L2/L3) is available for a card transaction.
dispute.updatedIndication of an update to a dispute.
dispute_evidence.upload_failedDispute evidence upload failed. The most likely cause of this is the file uploaded was not a supported format.
external_bank_account.createdNotification that an external bank account resource has been created
external_bank_account.updatedNotification that an external bank account has been updated e.g., name change, verification status changes
financial_account.createdNotification that a financial account has been created.
payment_transaction.createdNotification that an ACH transaction has occurred. See Financial Transactions
payment_transaction.updatedNotification that the state of an ACH transaction has been updated. See Financial Transactions
statements.createdNotification that a statement has been created.
settlement_report.updatedNotification that a settlement API report has been created or updated. Only available for programs that settle directly with the card networks.
three_ds_authentication.createdNotification that a 3DS authentication has taken place on one of your cards.
tokenization.approval_requestCard network's request to Lithic to activate a token.
tokenization.resultNotification of the end result of a tokenization, whether successful or failed.
tokenization.two_factor_authentication_codeA code to be passed to an end user to complete digital wallet authentication.
tokenization.two_factor_authentication_code_sentNotification that a digital wallet tokenization request 2FA code has been sent to our downstream messaging providers for delivery.
tokenization.updatedNotification that a tokenization status has changed.
transfer_transaction.created (deprecated)Notification that a transfer between financial accounts has occurred. See Financial Transactions.

This event type has been deprecated in favor of the book_transfer_transaction.created and book_transfer_transaction.updated types.

Event Schema

You can reference the schema of the various events types in our centralized OpenAPI spec.

Send Event Examples

You can simulate events in Sandbox. Please refer to this section.