> 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/pay/common-use-cases/installments.md).

# Adding Installments to the Payment Page

In Israel, it's very common for customers to split their payments into several installments. Hyp Pay makes it easy for you to offer this option right on your payment page.

There are two main ways your customers can pay in installments:

1. **Regular installments**. The total amount is split into equal monthly payments with no interest.
2. **Credit installments**. The customer pays the total amount plus interest over three or more installments.

The best part is that you don't have to worry about the logistics. The credit card company handles everything once the transaction is set up. They'll make sure the payments are processed correctly each month.

## Enabling installments

To start offering installments, just add a few extra parameters to your [payment page request](/pay/getting-started/creating-a-payment-page.md#create-a-payment-page-request). If you don't include them, the payment will be processed as a single, one-time charge.

Here are the parameters you'll use to set things up:

* `Tash`: Sets the maximum number of installments you'll allow. For example, if you set this to `12`, your customer can pick anything from 1 to 12 installments.
* `FixTash`: If you want to require a specific number of installments, set this to `True`. When it's `False` (the default), customers can choose any number up to the `Tash` value.
* `tashType`: Tells the system which kind of installment to use. Use `1` for regular installments (no interest) or `6` for credit installments (with interest). Just a heads-up: credit installments usually require at least 3 payments.
* `ShowEngTashText`: If your payment page is in English (`PageLang=ENG`), set this to `True` to display the installment labels, which aren't shown by default.

Here's an example of an API request for a payment page that offers up to six regular installments:

{% code overflow="wrap" %}

```http
https://pay.hyp.co.il/p/?action=APISign&What=SIGN&KEY=your-api-key&PassP=your-api-password&Masof=0010345518&Amount=600&Tash=6&tashType=1
```

{% endcode %}

## Payment experience

Once you've enabled installments, your customers will see a drop-down menu on the payment page. They can use it to pick exactly how many payments they want to make:

![Picking the number of installments on the payment page](https://212218747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNgLaCFED7cVeSJ11x81c%2Fuploads%2Fgit-blob-594f1950e7a2e43ff4fb9e0b4740a1a7f65dfdfc%2Finstallments-regular-6.png?alt=media)


---

# 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/pay/common-use-cases/installments.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.