Comments (3)
- User agrees with merchant to pay $100
What constitute an "agreement"? Who, if any, needs to be able to verify this "agreement" took place?
- When user chooses payment method, the payment method supports installments (e.g., $25 every week)
- The SPC transaction window should say "Do you agree to pay $25?"
This sounds like the browser UI should display $25. What would be the amount that the issuer wants to see in the Transaction Confirmation / Dynamic Linking signature?
- Subsequent payments are handled by card-on-file
Do these subsequent payments need to carry Dynamic Linking signatures?
from secure-payment-confirmation.
from secure-payment-confirmation.
The way the API has evolved, if it is callable at all in a payment handler, then it is callable with data provided by the payment handler. So the answer to the original issue is "Yes, the payment handler can specify a total that is different from what the merchant displayed." The resulting assertion will include the signed data that was displayed, and the RP can accept or reject it.
from secure-payment-confirmation.
Related Issues (20)
- Term 'monkey-patch' may not be inclusive? HOT 1
- `DOMString` for `payeeName` vs. `USVString` for other fields? HOT 1
- Add locale hint for browser UX
- Proposal: Remove User Activation requirement for authentication HOT 1
- Use lowercase values in enum HOT 11
- Register SPC-related WebAuthn extensions in IANA registry HOT 8
- Broken references in Secure Payment Confirmation
- Example of `locale` member HOT 3
- I18N problem with displayName unresolved? HOT 3
- [PING] Only allow triggering authentication from a foreground tab HOT 4
- Broken references in Secure Payment Confirmation
- Broken references in Secure Payment Confirmation
- Add Support for Cross-Device Authentication HOT 2
- Implementing a time out for fallback UX HOT 1
- How will new passkey providers impact SPC HOT 1
- Document End-User Guide HOT 5
- Update SPC spec to reflect that credential create in cross-origin iframe is now allowed in WebAuthn HOT 1
- Limitations for showing transaction data HOT 5
- Google payment solutions HOT 2
- Proposal: WebAuthn-agnostic device binding for Secure Payment Confirmation HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from secure-payment-confirmation.