Skip to main content
Jupico provides ready-to-use web components for Apple Pay and Google Pay, so you can offer one-tap wallet checkout without handling sensitive payment data. You embed the same script bundle used for card and bank account tokenization, configure the wallet options in your authorization session, drop in the component tag, and wire up a single callback. Jupico handles merchant validation, presents the native payment sheet, and returns a tokenized result to your callback for backend processing.

Apple Pay (<apple-pay-jupico>)

The Apple Pay component renders the native Apple Pay button, handles merchant validation with Apple’s servers, presents the Apple Pay sheet on user tap, and fires your callback with a tokenized payment result when the customer confirms.

Prerequisites

Before the Apple Pay component will display, make sure you have:
  • A page served over HTTPS
  • Your domain registered for Apple Pay on the Web
  • A customer on an eligible device and browser (Safari on iOS or macOS with Wallet configured)

Required properties

Enable Apple Pay in your authorization session

Include the applePay configuration in your backend authorization session call to activate the Apple Pay component:

Set up the component

The Apple Pay button only appears on eligible Apple devices and browsers (Safari on iOS or macOS) where the customer has Wallet configured. On all other devices and browsers, the component renders nothing. Plan your checkout layout to accommodate this gracefully.
Apple requires a user gesture (such as a button tap) to open the Apple Pay payment sheet. The component handles this requirement automatically — do not attempt to trigger the sheet programmatically on page load.

Google Pay (<google-pay-jupico>)

The Google Pay component renders the native Google Pay button, triggers the Google Pay payment sheet when the customer clicks, and fires your callback with a tokenized result on completion.

Required properties

Enable Google Pay in your authorization session

Include the googlePay configuration in your backend authorization session call to activate the Google Pay component:

Set up the component


Authorization session configuration for wallets

To enable both Apple Pay and Google Pay together, include both configurations in a single authorization session call. Pass the returned sessions object to both wallet components — and to any card or eCheck components on the same page.

Handling the transaction-complete callback

Both wallet components invoke transaction-complete when the payment sheet closes. The event object indicates whether the payment succeeded, the customer cancelled, or an error occurred. Inspect the event in your callback and forward a successful token to your backend for processing.
Wallet components use the same sessions object as the <tokenization-form> and <echeck-form> components. Create one authorization session per payment page, enable each payment method you need in the session configuration, and pass the single sessions object to every component on the page.
Last modified on July 15, 2026