List other URL-based payment method identifiers

[jyasskin]

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/Payment_Request_API/Concepts

What specific section or headline is this issue about?

URL-based payment method identifiers

What information was incorrect, unhelpful, or incomplete?

This section only lists https://apple.com/apple-pay and https://google.com/pay as options.

What did you expect to see?

I'm told that at least a couple other URLs work. It would be good to find and list them, or explain how developers can discover them.

cc/ @stephenmcgruer who might have some more breadcrumbs toward the right thing to write here.

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

MDN metadata

Page report details

• Folder: en-us/web/api/payment_request_api/concepts
• MDN URL: https://developer.mozilla.org/en-US/docs/Web/API/Payment_Request_API/Concepts
• GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/api/payment_request_api/concepts/index.md
• Last commit: f2088b8
• Document last modified: 2024-08-04T23:19:14.000Z

[stephenmcgruer]

Some I was able to find (can't track down a public source for PayTm, which is another payment app we are aware of using Payment Request):

• https://developer.phonepe.com/category/v1/mobile-browser-intent/steps-to-integrate-msite-intent/
• https://developer.samsung.com/internet/android/web-payments-integration-guide.html (this may be Samsung internet provider only?)
• https://blog.netcetera.com/smart-checkouts-with-payment-request-api-1884ab5f84e (appears to be a possibly no longer existing demo payment app?)

There's also the use in the Digital Goods API, which is a little different:

• https://learn.microsoft.com/nl-nl/microsoft-edge/progressive-web-apps-chromium/how-to/digital-goods-api

---

That said, I'm not sure that MDN should be listing these, since they're generally provided by the payment app to an integrating merchant, and may change! Not to mention that payment apps generally require a lot more than just a URL (e.g., they'll need you to pass them a merchant token and other transaction information in the data member), so it doesn't seem that useful to document here?

Also, I don't love "This is currently supported only by Chrome and Chromium-based browsers" being documented for https://google.com/pay , as it makes it sound like Google / Google Pay is doing that restriction. Could we extend it to "This is currently supported only by Chrome and Chromium-based browsers, because Payment Request on Safari only accepts Apple Pay" ?

[jyasskin]

My thought was more that MDN should give potential users of the API enough breadcrumbs that they can find how to use it with a variety of handlers, even if doing so requires a contract with a handler instead of just passing in that handler's string.

MDN should also probably point to the ways to be a handler via a native app (e.g. https://web.dev/articles/android-payment-apps-developers-guide), but that would be in a different article.

Re Stephen's last paragraph, maybe "Only Chromium-based browsers support handlers that aren't built into the browser"?

[stephenmcgruer]

My thought was more that MDN should give potential users of the API enough breadcrumbs that they can find how to use it with a variety of handlers, even if doing so requires a contract with a handler instead of just passing in that handler's string.

Ack, that's fair. No strong opposition from me :).

[Josh-Cena]

Welcoming PRs to revise any outdated information and link more resources on other payment methods, but I don't think we want to document their specificities or even to give a list ourselves.