> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/api-reference/open-api-references/checkout/checkout-notifications.md).

# Checkout Notifications

The **Create a Checkout Notification** endpoint allows you to manually trigger a notification event for an existing checkout session. This is useful for resending payment confirmations, triggering downstream webhook consumers, or testing notification flows in your integration.

{% hint style="info" %}
Notifications are sent for the checkout session identified by `checkoutId`. The session must exist and be retrievable via `GET /v2/checkout/{checkoutId}`.
{% endhint %}

## How It Works

{% stepper %}
{% step %}

### Identify the checkout session

Note the `checkoutId` of the session you want to trigger a notification for. See [Checkout Sessions](/api-reference/open-api-references/checkout/checkout-sessions.md) for how to retrieve session IDs.
{% endstep %}

{% step %}

### Create the notification

Call `POST /v2/checkout/{checkoutId}/notification`. The request body specifies the notification type and any additional parameters required by your notification configuration.
{% endstep %}

{% step %}

### Confirm delivery

A successful `2xx` response confirms the notification was accepted for delivery. Check your notification endpoint or webhook consumer for receipt.
{% endstep %}
{% endstepper %}

## API Reference

## Create a Checkout Notification

{% openapi src="/files/2a1a4293ec587ee0129ad1caaed6983120845ba1" path="/v2/checkout/{checkoutId}/notification" method="post" %}
[a477f48dd9168bd2ee1077c6399dab106e5491bf785fbde57185db0fcb31d32b.yaml](https://content.gitbook.com/content/OiXbo96Og9EN7rz2U44K/blobs/guUKPLHPZbgfg8qR8yIs/a477f48dd9168bd2ee1077c6399dab106e5491bf785fbde57185db0fcb31d32b.yaml)
{% endopenapi %}


---

# 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.verifone.com/api-reference/open-api-references/checkout/checkout-notifications.md?ask=<question>&goal=<user_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.