Re: [browser-payment-api] Add reference to issue #47. (#81)

> +  description: 'Payment to ExampleMerch for widgets',
> +  acceptablePayment: {
> +    paymentMethod: 'Visa',
> +    paymentAmount: {
> +      amount: '4.35',
> +      currency: 'USD'
> +    }
> +  }
> +};
> +
> +// request payment and get a promise that will resolve to
> +// a payment acknowledgement
> +var payment = navigator.payment.request(request);
> +        </pre>
> +      </div>
> +
>        <p>The following example shows how to construct a <a><code>PaymentRequest</code></a> and begin the

@msporny Can you reword this to be a lot simpler and leave the deeper explanation for users to read in the issue itself? I would also suggest placing this issue marker alongside those for #15 and #16 which also relate to the shape of the API.

Suggestion:

```html
<div class="issue" data-number="47" title="Should a payment request be just data, or a 
programmable object?"> There is an open issue about whether the payment request should 
be a programmable object or should be just pure data that can be operated on by methods.</div>
```



---
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/pull/81/files/81b3240a046ce70004ef3f0f2ba6e45734c583c8..3ddca06a9e2a7734809012ef55a21ea1671d8fb5#r57535219