Event Types

claim.created

Occurs when a dispute intake claim is created.

postWebhookclaim.created

Payload

event_type'claim.created' required

The type of event that occurred.

tokenstring uuid required

Unique identifier for the claim, in UUID format

reference_idstring nullable required

Identifier for the claim as displayed in the Lithic dashboard. Populated depending on your program's setup, null otherwise. Use it to match claims received through the API and webhooks to the dashboard. This is not the claim token, which is the identifier to use in API requests

card_tokensstring[] required

Tokens for the cards associated with the disputed transactions

account_tokenstring uuid nullable required

Token for the account associated with the claim

account_holder_tokenstring uuid nullable required

Token for the account holder that filed the claim

createdstring date-time required

When the claim was created

updatedstring date-time required

When the claim was last updated

reason'CARD_NOT_PRESENT' | 'CARD_LOST' | 'CARD_STOLEN' | 'CARD_NEVER_RECEIVED' | 'COUNTERFEIT' | 'ACCOUNT_TAKEOVER' | 'PRODUCT_NOT_RECEIVED' | 'NOT_AS_DESCRIBED' | 'CREDIT_NOT_PROCESSED' | 'CANCELLED_RECURRING' | 'PAID_BY_OTHER_MEANS' | 'DUPLICATE_CHARGE' | 'LATE_PRESENTMENT' | 'INCORRECT_TRANSACTION_CODE' | 'NO_AUTHORIZATION' | 'DECLINED' | 'INCORRECT_AMOUNT' | 'ATM_CASH_NOT_DISPENSED' | 'ATM_DEPOSIT_WRONG_AMOUNT' | 'ATM_DEPOSIT_MISSING' required

Dispute reason code provided when creating the claim

status'INITIALIZING' | 'AWAITING_INFO' | 'SUBMITTED' | 'RESOLVED' | 'ABANDONED' required

Current lifecycle status of the claim

outstanding_requirementsstring[] required

Requirements that must be fulfilled before the claim can be submitted

submittedstring date-time nullable required

When the claim was submitted. Null until the claim reaches SUBMITTED status

Example payload

{
  "event_type": "claim.created"
}

Response

Return a 200 status to indicate that the data was received successfully

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.