Reclaim InApp SDKsUsage
Verification Options
Customize the default verification flow with Reclaim Protocol's InApp SDKs
Options API
The InApp SDKs provide an setVerificationOptions method to customize the verification flow.
Below are the available options that can be set:
| Prop | Type | Description |
|---|---|---|
useTeeOperator | boolean | null | Enables use of Reclaim's TEE+MPC protocol for HTTP Request claim verification and attestation. When set to true, the verification will use Trusted Execution Environment (TEE) with Multi-Party Computation (MPC) for enhanced security. When set to false, the standard Reclaim's proxy attestor verification flow is used. When null (default), inappsdk decides whether to use TEE based on a feature flag. |
canDeleteCookiesBeforeVerificationStarts | boolean | This is enabled by default. Set false to persist sessions storage for the user. (This will be replaced with canClearWebStorage in an upcoming update) |
canUseAttestorAuthenticationRequest | boolean | Enable the use of authentication request when starting a verification. |
claimCreationType | 'standalone' | 'meChain' | The type of claim creation to use. Defaults to 'standalone'. |
canAutoSubmit | boolean | Whether to automatically submit the proof after generation. Defaults to true. |
isCloseButtonVisible | boolean | Whether the close button is visible in the verification screen. Defaults to true. |
locale | string | null | A language code & Country code for localization that should be enforced in the verification flow. |