The universal interface for PaymentHandlers is currently defined as browser API's in the Payment Handler API spec. Chrome on Android also supports handlers in the form of Android apps and this interface is defined at the Android OS level. Can you explain in more details how the same APIs and flows would be implemented via BT? Noting that this involves enrolment, and then handling payments. What is the user experience you envisage? How would the origin-based security work? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-request/issues/865#issuecomment-483156255
Received on Monday, 15 April 2019 08:25:00 UTC