# Simple Credit Card

Credit card payments are the simplest way to accept payments with Hyp, and they are available to merchants by default in all terminals and payment pages.

Here's what the payment page looks like for credit card payments:

![Payment page for credit card payments](/files/PZcivCMtsMonao2C89UA)

## Prerequisites and terminal configuration

Credit card payments are available by default in all terminals without any additional configuration.

## Payment page integration

The payment page integration process is covered in [Integrating Hyp's Payment Page and Accepting Payment](/enterprise/payment-page-integration/integrating-hyps-payment-page-and-accepting-payment.md).

For a walkthrough of a simple payment page integration in a sample Express.js application with additional context, see [Basic Integration Flow](/enterprise/introduction/basic-integration-flow-hello-world-with-a-full-working-charge.md).

## Additional considerations

You may want to suggest that the customer save their credit card details for future use, and then enable reuse of the saved details during repeat payments. See [Saved Card](/enterprise/available-payment-options/saved-card.md) for implementation guidance.

If your terminal supports more payment methods in addition to simple credit card payments, they will be displayed on the payment page by default. If you don't want to show these additional methods on a particular payment page, you can hide some or all of them. See [Hiding Payment Methods](/enterprise/changing-the-default-payment-page-appearance/hiding-payment-methods.md) for details.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developers.hyp.co.il/enterprise/available-payment-options/simple-credit-card.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.