> 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/recurring-payments-and-subscriptions/overview-of-recurring-payments.md). # Overview of Recurring Payments Recurring payments are the foundation of subscription-based business models, widely used in the SaaS industry. Beyond subscriptions, recurring payments also support standing orders (Hora'at Keva, הוראת קבע), which in Israel are common for rent, utilities, and insurance premiums. Hyp Enterprise supports both subscriptions and Hora'at Keva. ## What is a recurring payment? Instead of charging customers manually for each purchase, merchants can securely store a payment method and charge it on a schedule — monthly, annually, or any other cycle. A recurring payment uses a token to re-charge a credit card in an additional transaction. By definition, this requires *two or more transactions*. ## How are recurring payments different from installments? [Installments](/enterprise/payment-page-integration/installments.md) are part of *a single transaction*, with charges applied automatically at each interval as part of that same transaction. Recurring payments, on the other hand, create *a new transaction* for each charge. ## How are recurring payments different from reusing a saved credit card? [Reusing a saved credit card](/enterprise/available-payment-options/saved-card.md) spares the customer from re-entering card details each time they make a purchase. But saved cards are available only when the customer visits the payment page and initiates the purchase. In contrast, recurring payments are initiated by the merchant and require no customer interaction. ## Implementing recurring payments ### Subscriptions Hyp Enterprise supports subscriptions by letting you manually request charges on an existing credit card at regular intervals. For details, see [Implementing Recurring Payments](/enterprise/recurring-payments-and-subscriptions/implementing-recurring-payments.md). ### Hora'at Keva (הוראת קבע) Hyp Enterprise also supports Hora'at Keva for its merchants' customers. For details, see [Implementing Hora'at Keva](/enterprise/recurring-payments-and-subscriptions/horaat-keva.md). --- # 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/recurring-payments-and-subscriptions/overview-of-recurring-payments.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.