nimiq:pay-NQ02YP68BA760KR3QY9CSF0KLP8QTHB6LTKU?value=25e5 (edited)
We could optionally encode the address as HEX or base64 as well.
The pay- part is optional and is used as the default when omitted.
Just a little sad that the payment request urls are then not web urls that can open up straight in the browser anymore, e.g. to be scanned via a native qr scanner.
We should at least additionally support web+nimiq and register a handler for that via https://developer.mozilla.org/en-US/docs/Web/API/Navigator/registerProtocolHandler
I agree that we need web+nimiq://. Can native apps also add themselves as handler for that?
Most probably.
Let's see whether native qr scanners even try to open such URLs though or just scan them as text.
The ethereum payment url scheme, which we can just co-opt for Nimiq. It's straight forward: https://eips.ethereum.org/EIPS/eip-681
nimiq:pay-NQ02YP68BA760KR3QY9CSF0KLP8QTHB6LTKU?value=25e5(edited) We could optionally encode the address as HEX or base64 as well. Thepay-part is optional and is used as the default when omitted.Just a little sad that the payment request urls are then not web urls that can open up straight in the browser anymore, e.g. to be scanned via a native qr scanner. We should at least additionally support
web+nimiqand register a handler for that via https://developer.mozilla.org/en-US/docs/Web/API/Navigator/registerProtocolHandlerI agree that we need
web+nimiq://. Can native apps also add themselves as handler for that?Most probably. Let's see whether native qr scanners even try to open such URLs though or just scan them as text.