![]() This requestId is the idempotency key for all calls.Īny non terminal response (a non HTTP 200-success), must not be idempotently processed. All methods have a common RequestHeader which contains a requestId. The response for the successful processing should be reported instead. Integrators should not attempt to reprocess any request already successfully processed. Google will sporadically retry requests to ensure that transactions are in the same state on both sides. To represent a monetary value in micros, multiply the standard currency value by 1,000,000.Īll method calls within this API must have idempotent behavior. Micros are an integer based, fixed precision format. Monetary values in this API are in a format called "micros," a standard at Google. TimestampsĪll timestamps are represented as milliseconds since the Unix epoch (Jan 1, 1970) in UTC. The key words "MUST," "MUST NOT," "REQUIRED," "SHALL," "SHALL NOT," "SHOULD," "SHOULD NOT," "RECOMMENDED," "MAY," and "OPTIONAL" in these documents are to be interpreted as described in RFC 2119. These flows are described in more detail in the sections below, and in even greater detail in the guides section. This diagram illustrates a broad overview of the flows: Tokenized FOP overviewĪt a high level, adding your service as a form of payment to Google products involves these flows: 1) The user selects a product to buyĥ) Finally, they are authenticated and can purchase A Google customer may have more than one instrument to pay for goods and services.įinally, all movement of money between the integrator’s bank and Google’s bank is done in the remittance flow. Google uses this token to represent an instance of a payment method by a customer. Once the token is established, Google will use it during the purchase flow for a fast and seamless checkout experience for the user. The token may then be used in future purchases. This token represents a particular form of payment by a particular user. Association flow: Establishes a token for a user (new or previously identified and authenticated).Authentication flow: Identifies and verifies (authenticates) the user.Google uses two flows to establish identity and create this token: The rest of this document is focused on version 1. All other tokenized FOP providers should implement version 1. Version 2 supports mobile carriers and reference number providers. Currently there are 2 versions of these APIs. This token can then be used for payment over and over. This in turn goes through the flow of establishing a token, representing that form of payment for that particular user. ![]() For a user to make a payment with this FOP, Google and the Payment integrator must perform a one-time exchange of account identity credentials. A tokenized FOP (form of Payment) is one kind of payment integration into the Payments Platform. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |