> 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.md).

# Payment Gateways

One of the few reason Penni Cart came to full realization was to have a solution many Webflow users and communities face; limited payment processor option. 

Our team are working hard to ship more payment gateways for all Webflow users, as of this stage of the product. The following three below are payment gateways Penni Cart will start to offer and support transaction connection with.

{% content-ref url="/pages/xIXkEGnaexpBzDEj7ASc" %}
[Stripe](/managing-your-store/payment-gateways/stripe.md)
{% endcontent-ref %}

{% content-ref url="/pages/VK0VCFwW3UYJmsJo0nHK" %}
[Elavon](/managing-your-store/payment-gateways/elavon.md)
{% endcontent-ref %}

{% content-ref url="/pages/YBv9023xZR07F6Yotq1q" %}
[Authorize.net](/managing-your-store/payment-gateways/authorize.net.md)
{% endcontent-ref %}

### <mark style="color:purple;">Got something to add?</mark>

We would love to hear your ideas, suggestions, and future request to help Penni Cart empower many more Webflow users. Please visit our [wishlist](https://wishlist.pennicart.io/) to request or see what is in the works.


---

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