w3c / w3c/payment-request

Pre-calculate shipping costs for available addresses

Open
#615 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Future Candidate Feature proposal - needs discussion
Dominant language
HTML
Stars
510
Forks
139
PR merge metrics
No merged PRs in 30d

Description

Use case: the user has 2 or more address they can ship to. The merchant would like to pre-calculate the shipping costs and ideally pre-sort the addresses by cost.

To prevent accessing PII without the user's knowledge, the UA could provide only partial addresses (e.g. Country + zip/postal code) upfront, based on which the merchant could still calculate costs.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Payment Request API's existing shipping-address and shipping-cost flows, then compare them with the use case described here. Done would require a decided API design for pre-calculating costs across available addresses while limiting address data exposure, along with corresponding specification changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
api, payments
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.