Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developers.google.com/pay/api/android/reference/response-objects below:

JSON response objects | Google Pay API for Android

Stay organized with collections Save and categorize content based on your preferences.

This reference describes the Google Pay API response object options to use with your application. Response objects are objects that are returned by the Google Pay API client methods.

• PaymentData
• PaymentMethodData
• CardInfo
• PaymentMethodTokenizationData
• Address

Key Point: The JSON request objects are covered on their own page.

• IsReadyToPayRequest
• PaymentDataRequest
• MerchantInfo
• PaymentMethod
• PaymentMethodTokenizationSpecification
• CardParameters
• BillingAddressParameters
• ShippingAddressParameters
• TransactionInfo

This is a response object that's returned by Google after a payer approves payment.

This example response for Google Pay API version 2.0 shows a CARD payment method selected in the Google Pay payment sheet. A payment method token was generated for the example gateway.

{
  "apiVersion": 2,
  "apiVersionMinor": 0,
  "paymentMethodData": {
    "type": "CARD",
    "description": "Visa •••• 1234",
    "info": {
      "cardNetwork": "VISA",
      "cardDetails": "1234"
    },
    "tokenizationData": {
      "type": "PAYMENT_GATEWAY",
      "token": "examplePaymentMethodToken"
    }
  }
}

This object provides data for a selected payment method.

User-facing message to describe the payment method that funds this transaction.

This example response shows how a CARD payment method that's selected in the Google Pay payment sheet generates a payment method token for the example gateway.

{
  "type": "CARD",
  "description": "Visa •••• 1234",
  "info": {
    "cardNetwork": "VISA",
    "cardDetails": "1234"
  },
  "tokenizationData": {
    "type": "PAYMENT_GATEWAY",
    "token": "examplePaymentMethodToken"
  }
}

This object provides information about the selected payment card.

The payment card network of the selected payment. Returned values match the format of allowedCardNetworks in CardParameters.

This card network value should not be displayed to the buyer. It's used when the details of a buyer's card are needed. For example, if customer support needs this value to identify the card a buyer used for their transaction. For a user-visible description, use the description property of PaymentMethodData instead.

This example shows a card on the Visa network.

{
  "cardNetwork": "VISA",
  "cardDetails": "1234",
  "assuranceDetails": {
    "cardHolderAuthenticated": false,
    "accountVerified": true
  }
}

This object provides information about what validation has been performed on the returned payment credentials so that appropriate instrument risk checks can be applied.

If true, indicates that identification and verifications (ID&V) was performed on the returned payment credential.

If false, the same risk-based authentication can be performed as you would for card transactions. This risk-based authentication can include, but not limited to, step-up with 3D Secure protocol if applicable.

You can receive and process the response Object even if you don’t use the assuranceDetails field. To receive this object, include assuranceDetailsRequired: true in the Request object's CardParameters.

This object provides tokenization data for the payment method.

The generated payment method token.

• PAYMENT_GATEWAY: JSON object string that contains a chargeable token issued by your gateway.
• DIRECT: protocolVersion, signature, and a signedMessage for decryption. See Payment method token structure for more information.

This is an example of a tokenized response prepared for the example gateway.

{
  "type": "PAYMENT_GATEWAY",
  "token": "examplePaymentMethodToken"
}

This object provides information about a requested postal address. All the properties are strings.

A MIN address format may be returned if billingAddressFormat is set to MIN. A shipping address is returned in the FULL address format. All properties in a MIN formatted response exist in a FULL formatted response.

This is an example address in the United States with multiple lines of street address data.

{
  "name": "John Doe",
  "address1": "c/o Google LLC",
  "address2": "1600 Amphitheatre Pkwy",
  "address3": "Building 40",
  "locality": "Mountain View",
  "administrativeArea": "CA",
  "countryCode": "US",
  "postalCode": "94043",
  "sortingCode": ""
}

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-14 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 2025-08-14 UTC."],[[["This reference describes the Google Pay API response objects, including `PaymentData`, `PaymentMethodData`, `CardInfo`, `PaymentMethodTokenizationData`, and `Address`, for use in your application."],["Response objects are returned by the Google Pay API client methods after a user interaction, such as approving a payment."],["Each response object provides specific data, like payment method details, tokenization data, or user addresses, to help process transactions."],["The structure and content of these objects vary based on the request made and the user's selection within the Google Pay payment sheet."],["JSON request objects are covered on a separate page for a complete understanding of the Google Pay API integration."]]],["The document outlines the response objects returned by the Google Pay API. These include `PaymentData`, which contains transaction details, `PaymentMethodData` describing the selected payment, `CardInfo` with payment card specifics, `PaymentMethodTokenizationData` with tokenization details, and `Address` for postal information. Each object has properties like type, description, and associated data. `PaymentData` can contain `email` and `shippingAddress` if requested. Response data example included for `PaymentData`, `PaymentMethodData`, `CardInfo`, and `PaymentMethodTokenizationData`.\n"]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4