Authentication of merchant domain and details
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 510
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I was reading the spec and I don't really understand how the merchant domain or payment details are authenticated. How do you prevent such a scenario:
- A user visits
secure-legit-trusted-store.com, adds a $1000 laptop to their cart and initiates a payment secure-legit-trusted-store.combackend visitsbuy-crypto-online.comand initiates a payment for $1000secure-legit-trusted-store.comrelays the request frombuy-crypto-online.com, but changesdetailstoThe best laptop- User confirms the payment
secure-legit-trusted-store.comrelays the response tobuy-crypto-online.com
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 Payment Request API specification referenced by the issue and trace how merchant domains, payment details, and relayed requests are defined. Determine whether the scenario is covered by the current specification; done means reaching a clear security decision and specifying or documenting the required authentication behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, payments, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100