---
title: "PayPal Disputes"
description: "A non-technical ecosystem overview of PayPal Disputes in RevCent, focused on how RevCent automatically monitors connected PayPal Accounts for new disputes and dispute updates, and how PayPal Disputes relate to PayPal Transactions, Sales, Customers, Campaigns, Shops, Shipping, risk review, support workflows, and reporting."
type: "item"
company: "RevCent"
canonical: "https://revcent.com/documentation/markdown/ecosystem/item/PayPalDispute.md"
relationships:
  - name: "PayPal Account"
    url: "https://revcent.com/documentation/markdown/ecosystem/feature/PayPalAccount.md"
  - name: "PayPal Transaction"
    url: "https://revcent.com/documentation/markdown/ecosystem/item/PayPalTransaction.md"
technical_links:
  web_app: "https://kb.revcent.com/en/payments/paypal/dispute"
  api:
    section: "https://revcent.com/docs/api/v2#section-pay_pal_disputes"
    operations:
      - name: "Get PayPal Disputes"
        operation_id: "GetPayPalDisputes"
        operation: "https://revcent.com/docs/api/v2#operation-GetPayPalDisputes"
        schema: "https://revcent.com/documentation/files/api/operation/GetPayPalDisputes.json"
      - name: "Get A PayPal Dispute"
        operation_id: "GetPayPalDispute"
        operation: "https://revcent.com/docs/api/v2#operation-GetPayPalDispute"
        schema: "https://revcent.com/documentation/files/api/operation/GetPayPalDispute.json"
  mcp:
    overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewPayPalDispute.md"
    operations:
      - name: "Get PayPal Disputes"
        operation_id: "GetPayPalDisputes"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetPayPalDisputes.md"
        available_via_ai: true
      - name: "Get A PayPal Dispute"
        operation_id: "GetPayPalDispute"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetPayPalDispute.md"
        available_via_ai: true
  bigquery_schema: "https://revcent.com/documentation/files/bigquery/dataset.json"
  bigquery_tables:
    - "paypal_dispute"
---

# PayPal Disputes

PayPal Disputes are RevCent item records that represent dispute activity from PayPal.

A PayPal Dispute is not the same as a PayPal Account or a PayPal Transaction. The PayPal Account is the connected PayPal configuration. The PayPal Transaction is the PayPal payment record. The PayPal Dispute is the item that represents a dispute, claim, or dispute update connected to PayPal activity.

## Why PayPal Disputes Are an Item

PayPal Disputes are items because each one represents a specific dispute record in RevCent.

A business may configure a PayPal Account once, but many PayPal Transactions and many PayPal Disputes can appear over time as customers purchase, request refunds, open disputes, or as PayPal updates dispute status.

The simplest distinction is:

- PayPal Account: the reusable PayPal connection.
- PayPal Transaction: an individual PayPal payment record.
- PayPal Dispute: an individual PayPal dispute record.

## Where PayPal Disputes Fit in RevCent

PayPal Disputes sit in the payment risk and support layer of RevCent.

They help connect PayPal dispute activity to the rest of the RevCent commerce graph, including PayPal Accounts, PayPal Transactions, Sales, Customers, Product Sales, Shipping, Tax, Campaigns, Shops, Fraud Detection, Pending Refunds, support workflows, automation, and reporting.

In the web app, PayPal Disputes can be viewed from the PayPal Disputes area under Payments.

PayPal Disputes can also be retrieved programmatically through the API and MCP/AI when a user needs automated lookup, support context, risk review, or reporting preparation.

## Core Business Purpose

The purpose of a PayPal Dispute is to make PayPal dispute activity visible and understandable inside RevCent.

A PayPal Dispute helps answer questions such as:

- Which PayPal Account is connected to this dispute?
- Which PayPal Transaction is involved?
- Which Customer, Sale, Campaign, or Shop is related?
- What products or shipments may be relevant?
- Has PayPal updated the dispute status or outcome?
- Is this dispute concentrated in a specific storefront, campaign, product, or customer segment?
- Does the dispute require support, fulfillment, refund, or risk review?

Without PayPal Disputes, PayPal dispute activity would be harder to connect to the rest of the customer and revenue history in RevCent.

## Automatic PayPal Dispute Monitoring

RevCent monitors connected PayPal Accounts for dispute activity.

When a PayPal Account is linked to RevCent, RevCent can check PayPal for new disputes and updates to existing disputes. This allows RevCent to keep PayPal dispute records connected to the rest of the account's payment and customer history.

This automatic monitoring matters because PayPal disputes often change over time. A dispute may be opened, updated, moved into a new status, receive new messages or details, or reach an outcome. RevCent's role is to bring that activity into the RevCent ecosystem so teams can see the dispute alongside related payments, orders, customers, shipping, and reporting context.

Conceptually:

- PayPal Account connects RevCent to PayPal.
- RevCent monitors PayPal for dispute activity and dispute updates.
- A PayPal Dispute item is created or updated in RevCent.
- The dispute can then be understood alongside PayPal Transactions, Sales, Customers, Campaigns, Shops, Shipping, and other related records.

## Relationship to PayPal Accounts

A PayPal Dispute is connected to a PayPal Account.

The PayPal Account is the feature that lets RevCent recognize and organize PayPal activity for the business. When a dispute is found for a connected PayPal account, RevCent can associate that dispute with the correct PayPal Account context.

This relationship helps answer:

- Which PayPal account generated the dispute?
- Which business, brand, or storefront does the account represent?
- Which Campaign or Shop should be considered when reviewing the dispute?
- Are disputes concentrated around a particular PayPal Account?

For businesses with multiple PayPal Accounts, this relationship is especially important because it keeps dispute activity organized by the correct account and operating context.

## Relationship to PayPal Transactions

A PayPal Dispute may be connected to one or more PayPal Transactions.

This relationship helps RevCent connect the dispute back to the payment activity that caused or relates to it. The PayPal Transaction provides the payment context. The PayPal Dispute provides the dispute context.

Together, these records help support and risk teams understand:

- The PayPal payment involved.
- The customer purchase behind the payment.
- The related Sale and Product Sales.
- Any Shipping, Tax, or refund context.
- Whether the dispute is isolated or part of a broader pattern.

## Relationship to Sales and Customers

A PayPal Dispute becomes more useful when it is connected to the related Sale and Customer.

The Sale explains what was purchased. The Customer explains who purchased it. The PayPal Transaction explains the payment. The PayPal Dispute explains the PayPal-side dispute activity.

This connected context helps teams respond more accurately to questions such as:

- What did the customer buy?
- Was the order shipped?
- Was tracking available?
- Was there already a refund or support issue?
- Is the customer associated with other disputes or risk signals?

## Relationship to Campaigns and Shops

PayPal Disputes can be understood in the context of Campaigns and third-party Shops.

This is important because PayPal disputes may not be evenly distributed across the business. Some campaigns, storefronts, products, or customer acquisition channels may produce more disputes than others.

Campaign and Shop context helps the business ask questions such as:

- Are PayPal disputes concentrated in one campaign?
- Are disputes coming from one shop or storefront?
- Do certain product offers or traffic sources create more dispute risk?
- Is one PayPal Account seeing more dispute activity than another?

## Relationship to Shipping and Fulfillment

Shipping and fulfillment context can be important when reviewing a PayPal Dispute.

For physical products, a dispute may require understanding whether an item shipped, whether tracking was added, whether delivery happened, or whether fulfillment created a support issue.

Because RevCent can connect PayPal activity with Shipping records, teams can review dispute activity with better order and delivery context.

## Relationship to Risk, Support, and Automation

PayPal Disputes are useful for risk review, customer support, and automation.

Support teams can use PayPal Disputes to understand a customer's payment issue in context. Risk teams can use them to identify dispute patterns. Automation and AI workflows can use them as signals for internal review, alerts, memos, or follow-up workflows.

At the ecosystem level, the important idea is that PayPal Disputes are not isolated PayPal records. They are part of the connected RevCent graph that can include Customers, Sales, PayPal Transactions, Shipping, Fraud Detection, Notes, Metadata, AI workflows, and reporting.

## API, MCP, and AI Context

The API and MCP/AI links exist so PayPal Disputes can participate in automated review and support workflows.

At the ecosystem level, this means PayPal Disputes can be found, reviewed, summarized, and connected to related records by approved automation. The important concept is that PayPal Disputes are available to the broader RevCent system, not only to a user manually viewing PayPal.

## BigQuery Reporting and Relationship Visibility

The `paypal_dispute` BigQuery table represents PayPal Dispute records for reporting and relationship analysis.

For ecosystem understanding, the most important use of this table is that it helps show how PayPal Disputes connect to other RevCent records, including PayPal Accounts, PayPal Transactions, Sales, Customers, Product Sales, Shipping, Tax, Campaigns, Shops, and related payment or risk records.

This supports business-level reporting such as:

- PayPal disputes by account, campaign, or shop.
- PayPal dispute volume over time.
- PayPal dispute reasons and outcomes at a business level.
- Dispute exposure connected to Sales and Customers.
- Dispute patterns connected to storefronts, products, fulfillment, or traffic sources.
- Comparison of PayPal dispute activity across brands or PayPal Accounts.

BigQuery should be treated here as the reporting and relationship layer, not as a place to document technical schemas or query examples.

## Ecosystem Relationship Summary

PayPal Disputes connect to the RevCent ecosystem like this:

- PayPal Dispute → PayPal Account: the PayPal account connection where the dispute was found.
- PayPal Dispute → PayPal Transaction: the PayPal payment activity related to the dispute.
- PayPal Dispute → Sale: the customer purchase connected to the disputed PayPal payment.
- PayPal Dispute → Customer: the buyer associated with the dispute.
- PayPal Dispute → Campaign: the business grouping used for attribution.
- PayPal Dispute → Third-Party Shop: the storefront or external shop context.
- PayPal Dispute → Product Sales: the specific products that may be relevant.
- PayPal Dispute → Shipping: fulfillment and delivery context.
- PayPal Dispute → Fraud Detection and risk workflows: possible risk review context.
- PayPal Dispute → BigQuery: reporting and relationship visibility.

## Summary

PayPal Disputes are RevCent item records for PayPal dispute activity.

RevCent automatically monitors connected PayPal Accounts for new disputes and dispute updates, then brings that dispute activity into the RevCent ecosystem. This allows PayPal Disputes to be understood alongside PayPal Accounts, PayPal Transactions, Sales, Customers, Campaigns, Shops, Shipping, risk review, support workflows, automation, and BigQuery reporting.


---
Document Parent Directory
* [Items](https://revcent.com/documentation/markdown/ecosystem/item/index.md) - Non-technical markdown documentation for items within the RevCent ecosystem. An item is an entity that is spawned as a result of a feature or operation conducted within the RevCent ecosystem.