MCP Tools Reference: paydeveloper.googleapis.com

Tool: create_google_pay_integration

Creates a Google Pay integration for a specific merchant. This operation requires the user to have accepted the Business Console Terms of Service and the Google Pay API Terms of Service. You do not need to preemptively check for these. If they have not been accepted, the tool call will fail and the error message will contain the specific Terms of Service URLs that need to be accepted. If this occurs, present the URLs to the user for acceptance, and instruct them to try again once accepted. Follow this sequence to interact with the user BEFORE calling the tool: 1. First, ask the user for the integration item (Only Web integration is supported for now). - Ask for the website URL. - If the integration item is App integration, ask for the Android app package name. 2. Then, ask the user for the integration type: - Tell the user to choose Gateway if they use one of our supported Payment Service Providers (PSPs: https://developers.google.com/pay/api#participating-processors), otherwise choose Direct. 3. For ALL integration types (Direct or Gateway): - Tell the user to upload screenshots (1MB max) of their buyflow integrated with the Google Pay API. Their buyflow must be reviewed and approved before they're given full production access. Examples: https://developers.google.com/pay/api/web/guides/brand-guidelines#put-it-all-together. - You MUST ask the user to provide 5 supporting screenshots. Ask for them ONE BY ONE to ensure correct mapping. Use ONLY the user-friendly enum descriptions when asking. 4. If the integration type is Direct: - You MUST ALSO ask the user to provide the PCI attestation document in PDF format. Use ONLY the user-friendly enum description when asking. 5. For each file provided, ask the user to provide the document path or name if in the current directory. Map it to the correct DocumentType and set the name field to a descriptive name (e.g., item_selection.png or pci_attestation.pdf) in the request. Do not call this tool until you have attempted to collect the required documents for the selected integration type.

The following sample demonstrate how to use curl to invoke the create_google_pay_integration MCP tool.

Input Schema

{
  "merchantId": string,
  "googlePayIntegration": {
    object (GooglePayIntegration)
  }
}

{
  "integrationState": enum (IntegrationState),
  "createTime": string,
  "updateTime": string,
  "integrationType": enum (IntegrationType),
  "integrationDocuments": [
    {
      object (IntegrationDocument)
    }
  ],

  // Union field item can be only one of the following:
  "webDomain": string,
  "androidAppPackage": string
  // End of list of possible types for union field item.
}

{
  "seconds": string,
  "nanos": integer
}

{
  "name": string,
  "data": string,
  "documentType": enum (DocumentType),
  "mimeType": enum (MimeType)
}

Output Schema

{
  "integrationState": enum (IntegrationState)
}

Tool Annotations

Destructive Hint: ❌ | Idempotent Hint: ❌ | Read Only Hint: ❌ | Open World Hint: ❌