> For the complete documentation index, see [llms.txt](https://docs.omnivatelehealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnivatelehealth.com/overview/stripe-integration.md).

# Stripe Integration

This document will guide you through the transaction enabling process for your platform

### Introduction

Stripe is a tool that helps to accept payments online in a safe and straightforward way. When you connect Stripe to your platform, you can manage transactions smoothly, making it easy for your users to pay. It's all about giving them a hassle-free payment experience.

### Integration Overview

* This documentation outlines the steps required to integrate Stripe into your platform for processing payments that are redirected to specific clinics.
* The integration involves configuring payment settings in your admin settings and setting up webhook events to listen to events related to payment processing.

### Registering with Stripe

1. Log in to Omniva platform's admin dashboard.
2. Navigate to the settings section and select payment configuration.
3. You'll find an option to integrate with Stripe. Click on it to proceed.
4. You'll be directed to the Stripe login page. If you don't have a Stripe account, you can create one by following the registration process.
5. After logging in, you'll land on the home section of your Stripe account, and click on the developer button.<br>

   <figure><img src="https://105206586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQbmSVGziFCVxttjnOvMC%2Fuploads%2FfB4b03HQ34zrEwSx1zCE%2Fimage.png?alt=media&amp;token=76c5fddf-ffb2-498c-a61d-c5333907cd39" alt=""><figcaption><p>Click on "Developers" button</p></figcaption></figure>

### Adding Webhook Events

1. In the developer button, locate the option in the webhook tab.

<figure><img src="https://t8411958.p.clickup-attachments.com/t8411958/1a95c566-f25e-40ab-a768-796e657c9148/image.png" alt=""><figcaption><p>Click on "Webhook" tab</p></figcaption></figure>

2. Click on the add an endpoint.

<figure><img src="https://t8411958.p.clickup-attachments.com/t8411958/ea3ecb38-d1fe-4e76-bd45-12e75c29e139/image.png" alt=""><figcaption><p>Click on " Add an endpoint" button</p></figcaption></figure>

3. Input the Endpoint URL provided by our platform. This URL is where Stripe will send notifications about payment-related events.

<figure><img src="https://t8411958.p.clickup-attachments.com/t8411958/0d42f1d1-42cc-471a-b91b-f416a5f6b326/image.png" alt=""><figcaption></figcaption></figure>

4. Click on the "Select Events" button.
5. Select all events that our platform needs to listen to, such as account, balance, customer, etc.

<figure><img src="https://t8411958.p.clickup-attachments.com/t8411958/7b026190-2d14-4030-9bb9-353c5e723657/image.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://t8411958.p.clickup-attachments.com/t8411958/88adcb37-1548-4cce-898e-31ea8a6e22ab/image.png" alt=""><figcaption></figcaption></figure>

6. After filling out all the details, click on the "Add endpoint" button.

<figure><img src="https://t8411958.p.clickup-attachments.com/t8411958/aece85c6-7905-4194-be65-0b3509cc9ad5/image.png" alt=""><figcaption><p>Click on "Add endpoint" button</p></figcaption></figure>

7. Once you've configured the webhook events, the integration process is complete.


---

# 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.omnivatelehealth.com/overview/stripe-integration.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.
