Split shipping address from Payment Request API 1.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Read the Payment Request API 1.0 specification sections linked in the issue, then review related issue #842 and payment-handler issue #337. The proposed outcome is a resolved decision about separating shipping-address behavior for a future iteration, but the issue does not identify files, tests, or an implementation-ready scope.
Written by the indexing model from the issue text.
Description
Payment Request API currently specifies a standardized interface for merchants to request shipping and contact information from payment methods. However, Basic-Card is the only payment method that supports this interface. The two other payment methods in production, Apple Pay and Google Pay, both implement shipping and contact information collection via method-specific data. Other payment app developers have also requested shifting the collection of such information from the browser to the payment apps.
On the other hand, shipping address is a sensitive piece of personally identifying information of the user. It has been pointed out (e.g. #842) that any interface for collecting shipping address should support richer negotiation to avoid unnecessary collection of user information.
Given the lack of developer interest for the browser to provide shipping address, and the significant development effort involved to fully implement #842, I'd like to propose that we split out the shipping address related behaviors from Payment Request API 1.0 and to be considered in a future iteration of Payment Request API.
- Dominant language
- HTML
- Stars
- 510
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from w3c/payment-request
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
w3c/payment-request#1076 · 5 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
w3c/payment-request#1075 · 7 comments · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
w3c/payment-request#1072 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
w3c/payment-request#1071 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
w3c/payment-request#1064 · 2 comments ·
All issues in w3c/payment-request
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·