> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codapay/archived-tokenization-api-2.0/webhooks-notification/types-of-events.md). # Types of Events | Event Name | Description | | ---------------------------------------------- | ------------------------------------------------------------------------------------------------- | | shopper.created | Occurs whenever a shopper is created | | charge.created | Occurs whenever a charge is created | | token.created | Occurs whenever a token is created | | shopper.status.active | Occurs when a shopper status become active | | shopper.status.inactive | Occurs when a shopper status become inactive | | charge.status.blocked\_charge\_limit\_exceeded | Occurs whenever charge amount limit exceeded | | charge.status.blocked\_risk | Occurs when a charge is being blocked by risk | | charge.status.failed | Occurs whenever a charge failed | | charge.status.failed\_insufficient\_balance | Occurs when charge failed because of insufficient balance in the account | | charge.status.failed\_shopper\_cancel | Occurs when charge failed because shopper has canceled the transaction | | charge.status.failed\_token\_cancelled | Occurs when charge failed due to the cancellation of the associated token | | charge.status.failed\_token\_declined | Occurs when charge failed because the token used for the transaction has been declined | | charge.status.failed\_token\_expired | Occurs when charge failed because of token expiration | | charge.status.failed\_token\_not\_authorized | Occurs when charge failed due to unauthorized token | | charge.status.failed\_unauthenticated | Occurs when charge failed because of authentication | | charge.status.waiting\_for\_shopper\_action | Occurs whenever charge is pending completion and await for shopper action | | charge.status.processing\_shopper\_action | Occurs whenever charge shopper action is being processed by Coda | | charge.status.initiated | Occurs whenever charge is in the process of being initiated | | charge.status.initiated\_accepted | Occurs whenever charge initiation is successful and the Provider has accepted initiation | | charge.status.initiated\_not\_accepted | Occurs whenever charge initiation is unsuccessful and the Provider does not accept the initiation | | charge.status.initiated\_failed | Occurs whenever charge initiation is failed | | charge.status.not\_initiated | Occurs when charge is not being initiated on Provider end | | charge.status.authorized | Occurs whenever charge has been successfully authorized | | charge.status.succeeded | Occurs whenever charge is successful | | charge.status.succeeded\_for\_subscription | Occurs whenever charge is successful for subscription | | token.status.not\_initiated | Occurs when token is not being initiated on Provider end | | token.status.initiated | Occurs whenever token is in the process of being initiated | | token.status.initiated\_failed | Occurs whenever token initiation is failed | | token.status.waiting\_for\_shopper\_action | Occurs whenever token is pending completion and await for shopper action | | token.status.processing\_shopper\_action | Occurs whenever token shopper action is being processed by Coda | | token.status.not\_authorized | Occurs when token failed authorization process | | token.status.authorized | Occurs whenever token has been successfully authorized | | token.status.expired | Occurs whenever token has been expired | | token.status.cancelled | Occurs whenever token has been canceled | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.coda.co/codapay/archived-tokenization-api-2.0/webhooks-notification/types-of-events.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.