> 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/changing-the-default-payment-page-appearance/managing-payment-methods.md).

# Managing Payment Methods

The Hyp Enterprise payment page supports several [payment methods](https://developers.hyp.co.il/enterprise/available-payment-options/overview.md) in addition to standard credit card payments:

* Apple Pay
* Google Pay
* bit
* Pay By Link (IPR)
* Gift cards
* Pinpad Cloud Pairing (PCP)
* Account to account (A2A)

The exact set of payment methods available to you depends on your terminal settings.

By default, all available payment methods are displayed on the payment page. The standard credit card payment form is shown as the default option. You can customize this behavior by hiding specific methods or changing the default payment method.

## Hiding payment methods

If you want to hide one or more payment methods from the payment page, you can do this in one of two ways:

1. **To hide one or more payment methods**, use the `paymentMethods` array. To represent a payment method, add an object with two properties: `type` and `hidden`. The `type` property is the payment method type (`applepay`, `googlepay`, `bit`, `ipr` for Pay By Link, `gcs` for gift cards, `a2a` for account to account, and `pcp` for Pinpad Cloud Pairing), and the `hidden` property indicates whether to hide the payment method or not. For example, to hide Apple Pay, account to account, and Pay By Link:

   ```json
   <paymentPageData>
       <ppsJSONConfig>
          {
            "uiCustomData": {
                "paymentMethods": [
                     {"type": "applepay", "hidden": true},
                     {"type": "ipr", "hidden": true},
                     {"type": "a2a", "hidden": true}
              ]
            }
          }
       </ppsJSONConfig>
   </paymentPageData>
   ```
2. **To hide all payment methods** and only keep the standard credit card payment, use the `skipPaymentMethodsScreen` property. Instead of explicitly setting every payment method type to `"hidden": true` under `paymentMethods`, you can just set `skipPaymentMethodsScreen` to `true`:

   ```json
   <paymentPageData> 
       <ppsJSONConfig>
            {
              "uiCustomData": {
                    "skipPaymentMethodsScreen": true
              }
            }
       </ppsJSONConfig>
   </paymentPageData>
   ```

## Setting the default payment method

In some scenarios, you may want a specific payment method to be active by default when the payment page loads, instead of the credit card form. For example, if you are using a [physical pinpad terminal](https://developers.hyp.co.il/enterprise/available-payment-options/physical-pinpad-terminal.md), you want to open the pinpad pairing view immediately.

To define the default payment method, use the `defaultPaymentMethod` property in `uiCustomData` and set it to the type of payment method you want to preselect on the payment page. The supported values are:

* `creditcard` for the standard credit card form (default)
* `applepay` for [Apple Pay](https://developers.hyp.co.il/enterprise/available-payment-options/digital-wallets.md#apple-pay)
* `googlepay` for [Google Pay](https://developers.hyp.co.il/enterprise/available-payment-options/digital-wallets.md#google-pay)
* `bit` for [bit](https://developers.hyp.co.il/enterprise/available-payment-options/digital-wallets.md#bit)
* `ipr` for [Pay By Link](https://developers.hyp.co.il/enterprise/available-payment-options/pay-by-link.md)
* `pcp` for [Pinpad Cloud Pairing](https://developers.hyp.co.il/enterprise/available-payment-options/physical-pinpad-terminal.md)
* `a2a` for [Account to Account](https://developers.hyp.co.il/enterprise/available-payment-options/account-to-account.md)

Here's an example of how to set the default payment method to Apple Pay:

```json
<paymentPageData>
    <ppsJSONConfig>
       {
         "uiCustomData": {
             "defaultPaymentMethod": "applepay"
         }
       }
    </ppsJSONConfig>
</paymentPageData>
```

When a default payment method is set, the payment page skips the initial view with credit card fields and opens the specified payment method's view immediately.

If the chosen payment method is not supported in the customer's environment (for example, Apple Pay on a non-Apple device), the page falls back to showing the default set of available methods.

## Payment method specific options

Some payment methods have additional configuration options that can be set within their respective objects in the `paymentMethods` array.

{% hint style="info" %}
The `paymentMethods` array is also used to [show saved credit cards](https://developers.hyp.co.il/enterprise/changing-the-default-payment-page-appearance/showing-saved-credit-cards.md).
{% endhint %}

### Pay By Link (ipr)

When using [Pay By Link](https://developers.hyp.co.il/enterprise/available-payment-options/pay-by-link.md), you can use the `autoSubmit` property. If set to `true`, the payment page will automatically trigger the sending of the payment link SMS as soon as the page loads. This requires a phone number to be pre-populated in the request.

```json
{
  "type": "ipr",
  "autoSubmit": true
}
```

### Gift cards (gcs)

Gift cards support several customization options, such as limiting the number of gift cards used in a single transaction or restricting which providers are allowed. For more details on these options, see the [Gift Cards](https://developers.hyp.co.il/enterprise/available-payment-options/gift-cards.md) documentation.


---

# 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/changing-the-default-payment-page-appearance/managing-payment-methods.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.
