Integrations · Payments

Connect PayPal to Well

Name: PayPal entities in Well
Creator: Well

Import PayPal transactions, fees, and settlement reports for complete e-commerce reconciliation and visibility.

What Well pulls from PayPal

PayPal feeds payment, payout, refund into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke PayPal’s access.

From PayPal	In Well	Relation
Payment	Invoice	Matches
Payout	Bank deposit	Settles into
Refund	Credit note	Becomes
Customer	Company	Enriches

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: PayPal → Well

12 triggers from PayPal.

When a PayPal payment is captured
Captures completed PayPal payments with buyer, amount, and order id.
Trigger·Transaction
When a PayPal payment is refunded
Detects refunds against captured payments and links back to the order.
Trigger·Transaction
When a PayPal capture is denied
Surfaces denied captures with the denial reason for follow-up.
Trigger·Transaction
When a PayPal checkout completes
Picks up the moment a buyer finishes checkout, before the bank settlement.
Trigger·Transaction
When a PayPal payout settles
Tracks settlement batches with the covered captures and processing fees.
Trigger·Transaction
When a PayPal subscription renews
Detects recurring billing cycles and matches the new charge to the contract.
Trigger·Invoice
When a PayPal chargeback is filed
Flags the contested transaction and preserves the dispute trail.
Trigger·Transaction
When a PayPal capture is recorded with its merchant fee
Pulls the merchant fee out of the capture so net revenue is correct.
Trigger·Transaction
When a new buyer's first PayPal capture is recorded
Recognises a first-time buyer from the capture and prepares a customer record.
Trigger·Company

What Well does with your PayPal connection

Connect

Connect PayPal over OAuth (MCP DCR): Well registers a client through PayPal's OAuth Dynamic Client Registration and you approve on PayPal's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings payment, payout, and refund in from PayPal on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each PayPal entity into invoice, bank deposit, and credit note, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from PayPal lands in the workspace as invoice, bank deposit, and credit note you can search, chart, and automate.

Questions PayPal unlocks

Ask in plain language. Well answers from your connected PayPal connection, resolved against the rest of your stack.

Ask Well

Ask anything about your PayPal connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your PayPal connection…

Connect PayPal in three steps

01
Authorise PayPal via MCP
From Well's Connections panel, search for PayPal and click Connect. Well discovers PayPal's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on PayPal's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.paypal.com/mcp
02
Map your entities
Well's MCP client discovers payment, payout, refund, and customer from PayPal that PayPal's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
03
Use the data
Ask questions in conversation, build records tables, or let agents act on PayPal records. Because PayPal ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical PayPal records happens in the background. PayPal developer docs.

How PayPal stays secure with Well

Well connects to PayPal's MCP server (mcp.paypal.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived PayPal secret. Tokens are scoped to the payment, payout, refund, and customer PayPal exposes and refreshed server-side. Reads only, Well cannot modify or delete PayPal records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.paypal.com/mcp

Read PayPal records
Resources the PayPal MCP server exposes, scoped by your OAuth approval.
granted
Resolve payment, payout, refund, and customer across your stack
Match identifiers in PayPal against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete PayPal records
Not granted; PayPal is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store PayPal passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or PayPal’s admin panel.

Frequently asked questions about PayPal and Well

From Well, open Connections, find PayPal, and click Connect. Well discovers the OAuth metadata at mcp.paypal.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on PayPal's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in payment, payout, refund, and customer from PayPal and reshapes each entity into your workspace: payment becomes invoice; payout becomes bank deposit. Every record arrives with the source identifier preserved, so PayPal stays the source of truth while Well lets you query the data alongside the rest of your stack.

Once PayPal is connected, every record it exposes is queryable from conversation, filterable in records tables, and available to your agents through your workspace. The data stays linked to its PayPal source, so you can always trace a workspace record back to the original.

Well watches for updates to payments and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right invoice. Edits flow in incrementally; nothing is duplicated, and the PayPal source identifier is retained on every revision.

Well combines live PayPal events with periodic reconciliation reads of payment, payout, refund, and customer. New rows appear within seconds when PayPal pushes them; periodic reads catch anything a push missed. The first connect backfills history from PayPal in the background.

Open Connections > PayPal in Well and click Disconnect. Well calls PayPal's token revocation endpoint and stops calling PayPal immediately on its side; provider-side propagation to PayPal's admin panel varies by provider. The payment, payout, refund, and customer Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Well captures the original currency and the conversion rate PayPal applies, then reports both side by side. If you operate in EUR and PayPal settles in USD or GBP, the converted line and the raw line both land in the ledger, so reconciliation against the deposit currency works without manual FX math.