Wallets and Privy

SDK UI owns the customer wallet step after checkout opens. The merchant payment button should remain an entry point and should not expose wallet initialization or connection state.

Privy in React

Use a Privy application owned by the merchant, then pass the SixPay wallet adapter to session-backed SDK UI:

import { PrivyProvider } from '@privy-io/react-auth';
import { SixpayCheckoutModal } from '@sigworld/sdk-ui';
import { usePrivyWallet } from '@sigworld/sixpay-wallet';

function Checkout({ session }: { session: { id: string; checkoutToken: string } }) {
  const walletAdapter = usePrivyWallet();
  return <SixpayCheckoutModal
    checkoutSessionId={session.id}
    checkoutToken={session.checkoutToken}
    walletAdapter={walletAdapter}
  />;
}

SDK UI’s Change wallet action reopens Privy’s chooser. Customers can select an embedded wallet, an external wallet, or a different account of an external wallet.

Privy embedded wallets require HTTPS. The React adapter is a hook package and is not for a plain script-tag integration; browser bundles use their injected-wallet flow.

Overview

Get started

Build checkout

Operate

Reference

Privy in React

​Privy in React

Privy in React