QRs are simple links, typically URLs. To perform any kind of interaction with a 3rd-party system, you need to understand what parameters this system can take as part of a URL and see if it performs the expected use case well. My suggestion is that if you can generate the right use case by typing a URL in a browser, you can also support the same use case via a QR. The QR is not where the challenge is. I hope it helps