> 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/prerequisites-and-requirements.md). # Prerequisites and Requirements Hyp Enterprise is currently not a self-service platform, and you need to go through a setup process to start using it. The steps of this process are outlined below. ## 1. Sign a credit card acquiring agreement Before you, as an Israeli merchant, can begin accepting online credit card payments using Hyp Enterprise, you need to **sign an acquiring agreement** with one or more credit card companies (Isracard, Cal, or Max). This agreement enables your business to process card payments, assigning you a **vendor number** (`מספר ספק אינטרנטי`). For more about interacting with credit card companies, see [this page (in Hebrew)](https://www.creditguard.co.il/a3/%D7%9E%D7%A1%D7%A4%D7%A8-%D7%A1%D7%A4%D7%A7-%D7%90%D7%A9%D7%A8%D7%90%D7%99). This step is mandatory before Hyp can configure a terminal for you. If you sign with multiple acquirers (such as to optimize commissions or ensure redundancy), then you will receive multiple vendor numbers. In this case, Hyp can either set up a separate terminal for each vendor number or a single terminal covering all vendor numbers. **Note:** It's important to validate with your acquirer that the number is indeed an "Internet" vendor number, and not just a plain vendor number. ## 2. Contact Hyp’s sales team Once you, as a merchant, have a vendor number, contact the Hyp sales team at or [via this contact form](https://www.creditguard.co.il/%D7%A6%D7%95%D7%A8-%D7%A7%D7%A9%D7%A8) to begin the onboarding process. This includes: * Signing a **service agreement** with Hyp for setting up a payment terminal connected to your acquiring account. * (Optional) Signing an **integration agreement** for guided technical onboarding. If an integration agreement is in place, Hyp assigns a project manager to help define your integration requirements. A technical support representative is then appointed to advise your developers on implementing Hyp’s APIs. The integration agreement is most helpful for businesses with limited experience in payment integrations. ## 3. Receive credentials After signing the agreement(s), Hyp submits a request to set up your terminal with [Shva](https://www.shva.co.il/about-us/), Israel's payment processor. Once Shva completes the request, Hyp's support team (available at ) creates the terminal and then sends terminal credentials to you. While Shva setup is in progress, the Hyp sales team provides you with your test environment configuration information. If you have specific requirements for the test environment — for example, testing Apple Pay or other [payment methods](/enterprise/available-payment-options/overview.md) — please inform the Hyp sales team. Configuration information for both the test and production environments includes: * Base URLs for the Hyp Enterprise APIs. * Hyp Console URL and access credentials. * Username, password, merchant ID, and terminal number. ## 4. Set up test and production environments With the credentials in hand, start setting up and testing Hyp Enterprise integration using the test environment. Once verified, Hyp will assist in moving the setup to **production** and enable live transactions. For details, see [Environment Setup](/enterprise/introduction/environment-setup.md). If you have signed an integration agreement, Hyp's assigned integration specialist will help you streamline the setup, testing, and go-live phases. --- # 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/prerequisites-and-requirements.md?ask=&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.