Stay organized with collections
Save and categorize content based on your preferences.
Overview
The Generate Redirect Payment URL is an alternative to the Begin Redirect flow for initiating a redirect payment with the payment integrator. In this flow, Google will issue a server-to-server request to the payment integrator to get the URL the user should be redirected to at the start of the payment. Google will then redirect the user to the URL the integrator provided, which will allow the user to pay at their selected issuer, then be redirected back to Google using the Complete Redirect flow.
How the flow works
There are two ways for the user to select the issuer they will use as Form of Payment (FOP).
User selects issuer in Google's User Interface (UI).
User selects integrator in Google's UI, and issuer in the integrator's UI.
User selects issuer in Google's UI
In this case, the user selects an issuer during FOP selection in Google's UI, so the issuerId field of the formOfPayment object in the Generate Redirect Payment Url request will contain a Google-generated unique identifier that represents the chosen issuer. Note that if the payment integrator and the issuer are the same entity, Google will generate an issuerId for the payment integrator.
User: This is the person who wants to make a payment.
Google UI: Google's web or app interface, where the customer initiates a payment.
Google Server: The backend server at Google that creates a redirect request.
Payment Integrator: The integrator where the user selects an issuer.
Issuer: The issuer where the user has an account.
For the Generate Redirect Payment Url flow, we already assume the user is on Google’s property (Google UI) and is choosing a payment method. Here is where everything starts.
The user selects the specific issuer they want to use to make a payment. This is what triggers the Generate Redirect Payment Url flow.
The Google UI calls the Google Server (backend) to create a new redirect request.
The Google Server calls the payment integrator hosted GenerateRedirectPaymentUrl.
The integrator will respond to Google with a URL to redirect the user to the issuer's website or app.
The redirect request is sent to the Google UI.
The Google UI redirects the user to the issuer's web interface.
The user authenticates in the issuer's web interface.
The user follows on-screen instructions to complete payment.
User selects integrator in Google's UI
In this case, the user selects the integrator in Google's UI, so the formOfPayment field of the Generate Redirect Payment Url will be set to noneChosen, because only issuers are considered valid FOPs. The integrator must provide a UI that allows the user to select one of the issuers that has been approved by Google.
The following sequence diagram shows the interaction between the user's browser, Google, the integrator, and the issuer when the user selects an integrator in Google's UI:
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-09-03 UTC.
[[["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-09-03 UTC."],[[["\u003cp\u003eThe Generate Redirect Payment URL flow provides an alternative way to initiate redirect payments, where Google gets the redirect URL from the payment integrator.\u003c/p\u003e\n"],["\u003cp\u003eUsers can select their issuer either directly in Google's UI or through the payment integrator's UI after selecting the integrator in Google's UI.\u003c/p\u003e\n"],["\u003cp\u003eGoogle facilitates the redirect by requesting the URL from the payment integrator and then redirecting the user to the issuer's platform for payment completion.\u003c/p\u003e\n"],["\u003cp\u003eIf the user selects the payment integrator first, they will then choose their issuer on the integrator's UI, and the \u003ccode\u003eformOfPayment\u003c/code\u003e field will be set to \u003ccode\u003enoneChosen\u003c/code\u003e in the initial request.\u003c/p\u003e\n"],["\u003cp\u003eBoth the payment integrator and issuer are required to provide mobile and desktop-friendly web interfaces for a seamless user experience.\u003c/p\u003e\n"]]],["This flow allows users to initiate payments via a redirect. Google sends a server-to-server request to the payment integrator to obtain a redirect URL. The user can either select an issuer directly in Google's UI, providing an `issuerId`, or select the integrator, requiring the integrator to provide an issuer selection UI. Google then redirects the user to the provided URL for payment authentication and completion with the chosen issuer, then redirects back to Google.\n"],null,["# Generate Redirect Payment Url\n\nOverview\n--------\n\nThe Generate Redirect Payment URL is an alternative to the [Begin Redirect flow](/standard-payments/concepts/redirect_fop/begin-redirect-flow) for initiating a redirect payment with the [payment integrator](/standard-payments/reference/glossary#payment_integrator). In this flow, Google will issue a server-to-server request to the payment integrator to get the URL the user should be redirected to at the start of the payment. Google will then redirect the user to the URL the integrator provided, which will allow the user to pay at their selected issuer, then be redirected back to Google using the [Complete Redirect](/standard-payments/concepts/redirect_fop/complete-redirect-flow) flow.\n| **Note:** The payment integrator and the issuer can be the same entity.\n\nHow the flow works\n------------------\n\nThere are two ways for the user to select the issuer they will use as Form of Payment (FOP).\n\n1. User selects issuer in Google's User Interface (UI).\n2. User selects integrator in Google's UI, and issuer in the integrator's UI.\n\n### User selects issuer in Google's UI\n\nIn this case, the user selects an issuer during FOP selection in Google's UI, so the [`issuerId`](/standard-payments/payment-integrator-redirect-fop-api-v1/v1/FormOfPayment#issuerid) field of the [`formOfPayment`](/standard-payments/payment-integrator-redirect-fop-api-v1/v1/FormOfPayment) object in the [Generate Redirect Payment Url request](/standard-payments/payment-integrator-redirect-fop-api-v1/v1/payment-integrator-redirect/generateRedirectPaymentUrl) will contain a Google-generated unique identifier that represents the chosen issuer. Note that if the payment integrator and the issuer are the same entity, Google will generate an [`issuerId`](/standard-payments/payment-integrator-redirect-fop-api-v1/v1/FormOfPayment#issuerid) for the payment integrator.\n| **Note:** The issuer must provide both a mobile friendly web version and a desktop friendly version of their web app.\n\n#### Generate Redirect Payment Url flow (issuer selected)\n\nHere is the list of objects in the above diagram:\n\n- **User**: This is the person who wants to make a payment.\n- **Google UI**: Google's web or app interface, where the customer initiates a payment.\n- **Google Server**: The backend server at Google that creates a redirect request.\n- **Payment Integrator**: The integrator where the user selects an issuer.\n- **Issuer**: The issuer where the user has an account.\n\nFor the Generate Redirect Payment Url flow, we already assume the user is on Google's property (Google UI) and is choosing a payment method. Here is where everything starts.\n\n1. The user selects the specific issuer they want to use to make a payment. This is what triggers the Generate Redirect Payment Url flow.\n2. The Google UI calls the Google Server (backend) to create a new redirect request.\n3. The Google Server calls the payment integrator hosted GenerateRedirectPaymentUrl.\n4. The integrator will respond to Google with a URL to redirect the user to the issuer's website or app.\n5. The redirect request is sent to the Google UI.\n6. The Google UI redirects the user to the issuer's web interface.\n7. The user authenticates in the issuer's web interface.\n8. The user follows on-screen instructions to complete payment.\n\n### User selects integrator in Google's UI\n\nIn this case, the user selects the integrator in Google's UI, so the `formOfPayment` field of the Generate Redirect Payment Url will be set to `noneChosen`, because only issuers are considered valid FOPs. The integrator must provide a UI that allows the user to select one of the issuers that has been approved by Google.\n| **Note:** The integrator must provide both a mobile friendly web version and a desktop friendly version of their web app.\n\n#### Generate Redirect Payment Url flow (integrator selected)\n\nThe following sequence diagram shows the interaction between the user's browser, Google, the integrator, and the issuer when the user selects an integrator in Google's UI:"]]
