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

@ianbjacobs I guess it just struck me, looking at the request example in the 3DS spec, that the `data` object could get awfully messy if the merchant supports 2 or 3 or 4 payment methods because none of the fields are "namespaced" and some of the fields could apply to less than all the methods. However, I suppose the use of tuples for [[serializedMethodData]] might make it easier for the user agent to disentangle the business logic. (Sorry, just thinking aloud here...)

-- 
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#issuecomment-415097272