# Timeline events Timeline events deliver information about account activity to your end users. > 📘 Timeline events versus data events > > [Timeline events](https://developers.pismo.io/pismo-docs/docs/timeline-overview) are meant to deliver messages to your end users, such as a credit-limit notification in a mobile banking app. These are not the same as [data events](https://developers.pismo.io/pismo-docs/docs/event-data). Timeline events are defined with a **type** and a **category**. Your Pismo representative works with you to define the categories and types for your organization. The following table illustrates an example configuration.
| Type | Category |
|---|---|
| Card | Events related to physical cards.\ `ACTIVATION` – Physical card was activated.\ `BLOCK` – Physical card was (temporarily) blocked by the user.\ `CREATION` – Card object for an account was created in the system.\ `DELIVERY` – Delivery event for a physical card was filed by the courier company.\ `PRODUCTION` – Card information was successfully sent to the embossing company and the card is being manufactured.\ `UNBLOCK` – Physical card was unblocked by the user. |
| Cash in | Events related to platform authorizations.\ `AUTHORIZATION` – Operation was authorized.\ `CANCELLATION` – Operation was cancelled.\ `CONFIRMATION` – Operation was confirmed.\ `DENIED` – Operation was denied.\ `DENIED_CANCELLATION` – Operation cancellation was denied.\ `PARTIAL_CANCELLATION` – Operation was partially cancelled. |
| Cash out | Events related to platform authorizations.\ `AUTHORIZATION` – Operation was authorized\ `CANCELLATION` – Operation was cancelled.\ `CONFIRMATION` – Operation was confirmed.\ `PARTIAL_CANCELLATION` – Operation was partially cancelled.\ `DENIED` – Operation was denied.\ `DENIED_CANCELLATION` – Operation cancellation was denied. |
| Confirmation | Events related to transaction confirmations.\ `AUTHORIZE` – Operation was authorized.\ `CANCELLATION` – Operation was cancelled.\ `REPLACEMENT`– Operation was replaced.\ `REFUSAL` – Transaction was not authorized and was refused. |
| Credit | Events from account's credit monitoring service.\ `LIMIT_NEAR` – Credit balance has exceeded 80 percent of its limit.\ `LIMIT_REACHED` – Credit balance has reached its credit limit. |
| Dispute | Events related to transaction disputes. There is only one status for this category.\ `CREATE` – A dispute was filed for a transaction. |
| Statement | Events pertaining to credit card account billing cycle.\ `CARD_BLOCK` – Physical card was blocked due to a past overdue statement.\ `CLOSE` – Current statement was closed.\ `PARTIAL_PAYMENT` – Partial payment was confirmed.\ `PAYMENT` – Payment for the current statement was confirmed.\ `OVERDUE` – Statement due date passed without payment. |
| Tokenization | Events for **tokenized** cards (when the card number is registered with a mobile payments system, such as Apple Pay or Google Pay). There is only one status for this category:\ `ACCEPTED` – Card tokenization was accepted. |
| Transaction | Events related to authorizing transactions.\ `AUTHORIZE` – Transaction was authorized (for example, a purchase was made).\ `CANCELLATION` – Transaction was not authorized and was canceled.\ `CANCELLATION_REFUSAL`– Cancellation was not authorized and was refused.\ `CANCELLATION_REVERSAL`– Cancellation was reversed.\ `INCREMENTAL`– Incremental amount was added to the transaction.\ `PARTIAL_CANCELLATION`– Operation was partially cancelled.\ `REFERRAL`– Operation was referred.\ `REFUSAL` – Transaction was not authorized and was refused (for example, due to lack of credit).\ `REPLACEMENT`– Operation was replaced. |