> 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/available-payment-options/overview.md).

# Payment Methods Overview

Hyp Enterprise supports the following payment methods on its payment page:

* [Simple credit card](https://developers.hyp.co.il/enterprise/available-payment-options/simple-credit-card.md): the most common payment method, where the customer enters their credit card details directly on the payment page.
* [Saved card](https://developers.hyp.co.il/enterprise/available-payment-options/saved-card.md): allows customers to use a previously saved credit card for subsequent payments.
* [Digital wallets](https://developers.hyp.co.il/enterprise/available-payment-options/digital-wallets.md): allows paying with [Apple Pay](https://developers.hyp.co.il/enterprise/available-payment-options/digital-wallets.md#apple-pay), [Google Pay](https://developers.hyp.co.il/enterprise/available-payment-options/digital-wallets.md#google-pay), and [bit](https://developers.hyp.co.il/enterprise/available-payment-options/digital-wallets.md#bit), which are the three most popular digital wallets in Israel.
* [Payment link](https://developers.hyp.co.il/enterprise/available-payment-options/pay-by-link.md): allows sending a payment link to the customer via SMS, enabling them to complete the payment on their own device.
* [Payment request](https://developers.hyp.co.il/enterprise/available-payment-options/payment-request.md): another mechanism for sending payment links to customers, normally used for service payments, post-interaction billing, and similar cases.
* [Gift cards](https://developers.hyp.co.il/enterprise/available-payment-options/gift-cards.md): allows customers to pay with popular Israeli gift card types.
* [Pinpad pairing](https://developers.hyp.co.il/enterprise/available-payment-options/physical-pinpad-terminal.md): allows customers to pay using a physical terminal paired with the Hyp payment page.
* [Account to account](https://developers.hyp.co.il/enterprise/available-payment-options/account-to-account.md): allows customers to pay directly from their bank accounts, without using credit cards.

The basic structure of the payment page API request is the same for all payment methods and is shown in [Simple Credit Card](https://developers.hyp.co.il/enterprise/available-payment-options/simple-credit-card.md). All other payment methods can be fine-tuned by adding specific parameters to the request, as described in their respective sections.

Simple credit card is the default payment method, and it is automatically enabled for all terminals. Other payment methods must be explicitly configured in the terminal settings. As soon as they are configured, they appear on the payment page with no further configuration. However, you can choose to [hide payment methods](https://developers.hyp.co.il/enterprise/changing-the-default-payment-page-appearance/managing-payment-methods.md#hiding-payment-methods) when you don't need them on your payment page.


---

# 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/available-payment-options/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.
