Question 1.
The app we are serving is a hybrid app (APP + Mobile Web) that operates web view from the inside.
Apply React SDK (Web SDK) provided by web3auth to this app to connect the metamask wallet
We have implemented a service that transmits tokens, and the connection of metamask wallets goes well.
However, there is no confirmation request with a metamask when sending tokens, is there a solution?
Question 2.
The ‘wallet service’ provided by your company is when sending tokens after connecting to the metamask
Does the confirmation request from hybrid app (APP + Mobile Web) to metamask work well like the purpose of ‘Question 1’?
Or does the metamask confirmation request work in a different way provided by your company?
Question 3.
When using the ‘wallet service’ provided by your company
Logo, use of each function, color, button name, etc., as if it were our service
I want to provide it to users, what is the UI changeable item or scope?
Thank you for your detailed questions! Here’s a summary of your queries and some guidance for each:
Context from your message:
SDK Used: Web3Auth Plug and Play (PnP) Web SDK for React (with Modal)
Platform: Hybrid App (APP + Mobile Web, using WebView)
Integration: Connecting to MetaMask via Web3Auth, sending tokens
Issue: No MetaMask confirmation prompt on token transfer
1. MetaMask Confirmation Not Appearing on Token Transfer
Summary:
You’re using Web3Auth’s React SDK in a hybrid app to connect MetaMask. While wallet connection works, sending tokens does not prompt a confirmation in MetaMask.
Possible Reasons & Guidance:
In a hybrid app (especially inside a WebView), MetaMask extension/injection may not be available as it is in a desktop browser.
Web3Auth Modal SDK, when running in a WebView, can only interact with MetaMask if MetaMask Mobile is installed and deep linking is supported, or if WalletConnect is used as a bridge.
If you’re not seeing a MetaMask confirmation, it is likely because the transaction is being signed by the private key managed by Web3Auth (not by MetaMask), or the MetaMask connection is not being properly routed in the mobile context.
Action Items:
Please clarify: Are you using WalletConnect to connect to MetaMask Mobile, or are you expecting browser extension behavior in the WebView?
If you can share your Web3Auth initialization and login code snippets, it will help us confirm your setup.
2. Web3Auth “Wallet Service” and MetaMask Confirmation
Summary:
You’re asking if Web3Auth’s wallet service provides MetaMask-like confirmation prompts when sending tokens.
Clarification:
If you use Web3Auth’s embedded wallet (i.e., the private key managed by Web3Auth), transactions are signed directly in-app and there is no MetaMask confirmation prompt.
If you connect to external wallets (like MetaMask via WalletConnect), the confirmation should appear in the MetaMask app.
The behavior depends on whether the transaction is being routed through an external wallet (MetaMask) or the in-app wallet managed by Web3Auth.
Full customization of wallet UI (beyond the modal) is limited if you use the default modal; for deeper customization, you may need to use the Web3Auth NoModal SDK and build your own UI.
Next Steps / Info Needed
To help further, could you provide:
Are you using WalletConnect to link MetaMask Mobile, or just the in-app Web3Auth wallet?
Your Web3Auth initialization and login code snippets (if possible)
Any error messages or browser console logs/screenshots (if you see any)
This will help us pinpoint the exact issue with MetaMask confirmations in your hybrid app.
Let us know the above details, and we’ll help you resolve this quickly!
Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.
Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours