> For the complete documentation index, see [llms.txt](https://docs.pennicart.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pennicart.io/managing-your-store/payment-gateways/stripe.md).

# Stripe

{% hint style="warning" %}
Please note that this section/document is still <mark style="color:purple;">**Work in Progress**</mark><mark style="color:purple;">.</mark> It might be updated, revised, or changed entirely in the near future.&#x20;
{% endhint %}

{% embed url="<https://www.youtube.com/watch?v=JWFbdzlL7Rc>" %}

To have everything connect, navigate to your Stripe dashboard and start creating a webhook under the **Developer**, below are requirements in order to connect Stripe as the payment gateway on your store.

1. Public & Secret keys can be found on Stripe's Developer page
2. Setting the webhook url to <mark style="color:purple;">`https://api.pennicart.io/stripe/webhook`</mark>
3. Enable the following events <mark style="color:purple;">`payment_intent.succeeded`</mark> & <mark style="color:purple;">`payment_intent.payment_failed`</mark>
4. Once created, simply click on "Reveal" below **Signing secret** for the Webhook Secret needed on the Penni Cart Dashboard


---

# 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.pennicart.io/managing-your-store/payment-gateways/stripe.md?ask=<question>&goal=<endgoal>
```

`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.