Adding custom fields next after shipping options have been added.
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 510
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
Some ecommerce sites require extra fields with the shipping details other than the address they are sending to. E.G;
- Type of residence
- Instructions to the delivery driver
- Notes to the merchant
Ideally having an empty text field, which could be populated by the user would work in most cases. Or adding a drop down.
The reason for doing this in the PR API rather than on the merchants site, is the UX flow would seem broken to partially ask for some delivery details on the merchants site and others in the PR API.
The other alternative is to ask for all delivery details on the Merchant side, but this begs the question of why using PR API in the first place when all you are asking is credit card details.
This was originally filed as a chrome bug, moved here for discussion
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 by reading the issue discussion and the linked Chromium bug, focusing on the proposed custom fields and the UX constraints around shipping details. Done would require an agreed Payment Request API design for user-entered or selectable merchant-defined fields, with its scope and behavior resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100