Should the PaymentRequest ID be passed to canMakePayment?
Open
Nobody has claimed this yet.
Future Candidate Feature
proposal - needs discussion
- Dominant language
- HTML
- Stars
- 510
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
While experimenting with payment handlers we have found the desire to do waterfall logging. In the current specification we have no way to correlate canMakePayment with the payment request event. I can see this being valuable data, should it be provided to the payment handler?
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 definitions for canMakePayment and the payment request event described in the issue. Determine whether passing a PaymentRequest ID can support waterfall logging without changing the intended API model; done means the specification change and its interaction with payment handlers are decided.
Written by the indexing model from the issue text.
Assessment
- Domain
- payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100