QR codes are prevalent in making a better user experience for wallets throughout the payments ecosystem. However, there is no community standard defining how QR codes should be utilized within wallets, and what the expected interaction is for using them between different wallets.
There are a few cases that we think are important to address (at least to start):
Converting a QR code to a payment address, such that when a user scans someone else's QR code they don't have to input any additional information about the recipient of a transaction.
Invoice QR Codes: The ability to send an invoice (request for payment) to another user via a QR code, and when a user scans it, it pre-populates an entire transaction ready for signature.
SEP-0007 QR Codes: QR codes that encode SEP-0007 URIs to be scanned by a user in order to sign a transaction.
Closing this out to clean up my created issues across Github open source repos that are no longer relevant to me. If this is still an issue, please make a new issue to represent it.
QR codes are prevalent in making a better user experience for wallets throughout the payments ecosystem. However, there is no community standard defining how QR codes should be utilized within wallets, and what the expected interaction is for using them between different wallets.
There are a few cases that we think are important to address (at least to start):