When the payment mediator invokes a payment app, it does not pass the `PaymentRequest` instance to the app. Instead it passes a `PaymentAppRequestData` structure (as defined [here](https://w3c.github.io/webpayments-payment-apps-api/#idl-def-paymentapprequestdata)). Likewise, when the payment app passes response data back to the mediator, it should use a 'PaymentAppResponseData' structure instead of creating a `PaymentResponse`. I have two reasons for this: 1. Symmetry. The more symmetrical we can make the request and response, the easier it will be for developers to understand and use the API. 2. Serializability. The data that is passed between the mediator and the payment app needs to be json-serializable. The `complete` method of the `PaymentResponse` makes this object not serializable. I have assigned this issue to myself, and unless I'm hearinging objections to the addition of this structure, I plan to make a PR soon. -- 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/webpayments-payment-apps-api/issues/81
Received on Tuesday, 10 January 2017 10:04:52 UTC