> ## Documentation Index > Fetch the complete documentation index at: https://developers.circle.com/llms.txt > Use this file to discover all available pages before exploring further. # Web SDK > Set up the client-side web SDK for user-controlled wallets in your web application. The Circle Web SDK enables user-controlled wallets within your web application. Three authentication methods are supported, namely **social logins**, **email**, or **PIN**, which includes security questions for recovery. This allows you to authenticate your users in a seamless way and create user-controlled wallets for them. By integrating this client-side SDK, your users can securely create wallets and make transactions using social accounts or email. If you choose the PIN authentication method, your users can input sensitive data, like PINs or security answers, in a secure way. Moreover, the SDK encrypts the request body sent by the application, protecting your users' information. **Note:** The Web and Mobile SDKs preserve the user keyshare with the individual, giving them complete control. You must use the SDKs with the user-controlled wallet product. Additionally, the Web and Mobile SDKs support only the user-controlled wallet product. At Circle, we understand the importance of end-to-end security for your application and the need to create a tailored and seamless user experience for your end-users. Hence, Circle's SDK also exposes functionality for you to customize the description and layout. See the [Web SDK UI Customization API](/sdks/user-controlled/web-sdk-ui-customizations) article to customize the SDK. ## Install the SDKs Install using [npm](https://docs.npmjs.com/about-npm): ```shell Shell theme={null} npm install @circle-fin/w3s-pw-web-sdk ``` ## SDK architecture You must use Web, iOS, or Android SDKs to access the user-controlled Programmable Wallet product. The SDK secures, manages, and communicates with your server to ensure your user's keyshare, always stays with them and is not exposed to your servers. To learn more, see [How it works](/sdks/user-controlled/overview#how-it-works). ## SDK API references: enums The Web SDK supports the API reference enums listed in the following sections. ### ChallengeType Enumerates the types of challenges supported. ```javascript JavaScript theme={null} enum ChallengeType { INITIALIZE, SET_PIN, RESTORE_PIN, CHANGE_PIN, SET_SECURITY_QUESTIONS, CREATE_WALLET, CREATE_TRANSACTION, ACCELERATE_TRANSACTION, CANCEL_TRANSACTION, CONTRACT_EXECUTION, SIGN_MESSAGE, SIGN_TYPEDDATA, SIGN_TRANSACTION, WALLET_UPGRADE, UNKNOWN, } ``` ### ChallengeStatus Enumerates the possible status for a challenge. ```javascript JavaScript theme={null} enum ChallengeStatus { COMPLETE, EXPIRED, FAILED, IN_PROGRESS, PENDING, } ``` ### QuestionType Enumerates the types of security questions. ```javascript JavaScript theme={null} enum QuestionType { DATE, TEXT, } ``` ### ErrorCode Enumerates the types of error code. ```javascript JavaScript theme={null} enum ErrorCode { unknown = -1, success = 0, apiParameterMissing = 1, apiParameterInvalid = 2, forbidden = 3, unauthorized = 4, retry = 9, customerSuspended = 10, pending = 11, invalidSession = 12, invalidPartnerId = 13, invalidMessage = 14, invalidPhone = 15, userAlreadyExisted = 155101, userNotFound = 155102, userTokenNotFound = 155103, userTokenExpired = 155104, invalidUserToken = 155105, userWasInitialized = 155106, userHasSetPin = 155107, userHasSetSecurityQuestion = 155108, userWasDisabled = 155109, userDoesNotSetPinYet = 155110, userDoesNotSetSecurityQuestionYet = 155111, incorrectUserPin = 155112, incorrectDeviceId = 155113, incorrectAppId = 155114, incorrectSecurityAnswers = 155115, invalidChallengeId = 155116, invalidApproveContent = 155117, invalidEncryptionKey = 155118, userPinLocked = 155119, securityAnswersLocked = 155120, notEnoughFunds = 155201, notEnoughBalance = 155202, exceedWithdrawLimit = 155203, minimumFundsRequired = 155204, invalidTransactionFee = 155205, rejectedOnAmlScreening = 155206, tagRequired = 155207, gasLimitTooLow = 155208, transactionDataNotEncodedProperly = 155209, fullNodeReturnedError = 155210, walletSetupRequired = 155211, lowerThenMinimumAccountBalance = 155212, rejectedByBlockchain = 155213, droppedAsPartOfReorg = 155214, operationNotSupport = 155215, amountBelowMinimum = 155216, wrongNftTokenIdNumber = 155217, invalidDestinationAddress = 155218, tokenWalletChainMismatch = 155219, wrongAmountsNumber = 155220, walletIsFrozen = 155501, maxWalletLimitReached = 155502, walletSetIdMutuallyExclusive = 155503, metadataUnmatched = 155504, userCanceled = 155701, launchUiFailed = 155702, pinCodeNotMatched = 155703, insecurePinCode = 155704, hintsMatchAnswers = 155705, networkError = 155706, invalidUserTokenFormat= 155718, walletIdNotFound = 156001, tokenIdNotFound = 156002, transactionIdNotFound = 156003, entityCredentialNotFound = 156004, walletSetIdNotFound = 156005, } ``` ## SDK API references: interfaces The Web SDK supports the interfaces listed in the following sections. ### Configs * `appSettings` [\](#appsettings) Application settings object * `authentication` [\](#authentication) Authentication object * `socialLoginConfig` [\](#loginconfigs) Social login configuration object ### AppSettings Holds application settings. * `appId` [\](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Data_structures#string_type) Application ID, retrieved from Circle Developer Services Console ### Authentication Holds authentication information. * `userToken` [\](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Data_structures#string_type) User token * `encryptionKey` [\](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Data_structures#string_type) Encryption key ### LoginConfigs Holds login configuration information. * `google` [\