Google Introduces Payment Process Layer via Payment Request API

Google has introduced its Payment Request API. The API was created with a goal to "eliminate checkout forms." The new service is not a payment method, nor does it integrate with payment processors. Rather, the API provides a process layer to improve user workflow.

Google includes four goals for this new process layer. First, it allows the browser to serve as an intermediary between merchants, users, and payment methods. Second, the process layer standardizes payment communication flow. Third, because it is not a payment processor, it supports varying payment methods. Finally, it operates cross browser, device and Platform.

The API completely replaces traditional checkout processes. Merchants can accept any payment via a simple API call. Once integrated with a website, the API exchanges information with a user while the user provides input. In the end, the consumer enjoys a single click purchase experience because all necessary information is stored in-browser.

The process initiates with a new PaymentRequest. Next, the browser gathers all information required to complete a purchase (i.e. charge amount, currency, payment methods accepted by site, etc.). The browser determines compatibility, presents payments, and selects an authorization route. The PaymentRequest can also include addition information such as shipping address, email, and phone contact information. For more information, visit the API docs.

Be sure to read the next Payments article: Daily API RoundUp: Google Payment Request, Losant, Hellenic Bank, Bark