[w3c/3ds] Mixing 3DS with Payment Methods (#9)

The example in the spec has a `requestLevel` field in the `data` object within the Payment Request `methodData`. Can this field be "mixed in" with any arbitrary payment method (basic-card, tokenized-card, SEPA, Interledger, etc.)? 

What if the merchant or network wants to require a 3DS flow for some payment methods (say, basic-card) but not others (say, SEPA)? 

And is `requestLevel` too generic (i.e., would something like `authRequestLevel` or `3DSRequestLevel` be clearer)?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/3ds/issues/9