Stay organized with collections
Save and categorize content based on your preferences.
In order to handle payments, your Ordering End-to-End web service requests payment
tokens using Google Pay. To complete the transaction, the payment token is
forwarded to your payment gateway.
We recommend testing your payment gateway configuration early in your
integration development, as this can be a common bottleneck for developers.
The following diagram illustrates the interaction between Ordering End-to-End,
Google Pay services, your web service, and the payment processing service.
Figure 1. A visualization of
the Ordering End-to-End payment flow.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-31 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."]]],[]]
