Require user interaction before payment handler response returned

Open
#369 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the linked security consideration pull request #365 and its review at pullrequestreview-394293662, which contain the use cases and initial design ideas. Determine the proposed interaction requirement for payment handler responses and establish the design's completion criteria before implementation.

Written by the indexing model from the issue text.

Description

This issue is the "design" complement to the security consideration pull request:
https://github.com/w3c/payment-handler/pull/365

See some use cases and initial design ideas for ensuring that the user has an opportunity to confirm payment:
https://github.com/w3c/payment-handler/pull/365#pullrequestreview-394293662

Ian

Dominant language
HTML
Stars
75
Forks
40
No merged PRs in 30d

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.

More from w3c/web-based-payment-handler

All issues in w3c/web-based-payment-handler

Similar issues

More Fintech & Quant issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.