- From: adamroach <notifications@github.com>
- Date: Tue, 29 Nov 2016 19:28:33 -0800
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Wednesday, 30 November 2016 03:29:34 UTC
The information that goes in `data` is specific to individual payment methods. See, for example, the [relevant section in the basic card specification](https://w3c.github.io/webpayments-methods-card/#request). The requirement to be serializable is to allow payment apps to send them to a server for subsequent processing (if necessary) and to allow sending them between processes in some compatible way for communication with native OS wallets (e.g., for invoking Android native payment apps). -- 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/338#issuecomment-263773447
Received on Wednesday, 30 November 2016 03:29:34 UTC