Re: [webpayments] PROPOSAL: The PaymentRequest object MUST NOT expose internal state information to the developer. (#64)

@zkoch wrote:
>> 2) it hangs functionality off of the PaymentRequest object that, arguably, complicates how a developer has to manage it.

>Not sure I understand how this is a point separate from point 1.

I'm asserting that not only do you not need to expose state information on the PaymentRequest, but you also don't need methods on it like .show(), .complete(), and .abort().

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/64#issuecomment-175959614