fix: refactored exposed apis

[Shivam25092001]

FIXED

• exposed apis

CHANGED:

import { HyperInit } from '@juspay-tech/react-native-hyperswitch';
HyperInit(publishableKey, profileId)

const hyperElementsOptions: HyperElementsOptions = {
    clientSecret: clientSecret ?? undefined,
    sdkAuthorisationForPayments: sdkAuthorisation ?? undefined,
  };
<HyperElements hyper={hyperPromise} options={hyperElementsOptions}>
        <PaymentWidget
          widgetId="payment-widget"
          onPaymentResult={(result: any) => {
            console.log('Payment Result from Widget:', result);
            if (result.errorMessage) {
              setStatus(`Payment failed: ${result.errorMessage}`);
              setMessage(null);
            } else {
              setStatus(getStatus(result?.status));
              setMessage(result?.status);
            }
          }}
          style={{ width: '100%', height: 400 }}
          options={{ 
            ...getCustomisationOptions('accordion'), 
          }}
        />
</HyperElements>

Deprecated useHyper and HyperProvider

IMPLEMENTATION

• HyperInit stores the global variables in a global context.
• HyperElement resolves the hyperPromise and internally initailizes the nativeModule with pk_key and other configs (internally initializing the PaymentSession object on native layer).
• PaymentWidget presents the widget using the clientSecret.

[Copilot]

Pull request overview

Refactors the public React Native Hyperswitch SDK surface to a new initialization + context model (HyperInit + HyperElements) and introduces a widget-oriented hook (useWidget), while updating the example app accordingly and removing the prior useHyper / HyperProvider exports.

Changes:

• Added new core APIs: HyperInit (returns a hyper instance promise) and HyperElements (context provider).
• Updated PaymentWidget to pull clientSecret from HyperElements context; removed clientSecret/sdkAuthorisation from PaymentSheetConfiguration.options.
• Added useWidget hook and new exported TS types; updated example app to use HyperInit + HyperElements.

Reviewed changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 10 comments.

Show a summary per file

File	Description
packages/@juspay-tech/react-native-hyperswitch/src/views/PaymentWidget.res	Reads clientSecret from HyperElements context and passes it to the native widget.
packages/@juspay-tech/react-native-hyperswitch/src/types/PaymentSheetConfiguration.res	Removes clientSecret / sdkAuthorisation from payment sheet options.
packages/@juspay-tech/react-native-hyperswitch/src/types/NativeModuleTypes.res	Updates comment; keeps native widget prop types.
packages/@juspay-tech/react-native-hyperswitch/src/types/HyperTypes.res	Introduces new exported types for hyper instance, context data, and widget controller.
packages/@juspay-tech/react-native-hyperswitch/src/modules/NativeHyperswitchSdk.res	Changes native module types and adds new method signatures.
packages/@juspay-tech/react-native-hyperswitch/src/index.tsx	Re-exports new API surface; removes old exports.
packages/@juspay-tech/react-native-hyperswitch/src/hooks/useWidget.res	Adds new useWidget hook + legacy wrapper.
packages/@juspay-tech/react-native-hyperswitch/src/hooks/useHyper.res	Comments out legacy hook implementation (effectively removed).
packages/@juspay-tech/react-native-hyperswitch/src/core/HyperElements.res	Adds context provider responsible for initialization + holding clientSecret/sdkAuthorisation.
packages/@juspay-tech/react-native-hyperswitch/src/core/Hyper.res	Adds Hyper.init producing a hyperInstance and storing global config.
packages/@juspay-tech/react-native-hyperswitch/src/context/HyperProvider.res	Comments out legacy provider implementation (effectively removed).
example/src/PaymentScreen.tsx	Migrates example to HyperElements + widget flow.
example/src/App.tsx	Migrates example initialization to HyperInit.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

initPaymentSessionParams includes sdkAuthorisation, but useWidgetLegacy.initPaymentSession ignores it and nativeHyperswitchSdk.initPaymentSession only receives paymentIntentClientSecret. This is misleading for API consumers: either remove sdkAuthorisation from the params type / legacy hook, or change the flow so the SDK authorisation is actually applied (e.g., via HyperElements/native init).

Suggested change

	nativeHyperswitchSdk.initPaymentSession(~paymentIntentClientSecret=params.paymentIntentClientSecret->Option.getOr(""))->Promise.then(result => {
	nativeHyperswitchSdk.initPaymentSession(
	~paymentIntentClientSecret=params.paymentIntentClientSecret->Option.getOr(""),
	~sdkAuthorisation=params.sdkAuthorisation->Option.getOr(""),
	)->Promise.then(result => {

[Shivam25092001]

will change in upcoming PRs

[Shivam25092001]

@manideepk90 working on updateIntent feature might need this

[Shivam25092001]

TO check if web is making this a default export

[Shivam25092001]

loadHyper is a named import in hyperswitch-web, so keeping parity here, keeping as a named import.

[Shivam25092001]

rename to Hyperswitch

[Shivam25092001]

remove clientSecret flow completely

[Shivam25092001]

This will need client-core changes

[Shivam25092001]

move this call to HyperInit