marcoscaceres commented on this pull request. > + <a>PaymentDetailsInit</a> dictionary. This includes total cost, and + optionally a list of goods or services being purchased, for physical + goods, any shipping options. Additionally, it can optionally include + "modifiers" to how payments are made. For example, "if you pay with a + credit card of type X, it incurs a US$3.00 processing fee". + </li> + <li>The <var>options</var>: Optionally, a list of things that the site + needs to deliver the good or service (e.g., for physical goods, the + merchant will typically need an physical address to ship to. For + digital goods, an email will usually suffice). + </li> + </ul> + <p> + Once a <a>PaymentRequest</a> is constructed, it's presented to the end + user via the <a>show()</a> method. The <a>show()</a> returns a promise + that, once the user confirms request for payment, results in a Will investigate separately. I might have broken something in latest ReSpec release I did today. -- 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/553#discussion_r128452138
Received on Thursday, 20 July 2017 08:21:47 UTC