Ship Mode Update for PO BOX
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 510
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
Here's an issue I am running into with Payment Request in regards to PO Boxes and Ship Modes.
We have 3 Standard Ship Modes that user can select from:
Overnight - $30
Express - $18
Standard - Free
We can calculate shipping modes based on State and update accordingly.
User in this case selects Standard Ship Mode.
For users with a PO Box as shipping address, we only offer one ship mode which is unique to PO Box.
Unique Shipping - $25
The change here would affect total cost of product with shipping and would need to notify user that ship mode has been updated to reflect PO Box address.
We have limited ship modes for users with PO BOX as shipping address. But, since addressLine is not exposed until user commits to payment, how would Payment Request handle this case?
Would we use the retry method and throw an error and advise user to select the updated ship mode?
https://www.w3.org/TR/payment-request/#retry-method
cc @rsolomakhin
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.
Research direction
Start with the Payment Request API retry method and the addressLine exposure limitation described in the issue. Define whether PO Box detection can change shipping options after payment commitment, and specify the expected retry, error, and user-notification behavior so the issue has an implementable, testable outcome.
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
- Needs clarification
- Newbie friendliness
- 22/100