Para procesar los pagos, tu servicio web de extremo a extremo de pedidos solicita tokens de pago con Google Pay. Para completar la transacción, el token de pago se reenvía a tu puerta de enlace de pagos.
Te recomendamos que pruebes la configuración de la puerta de enlace de pagos al principio del desarrollo de la integración, ya que puede ser un cuello de botella común para los desarrolladores.
En el siguiente diagrama, se ilustra la interacción entre el pedido de extremo a extremo, los servicios de Google Pay, tu servicio web y el servicio de procesamiento de pagos.
Figura 1: Visualización del flujo de pago de pedidos de extremo a extremo.
[null,null,["Última actualización: 2024-11-26 (UTC)"],[[["Your Ordering End-to-End web service uses Google Pay to request payment tokens for handling payments, which are then sent to your payment gateway for transaction completion."],["Early testing of your payment gateway configuration is recommended to avoid potential integration bottlenecks."],["To accept tokenized payments, integration with a participating Google Pay gateway is necessary, potentially requiring merchant registration and Google Pay enablement for your account."],["The payment flow involves interaction between Ordering End-to-End, Google Pay, your web service, and the payment processing service, with potential CVC challenges for new credit cards used with Google Pay."]]],["The web service requests payment tokens via Google Pay to process payments. These tokens are then sent to the payment gateway to complete transactions. It's advised to test the gateway configuration early due to potential delays. Integration with a listed Google Pay gateway is required, and merchants must register and obtain a `merchantId`. The process involves interactions between the service, Google Pay, the web service, and the payment processor. Using a new credit card with Google Pay may result in a temporary pending transaction.\n"]]
