> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/other-features/connectors/available-connectors/zen.md).

# Zen

Connect Zen to Juspay Hyperswitch to accept payments with low fees, boost conversions, and manage raw card data securely through the Hyperswitch control center.

{% hint style="info" %}
This section gives you an overview of how to make payments via Zen through Hyperswitch.
{% endhint %}

![logo\_zen](https://hyperswitch.io/img/site/zenLogo.svg)

Zen is a modern and responsive payments portal with low fees for conversion boost and increased revenue. To know more about payment methods supported by Zen via Hyperswitch, visit [here](https://hyperswitch.io/pm-list).

### Prerequisites

1. You need to be registered with Zen and obtained the API Key from your Zen Account manager.
2. You should have a registered Hyperswitch account. You can access your account from the [Hyperswitch control center](https://app.hyperswitch.io).
3. Request the Zen support team to enable handling raw card data for your account. This will enable Hyperswitch to securely handle your customer's payment details.

[Steps](https://docs.hyperswitch.io/hyperswitch-cloud/connectors/activate-connector-on-hyperswitch) to activate Zen on Hyperswitch control center.


---

# 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.hyperswitch.io/other-features/connectors/available-connectors/zen.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.