Account Association flow
Stay organized with collections
Save and categorize content based on your preferences.
Overview
The purpose of the Account Association flow is to establish a long-lived token that both
the Payment Integrator
(integrator) and Google agree represents a link between this user's
account and a Google bank account and carries permission to move money between
these accounts. This long-lived token is called the Google Payment Token
(GPT). Google calls this token an instrument. A Google customer has one or
more instruments. An instrument is a way to pay for services and goods within
Google's various ecosystems and marketplaces.
This exchange occurs via the
associateAccount
method that is hosted by the integrator. Proof of
authentication-authorization is required input to this method. Proof of authentication is received as an outcome of the
authentication-authorization flow. For more information see the authentication-authorization flow
documentation.
This sequence diagram illustrates an example flow.
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 Account Association flow creates a Google Payment Token (GPT) linking a user's account with their Google bank account for payment purposes.\u003c/p\u003e\n"],["\u003cp\u003eThis flow requires proof of authentication-authorization, obtained through a separate authentication-authorization flow.\u003c/p\u003e\n"],["\u003cp\u003eThe GPT, also known as an instrument, allows users to pay for goods and services within Google's ecosystems.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eassociateAccount\u003c/code\u003e method, hosted by the Payment Integrator, facilitates this token exchange.\u003c/p\u003e\n"]]],["The core content details the Account Association flow, which establishes a Google Payment Token (GPT) representing a link between a user's account and a Google bank account. This GPT, called an instrument, allows for money movement between the accounts. The `associateAccount` method, hosted by the integrator, facilitates this exchange. Authentication-authorization proof is required input for this method, obtained from the authentication-authorization flow. This enables Google customers to pay for services within Google's ecosystems.\n"],null,["Overview\n\nThe purpose of the **Account Association flow** is to establish a long-lived token that both\nthe [Payment Integrator](/standard-payments/reference/glossary#payment_integrator)\n(integrator) and Google agree represents a link between this user's\naccount and a Google bank account and carries permission to move money between\nthese accounts. This long-lived token is called the Google Payment Token\n(GPT). Google calls this token an instrument. A Google customer has one or\nmore instruments. An instrument is a way to pay for services and goods within\nGoogle's various ecosystems and marketplaces.\n\nThis exchange occurs via the\n\n[`associateAccount`](/standard-payments/payment-integrator-banking-fop-api/v1/TopLevel/associateAccount)\nmethod that is hosted by the integrator. Proof of\nauthentication-authorization is required input to this method. Proof of authentication is received as an outcome of the\n**authentication-authorization flow** . For more information see the [authentication-authorization flow\ndocumentation](/standard-payments/v1/fops/banking/authentication-authorization-flow).\n\nThis sequence diagram illustrates an example flow."]]