Comments (2)
Here is my understanding (and I can add this to the wiki if useful):
- I though instinctively that each SRC system owner would want to leverage the payment method manifest to whitelist certified payment handlers. However, after discussion with the card brands, apparently that is not something that the card brands want to do. They do not want to publish payment method manifests.
- At that point, I believe there is little semantic difference between "one PMI with supportedNetworks" versus "N PMIs without supportedNetworks." The former requires W3C (or someone else) to maintain a registry, but we are already doing that. The former is much easier to write and remember. It also conveys more strongly "There is a single payment method" which is, as I understanding, a strong message the card brands wish to send.
I am not yet sure whether the "one PMI" will be a short string or a URL. However, either way, I think the above reasoning still holds.
from src.
However, after discussion with the card brands, apparently that is not something that the card brands want to do. They do not want to publish payment method manifests.
NOT needing a feature of URL-based methods is orthogonal to the issue of whether or not to use the less-appropriate short-string based system.
"one PMI with supportedNetworks" versus "N PMIs without supportedNetworks."
I disagree. When you use a short string identifier and define a data model for it then you are requiring browsers to explicitly implement validation for that data model and continue to update their code to support the changing registry.
The former requires W3C (or someone else) to maintain a registry, but we are already doing that.
This doesn't take away the need for browsers to do maintenance work whenever this registry changes.
We have done this once on the assumption that the registry will seldom if ever change and get deprecated along with basic-card
in the end anyway.
from src.
Related Issues (20)
- How should assurance data in the response be modeled?
- Token and token reference use cases HOT 2
- Do we need payloadTypeIndicator? HOT 3
- Is EventHistory useful for the Payee
- Is support for custom input/output data required?
- Missing ServiceID in request data
- What request data do we need to support 3DS from the payment handler? HOT 1
- What are user journeys with SRC payment handlers?
- Consumer Identity Mapping
- Can we align AssurancePreference with SRC 3DS Preference?
- Allow for custom data to SRCI
- Can common payment handler be used for card-on-file updates?
- Maybe avoid mention of hasEnrolledInstrument for now? HOT 1
- Make the arc document a markdown doc HOT 2
- Try to remain vendor neutral HOT 3
- Phishing-resistant HOT 1
- SRC-I not defined HOT 1
- Browser-specific manifest instructions HOT 1
- Defining behavior in different SRC-I availability scenarios HOT 1
- expand acronym
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 src.