Google Cloud Financial Services United States

PayPal

Enterprise Knowledge Search · Real-time Analytics · Security and Compliance

PayPal wanted thousands of employees to query petabytes of governed finance data conversationally, but it had to avoid plaintext secrets, AI hallucinations, inconsistent metric definitions, and data-loss-prevention risks that are unacceptable in financial services.

Achieved near 100% accuracy in AI-generated insights
Delivered governed, self-service analytics to over 5,000 users across the organization
accelerating insights by more than 50%
reducing build time from hours to minutes

Reported impact

Business outcome

PayPal delivered governed self-service analytics to 5,000 users, accelerated insight generation and dashboard creation, and proved that conversational data access can meet the accuracy and security bar required in regulated financial operations.

  • Compliance
  • Productivity Improvement
  • Risk Reduction

Solution

PayPal layered conversational analytics on top of its existing Google Cloud data stack by combining BigQuery, Looker, and Looker MCP Server inside a tightly controlled enterprise architecture. BigQuery remains the underlying warehouse for petabyte-scale data, while Looker provides the governed semantic layer and LookML business definitions needed to keep metrics consistent. To expose that semantic layer safely to LLMs, PayPal deployed Looker MCP Server into its internal MCP Hub behind an AI proxy layer, then wrapped it with an automated security handshake that fetches credentials from Looker, encrypts them into a secure vault or database, and stores access tokens in Redis rather than on user machines. Claude queries the Looker model instead of raw tables, which lets PayPal deliver natural-language analytics with near-100% accuracy while preserving auditability, row-level governance, and strict InfoSec controls.

Data flow

Users ask questions in Claude Desktop, which connects through PayPal's AI proxy and MCP Hub to Looker MCP Server. The server retrieves governed context from Looker, Looker generates SQL against BigQuery, and the response returns as a natural-language answer grounded in approved metric definitions rather than raw table guesses.

Solution architecture

4 components · 4 layers
  1. Compute
    • Claude Handles natural-language questions against the Looker semantic layer without querying raw databases directly.
  2. Storage
    • BigQuery Stores the petabyte-scale data estate that PayPal employees query through governed conversational analytics.
  3. Serving
    • Looker Provides the semantic layer and governed LookML definitions that keep metrics accurate and consistent across teams.
  4. Orchestration
    • Looker MCP Server Acts as the bridge that lets LLMs understand Looker semantic models inside PayPal's secured enterprise environment.

Architecture clues

  • AI queries the Looker model instead of the raw database
  • Credentials are pushed into a secured vault/database with encryption and access tokens are stored in Redis cache
  • Looker MCP Server is deployed directly into PayPal's MCP Hub
  • The environment is delivered as a one-click installation from the internal software center

Evidence from the source

By grounding AI interactions in Looker's governed data models, PayPal ensures accuracy and compliance while enabling 5,000 employees to query petabytes of data using natural language.
PayPal adopted Looker's Model Context Protocol (MCP) Server to provide secure, conversational analytics to its workforce.
When the LLM receives a prompt, it doesn't query the raw database; it queries the Looker model.
delivers almost 100% accuracy against our defined metrics.
the system pushes them directly into a secured vault/database with encryption, while access tokens are encrypted and stored in Redis cache
Transparency Evidence & methodology 100/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Google Cloud

    PayPal customer story

    First-party
    https://cloud.google.com/customers/paypal-looker-mcp
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Apr 22, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Apr 20, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.