@ianbjacobs wrote: > The browser implements Payment Request API but not Payment Method Manifest I've addressed this issue in this pull request by checking whether [Payment Method Manifest](https://w3c.github.io/payment-method-manifest/) spec is implemented. In this case, payment handlers can use all [standardized payment method identifiers](https://www.w3.org/TR/payment-method-id/#dfn-standardized-payment-method-identifier), but as for [URL-based payment method identifiers](https://www.w3.org/TR/payment-method-id/#dfn-url-based-payment-method-identifier), the [origin](https://tools.ietf.org/html/rfc6454) of the identifier must be equal to the [origin](https://tools.ietf.org/html/rfc6454) of the [service worker registration](https://www.w3.org/TR/service-workers-1/#service-worker-registration-concept) [scope URL](https://www.w3.org/TR/service-workers-1/#dfn-scope-url). -- 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-handler/pull/197#issuecomment-320003972
Received on Thursday, 3 August 2017 15:29:44 UTC