Google Cloud Financial Services United States

PayPal

Application Refactoring · IT Operations Automation · Real-time Analytics

After unifying its core data estate, PayPal needed an AI platform that could power global commerce use cases, let developers choose the best model for each workload, and elastically handle training and inference without reverting to monolithic release cycles or custom infrastructure for every project.

25,000 pipelines every day
migrating over 300 petabytes of data to BigQuery
more than 200 enterprise-ready models
over 439 million global users

Reported impact

Business outcome

PayPal transformed its post-migration data estate into a flexible AI platform that speeds releases, supports tens of thousands of pipelines a day, and lets the business scale agentic commerce capabilities without locking teams into a single model vendor or architecture pattern.

  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

PayPal built its next-generation AI stack on Google Cloud by combining BigQuery, Google Kubernetes Engine, Gemini Enterprise Agent Platform, and Cloud GPUs into a unified model and infrastructure layer. BigQuery provides the AI-ready data foundation following PayPal's migration of more than 300 petabytes, while GKE gives teams an elastic architecture that replaced slower monolithic release patterns and now supports 25,000 pipelines per day. On top of that runtime, PayPal created a unified LLM stack: open-source models run on the GKE inferencing layer, while proprietary models such as Gemini run through Gemini Enterprise Agent Platform and Model Garden. Cloud GPU capacity provides the compute horsepower for training and high-performance workloads. This architecture lets developers move from idea to production quickly while preserving security, compliance, and model-choice flexibility across PayPal's 439 million-user commerce business.

Data flow

Enterprise data lands in BigQuery and is consumed by PayPal's data scientists and AI services. Open-source models run on the GKE inferencing layer, proprietary models such as Gemini are served through Gemini Enterprise Agent Platform, and Cloud GPUs supply the training and inference capacity needed to scale AI products into commerce workflows.

Solution architecture

4 components · 3 layers
  1. Compute
    • Cloud GPUs Provide the high-performance training and inference compute needed for PayPal's unified AI stack.
  2. Storage
    • BigQuery Stores the unified data foundation that PayPal uses to train, evaluate, and operationalize AI workloads at global scale.
  3. Orchestration
    • Google Kubernetes Engine Runs the elastic inferencing and application architecture that replaced slower monolithic release patterns.
    • Gemini Enterprise Agent Platform Hosts proprietary model access and gives developers a governed path to production AI agents and Model Garden assets.

Architecture clues

  • Model Garden exposes more than 200 enterprise-ready models
  • Open-source models run on top of the inferencing stack on GKE
  • PayPal is transitioning into B200 GPUs
  • close-sourced models like Gemini run on top of Gemini Enterprise Agent Platform

Evidence from the source

PayPal built a unified large language model (LLM) stack, which runs open-source models on top of the inferencing stack on GKE and close-sourced models like Gemini on top of Gemini Enterprise Agent Platform.
With Google Cloud, PayPal built a unified AI platform to architect the next era of commerce for over 439 million global users.
after GKE, our release life cycle went from weeks to minutes.
developers have access to more than 200 enterprise-ready models through Model Garden.
migrating over 300 petabytes of data to BigQuery
Transparency Evidence & methodology 85/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 value85/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/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 impact15/25
    1 metric 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-ai
    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 Aug 29, 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 Aug 26, 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.