“The survey found 98 percent of respondents considered mobile payment as the most commonly used payment method, up 5 percentage points from a year earlier. The proportion of people who paid by scanning QR codes reached 85 percent, up 6 percentage points from 2019.”
Takeaway: I’m not good at reading standards. I’m also not sure how well this binary data format applies to non-card based, cryptocurrency payment transactions which don’t have the same data elements or requirements like an acquirer.
Would it make sense for us to introduce a “fio:” or “fioprotocol:” prefix to let an application know they are to interact with the FIO chain to do a look up on the fio address and from that, construct a resulting standard url?
Should we have a service endpoint which does this automatically?
This could be a new endpoint in the API (so all BPs would be running it) which converts this information and redirects to a standard “ethereum:” or “bitcoin:” uri according to the existing specifications.