You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I’m working on integrating WalletConnect functionality and have a specific use case I’m trying to address:
Is there a way to create a unique WalletConnect URI such that:
The server listens for a new session connection tied to this URI.
Once a wallet connects, the server sends a payment request immediately.
After completing the payment request, the server disconnects the client, making the URI available for the next wallet to connect.
Essentially, I’d like to reuse the same WalletConnect URI to handle one wallet connection at a time, sequentially.
Let me know if this is possible with your API or if you have any recommendations on implementing this functionality.
Thanks in advance for your help! Looking forward to your response.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I’m working on integrating WalletConnect functionality and have a specific use case I’m trying to address:
Is there a way to create a unique WalletConnect URI such that:
Essentially, I’d like to reuse the same WalletConnect URI to handle one wallet connection at a time, sequentially.
Let me know if this is possible with your API or if you have any recommendations on implementing this functionality.
Thanks in advance for your help! Looking forward to your response.
Beta Was this translation helpful? Give feedback.
All reactions