Payment Integrator Account Structure
Stay organized with collections
Save and categorize content based on your preferences.
A company is a concept defined within Google's configuration and contract.
A payment integrator account ID correlates with an agreement (contract) that the
payment integrator has signed. A payment integrator account ID will define
things associated with capture and refund: purchase currency, settlement
currency, minimum transaction values, etc.
For more details, see the Company and Payment Integrator Account ID
glossary
definition.
The company defines things such as keys, URLs etc about the particular connection
between Google and the payment integrator.
The structure of a company having one or more accound IDs allows Google and the
integrator to structure fees and eligibility independent of a user adding their
instrument. Further it allows all instruments created within the company to work
on all payment integrator account IDs.
The Association flow
contains a subtlety that needs to be called out. Google Payment
Tokens and association IDs are not
associated with a particular payment integrator account ID. They are associated
with a company. All GPTs must be automatically associated with every payment
integrator account ID within the company. That doesn't necessarily mean every
GPT will be useable in every purchase flow for every payment integrator account
ID within the company. For instance, if a particular payment integrator account
ID specifies a currency code that isn't supported for a purchase, the capture
must fail with an error.
Companies and payment integrator account ID have a 1:N relationship, where N
is >=1.
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\u003eA company in Google's system represents the connection between Google and a payment integrator, encompassing keys, URLs, and other configuration details.\u003c/p\u003e\n"],["\u003cp\u003ePayment integrator account IDs within a company define specifics like currency, transaction limits, and settlement, impacting capture and refunds.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Payment Tokens and association IDs are linked to the company level, allowing their potential use across all associated payment integrator accounts within that company, but subject to account-specific restrictions.\u003c/p\u003e\n"],["\u003cp\u003eWhile all Google Payment Tokens are technically associated with every payment integrator account within a company, their usability is determined by factors like currency compatibility, potentially causing transaction failures if mismatched.\u003c/p\u003e\n"],["\u003cp\u003eCompanies and payment integrator account IDs have a one-to-many relationship, meaning a company can have one or more associated payment integrator account IDs.\u003c/p\u003e\n"]]],["A company, as defined in Google's configuration, holds keys and URLs for the connection between Google and a payment integrator. Each company can have multiple payment integrator account IDs, each tied to a specific contract and defining transaction details like currency and minimum values. Google Payment Tokens (GPTs) are linked to a company, not a specific account ID, ensuring they are associated with all account IDs within that company. While all GPTs are associated, their usability in purchases depends on the account ID's specific requirements, such as supported currencies. The relationship between company and payment account IDs is 1:N.\n"],null,["# Payment Integrator Account Structure\n\nA company is a concept defined within Google's configuration and contract.\n\nA payment integrator account ID correlates with an agreement (contract) that the\npayment integrator has signed. A payment integrator account ID will define\nthings associated with capture and refund: purchase currency, settlement\ncurrency, minimum transaction values, etc.\n\nFor more details, see the Company and Payment Integrator Account ID\n[glossary](/standard-payments/reference/glossary#payment_integrator_account_id)\ndefinition.\n\nThe company defines things such as keys, URLs etc about the particular connection\nbetween Google and the payment integrator.\n\nThe structure of a company having one or more accound IDs allows Google and the\nintegrator to structure fees and eligibility independent of a user adding their\ninstrument. Further it allows all instruments created within the company to work\non all payment integrator account IDs.\n\nThe [Association flow](/standard-payments/v1/key-concepts/association-flow)\ncontains a subtlety that needs to be called out. [Google Payment\nTokens](/standard-payments/reference/glossary) and association IDs are not\nassociated with a particular payment integrator account ID. They are associated\nwith a company. All GPTs must be automatically associated with every payment\nintegrator account ID within the company. That doesn't necessarily mean every\nGPT will be useable in every purchase flow for every payment integrator account\nID within the company. For instance, if a particular payment integrator account\nID specifies a currency code that isn't supported for a purchase, the capture\nmust fail with an error.\n\nCompanies and payment integrator account ID have a 1:N relationship, where N\nis \\\u003e=1."]]