> For the complete documentation index, see [llms.txt](https://docs.tebex.io/developers/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tebex.io/developers/tebex.js/checkout/events.md). # Events Events are fired by `Tebex.checkout` upon specific actions to alert your frontend and enable you to take action when required. These events should **not** be used to confirm actual receipt of payment - you should use [Webhooks](/developers/webhooks/overview.md) instead. To add a checkout event callback, use `Tebex.checkout.on()` . The first argument to this function should be the name of the event to listen to, and the second argument should be a function to call when that event is fired: ```javascript Tebex.checkout.on("payment:complete", (event) => { console.log("Payment completed!", event); }); ``` Available events are as follows:
NameFired Upon
"open"The portal popup opening after calling Tebex.checkout.launch().
"close"The portal popup closing after being dismissed by the user.
"payment:complete"The customer has successfully completed their payment.
"payment:error"The customer experienced an error, such as incorrect card details or insufficient funds, when making a payment.
All events that can be listened to with [`Tebex.checkout.on()`](#events) are exposed on the element as custom DOM events, which means you can use addEventListener to subscribe to them: ```html ``` --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.tebex.io/developers/tebex.js/checkout/events.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.