Google Pay & Apple Pay Element
The Google Pay & Apple Pay Element provides a unified wallet payment component for collecting payments through the supported native wallets. Render this element to present the appropriate wallet optio
The Google Pay & Apple Pay Element provides a unified wallet payment component for collecting payments through the supported native wallets. Render this element to present the appropriate wallet option based on the user's device and platform.
Use the wallet buttons when all of these are true:
You are building a custom checkout UI (Elements). If you use
presentPaymentSheet, wallets already appear inside the sheet — don't add these buttons too.You want one-tap express payment at the top of your checkout (best conversion), instead of making users fill the card form.
The wallet is actually relevant for the device:
ApplePayButton→ iOS only (requires a real device — Apple Pay does not run on the iOS Simulator).GooglePayButton→ Android only.
The wallet is enabled for this payment: the connector must be configured on your Hyperswitch dashboard (Apple Pay / Google Pay enabled + merchant certificates set up) and the payment method must be returned for the intent.
Find the Demo App
Find the demo app here
1. Basic Usage
1.1 Install the react native sdk
npm install @juspay-tech/react-native-hyperswitch
# or
yarn add @juspay-tech/react-native-hyperswitch1.1.1 Install Peer Dependencies
The SDK requires the following peer dependencies to be installed in your project:
1.2 Initialize Hyperswitch
Initialize Hyperswitch once using your publishable key and profile ID. Reuse the same initialized instance throughout your application.
Keep the Hyperswitch secret API key on your backend only. The app should never handle it.
1.2 Get sdk_authorization from your Backend
Call your payment-creation endpoint. Its JSON response must contain sdk_authorization.
1.3 Wrap your app with HyperElements
To use HyperSwitch hooks and the Embedded UI in a React Native application, wrap your payment screen with the HyperElements component. During initialization, you must provide the required sdkAuthorization prop to HyperElements. This authorization is necessary for the SDK to initialize correctly.
1.4 Pick per platform:
1.5 Render the button (always mounted).
Never conditionally unmount it — if it's not mounted, it can't tell you whether the wallet is available:
1.6 Handle the result:
Congratulations! 🎉 You have successfully integrated the One-Tap Wallet Element into your application.
Differences
Confirmation
Automatic on sheet approval
You call confirmPayment(...)
Platform
iOS-only / Android-only
Both platforms
Result
via onPaymentResult prop
via onPaymentResult or confirmPayment return
That's it — the wallet buttons are fully self-driving: mount, wait for PAYMENT_METHOD_STATUS, handle onPaymentResult.
Last updated
Was this helpful?

