> For the complete documentation index, see [llms.txt](https://developers.hyp.co.il/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.hyp.co.il/enterprise/introduction/overview.md).

# Hyp Enterprise Overview

Hyp Enterprise (formerly known as Hyp CreditGuard) is Israel's leading PCI DSS-certified payment gateway. It provides secure, reliable, and fully customizable payment solutions for businesses of all sizes.

## Key capabilities

* **Hosted payment page** – a customizable, PCI DSS-compliant payment page that supports branding, styling, and multiple payment methods out of the box.
* **Support for a variety of payment methods**, including credit cards, Apple Pay, Google Pay, bit, payment links, and gift cards.
* **Advanced payment scenarios**:
  * Recurring payments – subscriptions and standing orders
  * Two-phase commits – authorization and capture flows
  * Tokenization for storing and reusing card details
  * Refunds
  * Payouts
* **Israeli market optimization**:
  * Native support for Israeli personal ID verification
  * Installment payments (“Tashlumim”)
  * Gift card integrations with major local providers

## Who this documentation is for

* **New users**. If you are only looking to sign up for Hyp Enterprise, start by reading about [prerequisites and requirements](/enterprise/introduction/prerequisites-and-requirements.md), then continue with [environment setup](/enterprise/introduction/environment-setup.md) instructions.
* **Developers**. If you are integrating Hyp Enterprise into your application, this documentation covers Hyp Enterprise's XML API, supported commands, request/response formats, and integration patterns.
* **Experienced integrators**. If you already work with Hyp Enterprise and just need command-level details, go directly to the [API reference](/enterprise/api-reference/index.md).

## How to get started

1. [Contact Hyp sales](mailto:sales@hyp.co.il) for pricing, onboarding, and tailored solutions.
2. Review [prerequisites and requirements](/enterprise/introduction/prerequisites-and-requirements.md).
3. Complete [environment setup](/enterprise/introduction/environment-setup.md) to configure your test and production environments.
4. Familiarize yourself with [key concepts](/enterprise/introduction/key-concepts-and-terminology.md) and the [request/response structure](/enterprise/introduction/request-and-response-general-structure.md).
5. Follow the step-by-step [guide on implementing a basic integration flow](/enterprise/introduction/basic-integration-flow-hello-world-with-a-full-working-charge.md) in a sample Node.js application.
6. Explore the [available payment flows and configurations](/enterprise/introduction/when-to-use.md) and choose those that best fit your business needs.
7. Explore the [API reference](/enterprise/api-reference/index.md) to dive deeper into specific commands.

## Special thanks

The Hyp team would like to thank [Tom Granot](https://granot.io/) and [Jura Gorohovsky](https://gorohovsky.com/) for their help writing, editing and testing this documentation site.


---

# 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://developers.hyp.co.il/enterprise/introduction/overview.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.