Digital Wallets

Hyp currently supports all three major digital wallets used in Israel: Apple Pay, Google Pay, and bit.

Here's what the payment page looks like when all three are enabled:

Payment page with all three digital wallets enabled

The following sections describe prerequisites, implementation guidelines, and payment experience for each digital wallet.

Note that for all digital wallet transactions, the card number Hyp receives and passes to the merchant is not the actual credit card number but a token generated by the digital wallet provider. These tokens are typically single-use, transaction-specific, and not reusable. Do not store them or rely on them in business logic such as reporting, analytics, duplicate detection, or customer identification, as they do not consistently represent the same customer or card. Instead, use stable identifiers such as transaction IDs provided by Hyp, your internal customer IDs, or order references for such purposes.

Google Pay

Prerequisites

Contact your Hyp representative to have Google Pay enabled in your terminal.

Payment page integration

As soon as Google Pay is enabled in your terminal, the Google Pay button will show on your payment pages by default, without any extra effort, unless you have chosen to hide this payment method.

Note that Google Pay is only available on supported devices.

Payment experience

Here's what the Google Pay payment button looks like on the payment page:

Google Pay button

When the button is clicked, a modal pop-up displays, and the underlying payment page is grayed out:

Google Pay modal pop-up

When the customer has selected a payment method saved in Google Pay and clicked Pay in the pop-up, the pop-up closes, the payment page becomes active again and displays the two remaining fields to fill out, which are CVV and Personal ID:

CVV and personal ID entry

When the customer has filled out the fields and clicked Pay, the transaction is processed, followed by displaying either the success or the error page.

This works exactly the same whether you use a full-page redirect or display the payment page in an iframe.

Apple Pay

Prerequisites

Contact your Hyp representative to have Apple Pay enabled in your terminal.

Payment page integration

Integrating Apple Pay differs depending on whether you use the full-page redirect or display the payment page in an iframe.

If you're using the full-page redirect, then as soon as Apple Pay is enabled in your terminal, the Apple Pay button will show on your payment pages by default, without any extra effort, unless you have chosen to hide this payment method.

To integrate Apple Pay in iframe-based payment pages, you need to complete a few extra steps:

1. Make sure that your merchant website meets these Apple requirements for TLS and specific ciphers used by your TLS implementation.

2. In your web server's root folder, create a subfolder called .well-known, and add this merchant association file to the subfolder. The file should be available from your merchant website's domain via this URL: https://your-merchant-website.com/.well-known/apple-developer-merchantid-domain-association.

3. Contact your Hyp representative and request them to complete the Apple Pay registration process.

4. Add a script to the page that embeds the payment page iframe. The script URL needs to be different for the testing and production environments:

   1. For testing: <script src="https://ppsuat.creditguard.co.il/plugins/applePayOnIframe.js"></script>

   2. For production: <script src="https://pps.creditguard.co.il/plugins/applePayOnIframe.js"></script>

Note that Apple Pay is only available on supported devices.

Payment experience

Here's what the Apple Pay payment button looks like on the payment page:

Apple Pay button

When the customer clicks the Apple Pay button, the payment page displays an additional required field for Personal ID:

Personal ID field

After entering a personal ID and clicking Pay, the customer sees the Apple Pay overlay where they can select a payment card and confirm the payment:

Apple Pay overlay

Upon confirming the payment, transaction processing occurs, followed by displaying either the success or the error page.

bit

bit is the leading Israeli digital payment network that you can enable on your payment pages with very little effort.

Prerequisites

Contact your Hyp representative and ask them to perform the two steps required to enable bit in your payment pages:

1. Open a bit payment account.

2. Enable bit payments in your terminal.

Payment page integration

As soon as bit is enabled in your terminal, the Pay with bit button will show on your payment pages by default, without any extra effort, unless you have chosen to hide the bit payment method.

Payment experience

Here's what the bit payment button looks like on the payment page:

bit payment button

After clicking bit, the payment page displays two required fields for bit customer name and Israeli phone number. The latter only accepts Israeli phone numbers in the short format, without the country code.

bit-specific fields

When the customer clicks the bit button, the payment page displays a bit overlay with a QR code that the customer can scan with their bit application to perform the payment. The QR code expires after 9 minutes:

bit QR code

As soon as the customer has performed the payment in their bit application, the payment page redirects to either the success or error page.

If the customer has not been able to perform the payment in their bit application, the bit overlay expires, and the customer can either start again or choose a different payment method.

Considerations

• For transactions exceeding ₪5000, which is the maximum amount allowed by bit, the Pay with bit button will not show on the payment page.

• bit does not support installments. If your payment page is configured to allow multiple installments and the customer has selected the number of installments other than 1, then if bit is used for payment, the payment QR code will use the full amount despite the selection.

• bit does not provide a test environment. Keep this in mind when testing digital wallet payments. If you proceed with a charge in testing, you'll need to contact bit directly to cancel the transaction.

• bit has transaction limits: see this document for more information.

• You can optionally change the redirect behavior on mobile devices after completing a payment made via the bit application.

Troubleshooting

If you encounter errors relating to the top-level browser context or general iframe issues, please try the following workaround:

• Add the allow=payment attribute to your iframe — see this guide.

• Add the allowPaymentRequest property explicitly — see this guide.