- From: rvm4 <notifications@github.com>
- Date: Fri, 29 Apr 2016 18:47:27 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
Received on Saturday, 30 April 2016 01:48:33 UTC
I also think that that short-form identifiers are troublesome on the response side of the flow. If there are two payment apps that say they can return credit card info, the expectations from the payee is that this info is standardized between the two apps, which in turn means we need to designate what that looks like. I think specing out what the response looks like for a "CC" payment method is going to be tricky and so should also be tackled as a V2 if needed. --- 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/browser-payment-api/issues/10#issuecomment-215923128
Received on Saturday, 30 April 2016 01:48:33 UTC