> 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/credit-cards.md).

# Accepting Credit Cards

Credit card payments are the simplest way to get paid with Hyp. Best of all, they're **available to your customers by default** on all your terminals and payment pages.

All you need to do is request a payment page, and it'll be ready to take credit card payments right away. You can find the step-by-step guide in [Creating a Payment Page](/pay/getting-started/creating-a-payment-page.md).

![A basic payment page for credit card payments](https://212218747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNgLaCFED7cVeSJ11x81c%2Fuploads%2Fgit-blob-9e1ee985ce544fd553e5fd737592ec68aa8a8c6f%2Fbasic-credit-card.png?alt=media)

The basic payment page is a great starting point, but you can make things even easier for your customers. Depending on what your business needs, you can enable more payment methods, tweak the look and feel, or even change how you send the page to your customers.

Here are a few ways you can **level up your payment page**:

* [Digital wallets](/pay/common-use-cases/digital-wallets.md): Let your customers breeze through checkout using Apple Pay or Google Pay without needing to dig for their card.
* [Installments](/pay/common-use-cases/installments.md): Let your customers split their payments into monthly installments — a great way to help them say "yes" to bigger purchases.
* [Customizing page UI](/pay/common-use-cases/customizing-payment-page-design.md): Make the payment page feel like a natural part of your site by controlling its UI language and layout.


---

# 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/credit-cards.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.