address? | string | the address of the wallet to automatically link | - | types.ts:135 |
chain? | string | number | The network of the wallet to automatically link | - | types.ts:139 |
client_id | string | the authentication flow client id of the application | PKCERequestShared.client_id | types.ts:109 |
code_challenge | string | the code challenge automatically generated by the SDK | PKCERequestShared.code_challenge | types.ts:113 |
code_challenge_method | "S256" | the code challenge method for the authentication flow , handled by the SDK | PKCERequestShared.code_challenge_method | types.ts:115 |
email? | string | the email of the user to prefill the login form | - | types.ts:131 |
redirect_uri? | string | the redirect uri of the application | PKCERequestShared.redirect_uri | types.ts:111 |
response_type | "code" | the response type of the authentication flow, handled by the SDK | - | types.ts:129 |
scope? | string | @deprecated: will be removed, the scope of the application | - | types.ts:133 |
signature? | string | the signature of the wallet to automatically link | - | types.ts:137 |
skip_create_account? | boolean | You can skip the connect wallet and request IBAN steps in the Authorization Flow and use the Link Address and Request IBAN API endpoints after you have gotten the authorization | - | types.ts:141 |
skip_kyc? | boolean | You can skip the KYC onboarding steps in the Authorization Flow and use the the details, additional data, and verifications API endpoints after you have gotten the authorization. | - | types.ts:143 |
state? | string | the state of the application | PKCERequestShared.state | types.ts:117 |