Adding blinks support for QR scanning wallets
Summary
Browser wallets like Phantom support blinks by reading a URL and rendering data received back. For example, displaying options for the user to pick from, entering an amount, etc… before submitting the transaction.
What would be good, is if this same flow and UX was initiated by wallets scanning a blink url (outside the context of any existing site or social media like X).
Flow:
- mobile wallet scans a blink URL
- the URL returns data such as options for the user to select
- the wallet renders the options (same as it does in X for blink) and allows the user to input some data and/or make selections
- the user then submits the transaction
Simple Use Case:
User-selected payment method. The simple scenario that we’d like to build goes like this:
- merchant displays a blink as a QR code
- mobile app scans the the code and submits the initial GET request
- the action provider returns a series of payment options (USDC, USDT, BONK, etc…)
- the wallet renders the options for the user to select from
- user/wallet selects an option and submits the returned transaction
This would greatly improve the flow and UX, as right now the merchant has to select the payment currency before generating the QR code to scan.
One ideal improvement here would be the ability to submit the wallet pubkey in the initial GET request so that the action provider could respond back with actual available options instead of blindly returning selections that may or may not be available to the user. Pretty obvious though, and I know it’s already been mentioned by a lot of folks.