# DApp and Web2 integration

This article provides a guide for integrating the SDK into an app which is not a wallet. Signing and minting will be performed by a separate wallet app, which will have to be connected to the SDK. For this task, the SDK uses WalletConnect.

Three main topics will be discussed here:

• Connecting to a wallet
• Checking the verification status of an address
• Initializing a verification flow

Connecting to wallets starts with the WalletConnectManager having to actively listen for peers which will accept our session offer.

WalletConnectManager.startListening()

The WalletConnectManager will keep waiting for new connections and emit the result of the connection event through the sessionState flow. Here's an example for how to collect it.

WalletConnectManager.sessionsState.collect { result ->
    when(result){
        is Resource.Failure -> {
            //The connection failed or it was declined
	    }
		is Resource.Success -> {
            //Successfull connection
			val myWalletSession = result.data
		}
	}
}

The user's wallet can be connected via the following two options:

• Present them a QR code which they can scan to connect
• Rely on the built in intent mechanism to oppen an installed wallet.

The QR Code for WalletConnect is an URI. This URI will change with every attempt at connecting to a wallet, regerdless if it was a succes or not. This is needed to ensure that the system is always ready for new connections. These updates are served on a pendingSessionURI flow. Here's an example how to handle the incoming URI changes:

WalletConnectManager.pendingSessionURI.collect { qrUri-> //String
    //Encode URI as a QR code
    //Set imageView content to the QR code
}

Once the user scans the QR code and accepts the prompt shown by the wallet, the sessionState will emit the successfully established WalletConnectSession, and pendingSessionURI will emit the URI for the next possible connection.

If the wallet that the user wishes to connect to is installed on the same device as the SDK is running on, all thats needed to be done is:

WalletConnectManager.connectWallet()

Once the wallet is launched and the user accepts the connection, sessionState will emit the established WalletConnectSession, and pendingSessionURI will emit the URI for the next possible connection.

Depending on your usecase, there are two options to choose from.

First, if you already obtained the user's wallet address, you can use it to check if they have a valid token or not. With this option you have to provide the chainID on which you want to check, yourself.

In case the user’s wallet address is unknown, you can get a connection through WalletConnectManager to their wallet and use the WalletConnectSession object to ask for their verification status.

When you already have the chain information of the user's wallet, you can use a chain id in CAIP-2 format format to check for a valid token.

val chainId = "eip155:80001"
val hasValidToken = VerificationManager.hasValidToken(
    verificationType = VerificationType.KYC,
    walletAddress = walletAddress,
    chainId = chainId
)

WalletConnectSession contains a blockchain account list (wallet addresses), with all the accounts returned by WalletConnect for the connection with the wallet app. The user should select their address from accounts if there are more than one, otherwise the one available address can be used.

Once we obtained the wallet address, we can call

val hasValidToken = VerificationManager.hasValidToken(
    verificationType = VerificationType.KYC,
    walletAddress = walletAddress,
    walletSession = walletConnectSession
)

The requirements before starting the verification process are that you need to have a WalletConnectSession and a selected wallet address from the available accounts.

val verificationSession = VerificationManager.createSession(
    walletAddress = selectedAddress,
    walletSession = walletConnectSession
)

Summary code