Skip to main content
Signing lets users authorize transactions and sign messages or typed data with their embedded wallet’s passkey. Your application can own the action review or use Rhinestone’s review interface to show the prepared payload before approval. The review experience and passkey approval serve different purposes: the review explains what the user is authorizing, while the passkey signs the bound challenge.

​
Choose the review experience

Blind signing keeps the review in your application. You show the recipient, amount, chains, fees, and relevant permissions before requesting approval. Rhinestone prepares the payload without showing a second review screen, then the browser asks the user to approve with their passkey. Clear signing adds a Rhinestone review of the server-prepared action before passkey approval. It can display decoded transfers, approvals, and registered actions, with raw contract calls as a fallback when a safe decode is unavailable. Application-supplied labels are marked as unverified. Clear signing is experimental. Neither option removes passkey approval or changes the account’s credential namespace.

​
Defaults depend on the action

Intent and batch flows use blind signing by default, with clear signing available as an opt-in. In the default app-origin mode, message signing, typed-data signing, and modal signing always show Rhinestone’s review. The clear-signing option does not change those flows. For actions that should run without repeated passkey prompts, use separately authorized session keys.

​
Get started

Start with an initialized embedded wallet client, then choose who owns the review for your transaction flow.