The benefit of this Payment Link scheme over the EPC QR scheme is that: (a) Both of these QR codes can be scanned with your bank app (b) Only the Link can be scanned with your default camera app (c) Only the Link can be shared in a message or typed into a browser
The callback needs to be verified though, which we can do through a combination of: (a) The unique key (which transaction) (b) HTTP Signatures (correct server) (c) Bank account number to domain name mapping maintained by the central directory (server is a bank)
-
-
URL maximum is 2048 characters, but they are preferably shorter than that to generate easy to scan QR codes. Every parameter has a preferred long-form and optional short-form: type = t receiver_name = rn receiver_identifier = ri sender_identifier = si recur_frequency = rf
Show this thread -
And we can even merge some variables: ¤cy=EUR &amount=9.50 is shortened as &a=EUR9.50
Show this thread -
What else should we consider for a light-weight, permissionless payment request link scheme?
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
at
retweets