The W3C Web Payments HTTP API allows developers to register payment applications, create payment requests, and reply with payment responses. It allows web applications to initiate payments for products or services by serving an HTTP 402 Payment Required response along with sufficient data to start and complete the payment flow.
The following is a list of historical changes that were made to this asset. Typically, once an API is published on ProgrammableWeb.com, the data we keep about that asset gets updated over the course of its life. For example, the endpoint or home page of the documentation might change. As a means of enforcing the integrity of our data, every time a non-trivial change is made to the data we keep about an asset, we require the entry of some changelog text before that change can be saved. This way, we have a great audit trail of all activity surrounding the asset. For each asset, the changelogs begins with the moment an asset is approved for publication on ProgrammableWeb. If you spot an error in our data and believe that a record needs to be updated in some way, the ProgrammableWeb team would very much like to hear from you at firstname.lastname@example.org
08-12-17 17:19:21[Brief] ProgrammableWeb's Most Interesting APIs in 2017: Payments, Banking, Blockchain and Finance updated with Related API W3C Web Payments HTTP
29-11-17 14:41:38[News] W3C Payment Request API is Being Implemented in All Major Browsers updated with Related API W3C Web Payments HTTP
10-10-16 15:51:54[Brief] Daily API RoundUp: Amazon Cognito Identity, BloomSky, World Air Quality, Crowdpay, Stride, Blinkstick updated with Related API W3C Web Payments HTTP