Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34)

>> The spec talks about network failures. I think Service Workers are the answer here. 
>> They provide offline capability and caching, if necessary.
> Do you think we need to provide any information (e.g., a transaction identifier) that
> could be used to query the state of a transaction?

The issue here is with push payments where the website gets no response from the app and so has no way of knowing if the payment was completed. I think we need a holistic approach to this including a unique transaction ID set by the browser and possibly a standard query URL that can be used to get the status of a payment using the ID.

-- 
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/34#issuecomment-245455569

Received on Wednesday, 7 September 2016 23:58:31 UTC