> 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/payment-page-integration/deferring-payments.md).

# Deferring Payments

Hyp Enterprise allows merchants to defer payments, delaying the charge by a specified number of months. Deferred payments are commonly used for promotions, travel packages, and high-value goods.

Deferred payments can also be combined with [installments](https://developers.hyp.co.il/enterprise/payment-page-integration/installments.md), where the first installment is charged after the deferral period. For example, a customer may pay in 10 installments, starting three months after the purchase date.

To implement deferred payments, make a standard [payment page request](https://developers.hyp.co.il/enterprise/payment-page-integration/integrating-hyps-payment-page-and-accepting-payment.md), but include the following inside the `doDeal` element of your request:

```xml
<ashraitEmvData>
    <deferMonths>3</deferMonths>
</ashraitEmvData>
```

The `deferMonths` element specifies the number of months to defer the payment. The value must be between 1 and 99, with an optional leading zero for values less than 10.

Apart from adding the elements shown above, the payment page flow is exactly the same as for a standard, non-deferred payment.


---

# 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/payment-page-integration/deferring-payments.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.
