w3c src issues - Githubissues

w3c / src

Other

7 stars 7 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

expand acronym

#41 samuelweiler opened 3 years ago
0
Defining behavior in different SRC-I availability scenarios

#40 ianbjacobs opened 4 years ago
1
Built-in SRC Payment Handler

#39 tblachowicz closed 4 years ago
1
Browser-specific manifest instructions

#38 marcoscaceres closed 4 years ago
1
SRC-I not defined

#37 marcoscaceres closed 4 years ago
1
Phishing-resistant

#36 marcoscaceres opened 4 years ago
1
Try to remain vendor neutral

#35 marcoscaceres closed 4 years ago
3
Make the arc document a markdown doc

#34 marcoscaceres closed 4 years ago
2
Maybe avoid mention of hasEnrolledInstrument for now?

#33 marcoscaceres opened 4 years ago
1
Can common payment handler be used for card-on-file updates?

#32 ianbjacobs opened 4 years ago
0
(Editorial) Spell fixes

#31 ianbjacobs closed 4 years ago
0
Source file for unrecognised consumer flow

#30 tblachowicz closed 4 years ago
0
Source file for recognised consumer flow

#29 tblachowicz closed 4 years ago
0
Source file for 1st time consumer flow

#28 tblachowicz closed 4 years ago
0
SRC Flows

#27 tblachowicz closed 4 years ago
0
Allow for custom data to SRCI

#26 ianbjacobs opened 4 years ago
0
Can we align AssurancePreference with SRC 3DS Preference?

#25 tblachowicz opened 4 years ago
0
Consumer Identity Mapping

#24 tblachowicz opened 4 years ago
0
What are user journeys with SRC payment handlers?

#23 ianbjacobs opened 4 years ago
0
What request data do we need to support 3DS from the payment handler?

#22 ianbjacobs opened 5 years ago
1
Missing ServiceID in request data

#21 tblachowicz opened 5 years ago
0
Is support for custom input/output data required?

#20 tblachowicz opened 5 years ago
0
Is EventHistory useful for the Payee

#19 tblachowicz opened 5 years ago
0
Do we need payloadTypeIndicator?

#18 ianbjacobs opened 5 years ago
3
Token and token reference use cases

#17 ianbjacobs opened 5 years ago
2
How should assurance data in the response be modeled?

#16 ianbjacobs opened 5 years ago
0
Can we align response data names with Basic Card response data?

#15 ianbjacobs opened 5 years ago
4
How do we define dynamic data options?

#14 ianbjacobs opened 5 years ago
3
Assumption: Merchant has already onboarded into SRC (when this payment method is used)

#13 ianbjacobs closed 5 years ago
2
Provide full data instead of masked with user consent?

#12 ianbjacobs opened 5 years ago
1
Redundant payment data and display data?

#11 ianbjacobs opened 5 years ago
4
How are keys communicated for encryption of response data?

#10 ianbjacobs closed 5 years ago
4
Request parameter for different card response options

#9 ianbjacobs closed 5 years ago
1
Is tokenUsageType useful for SRC?

#8 ianbjacobs closed 5 years ago
3
Is transactionType useful for SRC?

#7 ianbjacobs closed 5 years ago
4
Is supportedTypes useful with SRC?

#6 ianbjacobs closed 5 years ago
1
[wiki] Why is SRC Profile out of scope?

#5 adrianhopebailie opened 5 years ago
1
[wiki] Provide clarity on security requirements

#4 adrianhopebailie opened 5 years ago
2
[wiki] Why not use URL-based payment methods for each SRC system?

#3 adrianhopebailie opened 5 years ago
2
[wiki] Is it a goal for browsers to need explicit support SRC?

#2 adrianhopebailie closed 5 years ago
1
Browser as Aggregator of Card Metadata is bad idea

#1 adrianhopebailie opened 5 years ago
4