- From: Rouslan Solomakhin <notifications@github.com>
- Date: Thu, 08 Sep 2016 07:52:45 -0700
- To: w3c/webpayments-payment-apps-api <webpayments-payment-apps-api@noreply.github.com>
Received on Thursday, 8 September 2016 14:53:44 UTC
Should we recommend different URLs for apps and methods? For example, `https://alicepay.xyz/app` vs `https://alicepay.xyz/method`. The implication here being that browser will download `https://alicepay.xyz/app/payment-app.json` that defines the AlicePay payment app and `https://alicepay.xyz/method/payment-method.json` that describes the AlicePay payment method. Merchants would need to specify `supportedMethods: ['https://alicepay.xyz/method']`. `https://alicepay.xyz/app/payment-app.json` example: ```js { "short_name": "AlicePay", "icons": [], "payment_methods": ["https://alicepay.xyz/method"], "payment_app_service_worker": "/app/sw.js" } ``` `https://alicepay.xyz/method/payment-method.json` example: ```js { "externally_supported_apps": ["https://alicepay.xyz/app"] } ``` It feels less cool, but is definitely more clear. -- 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/webpayments-payment-apps-api/issues/35#issuecomment-245624008
Received on Thursday, 8 September 2016 14:53:44 UTC