- React
- React Native
When you request a signature or transaction from a user’s embedded wallet from another app, Privy requires the user to explicitly confirm the signature or transaction. This is accomplished by opening a popup to the provider app’s domain, where the user confirms the action in an isolated environment.
signMessage, signTypedData, and sendTransaction methods returned by Privy’s useCrossAppAccounts hooksignMessage, signTypedData, and sendTransaction methods returned by usePrivy except they all require an additional CrossAppWalletOptions object of the following type:The address for the cross-app embedded wallet that you’d like to request a signature/transaction
from.
address you specify in this CrossAppWalletOptions object is not a valid embedded wallet
that has been linked to the current user from a provider app, these wallet methods will error.signMessage
To thesignMessage method returned by useCrossAppAccounts, pass the following parameters:The message the user must sign as a
string.Options for the cross-app embedded wallet, which must include the requested wallet’s address.
signTypedData
To thesignTypedData method returned by useCrossAppAccounts, pass the following parameters:A JSON object that conforms to the EIP-712
TypedData JSON schema.Options for the cross-app embedded wallet, which must include the requested wallet’s address.
sendTransaction
To thesendTransaction method returned by useCrossAppAccounts, pass the following parameters:The transaction request to be sent.
Options for the cross-app embedded wallet, which must include the requested wallet’s address.

