Boost payment applications with web payments

Nuevos estándares Web para una experiencia de pago sin problemas en la web.

May 25, 2020
Updated July 16, 2020

One of the key drivers of the web ecosystem is payments. With secure, fluid and flexible payment systems, the web can become a sustainable and profitable platform. Web Payments standards have the potential to be a key component that will enable seamless integration of payment solutions into merchant payment flows.

What are web payments?

Web Payments es una serie de nuevas API de pago estandarizadas disponibles en los browsers modernos, que incluyen Payment request API, Payment Controller API and some others. Estas nuevas primitivas del browser simplifican los pagos en línea y permiten que las aplicaciones de pago se integren con los navegadores más fácilmente que nunca.

The standards are flexible; They work with various types of payment systems and are designed to work in any browser on any device, payment method or payment service provider. This flexibility enables simplicity of development, consistency of implementation, and future compatibility with emerging payment technologies.

Research shows that Long checkout flows lead to cart abandonment. Con Web Payments, el flujo de pago se simplifica a unos pocos toques en lugar de la entrada manual de datos de facturación para cada compra. Vea una demostración a continuación de cómo Google Pay aprovecha los pagos web para crear un flujo fluido. Lo mismo se puede lograr con cualquier otra aplicación de pago:

1. The client va a la caja y presiona el GPay button.

2. The Google Pay application is launched in front of the merchant's website.

3. The customer confirms the payment in the Google Pay app after examining the details.

4. The merchant verifies the payment and the purchase is approved.

Browser support

Web Payments consists of a few different technologies and the support status is browser dependent.

The benefits of integrating Web Payments into a payment application

Al integrarse con Web Payments, las aplicaciones de pago pueden brindar una mejor user experience a los clientes, tener una mejor experiencia de desarrollador y una seguridad más estricta.

Mejor experiencia de Username

• Payments in context: Payments are made in
  manners, in the context of the merchant's website, without redirects or pop-ups.

• Faster payment: Customers can save their payment details securely in their browser or in a payment application, ready to be used on any supporting business site.

• Optimized shopping experience: After completing (or canceling) the payment, the customer is on the merchant's website exactly where they left off.

Better developer experience

• Easy integration: Web payments can be extended from an existing platform-specific payment application or a web-based payment application.

• Low integration cost: Los comerciantes pueden integrar Web Payments con JavaScript y la integración del lado del server de nivel básico.

• Standards: The protocol and data format for exchanging information with merchants is standardized and does not require deep integration.

• Dynamic price updates: Merchants can dynamically change the shipping cost based on the shipping address selected in the checkout app, without deep integration.

Tighter security

• Lateral load prevention when invoking platform-specific payment applications.

• Designed with the upcoming security and privacy paradigms in mind.

Using Web Payments also enables payment applications to bring any type of payment method to the web, such as e-money, cryptocurrencies, bank transfers, and more. Web Payments is designed with sustainability in mind and does not impose restrictions on processing and payment methods.

Comparison of web payments with other approaches

Consider existing approaches to integrating payments on the web:

• iframes: Usar JavaScript para inyectar el sitio web del administrador de pagos en un iframe y recopilar la credencial de pago del cliente a través de un formulario.

• Pop-up windows: Usar JavaScript para abrir una ventana emergente y recopilar las credenciales de pago del cliente, ya be a través de un formulario o haciendo que el cliente se autentique y seleccione una credencial de pago.

• Redirects: El comerciante redirige al cliente al sitio web de un administrador de pagos y permite que el cliente se autentique y seleccione las credenciales de pago. La Url de redireccionamiento se comunica a través de un servidor.

• OAuth: El comerciante permite que el cliente se autentique y autorice con la identidad de un administrador de pagos a través de OAuth, seleccione un método de pago, una dirección de envío, etc., a través de la user interface de iframe en contexto.

Here's how they compare to web payments:

Integration of web payments in existing applications

You can integrate Web Payments into platform-specific and web-based payment applications: If the platform-specific payment application is not installed, the web-based payment application can be used as an alternative. Customers and merchants can seamlessly send and receive payments through a payment method of their choice, depending on the environment.

Platform-specific payment applications

• Ideal for paid applications that already have a large install base and want to provide existing users with a consistent web experience.

• different to Android 'Intent' function, Web Payments performs signature verification before running the payment application, making malicious payment applications impossible to download.

In the video above, Google Pay is a platform-specific payment app.

Web-based payment applications

• More future-proof: Typical payment application techniques, such as redirects or pop-ups, rely on third-party cookies. that can become obsolete. While the consequences are still difficult to foresee, web payments look to the web for better privacy and a world without third-party cookies.

• The web-based route is ideal for web services that have a large number of customers with their registered card.

How does commercial adoption work?

For a payment application to be available from a merchant, the merchant must explicitly adopt it. Technically speaking, the merchant must specify the identifier of the payment application (identifier of the payment method) and use the payment request API with it.

We suggest that you provide good documentation in integration guides and SDKs or libraries to facilitate integration. For example, Google Pay provides a guide for developers.

Trabajar con pasarelas de pago también es una buena opción, ya que también pueden ayudar a escalar su scope.

How much is it?

Web payments are standard technology in the browser. Payment applications that adopt or activate it in the browser will not charge you any fees for themselves.