PayPal logoRamp logoPayPal to Ramp
AvailableNative · PayPalNative · Ramp

Bring PayPal invoices into Ramp

PayPal settlements arrive in Ramp with the underlying charge breakdown preserved, so the bank reconciliation sees gross revenue and processor fees as separate lines.

About PayPal and Ramp

PayPal logo
PayPal
Source

The PayPal integration connects your payment account to Well via MCP, importing transactions, fees, settlements, and refund data.

Ramp logo
Ramp
Target

The Ramp integration connects your corporate card and expense management platform to Well.

Why this pair

Invoices and payments run through PayPal, but the documents behind Ramp spend still have to be matched by hand.

Well reads the invoices and transactions from PayPal along with the companies behind them, and your existing records from Ramp, then forwards each document to your Ramp email-in address. The document arrives with the counterparty resolved and checked against Ramp spend, so a receipt lands against the charge it belongs to rather than as a fresh unknown.

What Well does between PayPal and Ramp

  • One-way: PayPal into Well into Ramp
  • Sync mode: Real-time MCP push
  • Events arrive in seconds
PayPal logo
Trigger from PayPal
9 events · pick one
Well engine·recipe·When a PayPal payment is captured
Source
from payment · live webhook
Quantica Energy
via PayPal
Payment
When a PayPal payment is captured
ch_1q5nk · 22 Apr 2026€1,284.00
Extract
6 fields read from PayPal
6 fields read
  • CustomerQuantica Energy
  • Charge date22 Apr 2026
  • Charge amount€1,284.00
  • CurrencyEUR
  • Processing fee€37.24
Enrich
against your historical record graph
4 fields added
  • Customer recordQuantica Energy
  • Domainquantica.energy
  • Tax idES45612378900
  • Sales journalVE · 2026
Confidence97%
<55% refused5585% review85% auto-posts
Post
reconcile as draft bills
Create a draft bill in Ramp Bill Pay
auto-posted
posted
  • TypeBill
  • VendorQuantica Energy
  • Amount€1,284.00
  • LedgerVE · 2026
  • Source docattached
  • Confidence97%
audit linkto Ramp
Ramp logo
Action in Ramp
1 compatible with this trigger
Create a draft bill in Ramp Bill Pay

Workflows PayPal and Ramp unlock together.

01Featured

Bring a PayPal invoice in

Well reads an invoice from PayPal and forwards it to your Ramp email-in address, so the document is filed without anyone re-keying it.

02

Match against records Well reads from Ramp

Well reads your companies and transactions from Ramp and checks each PayPal document against them, so a receipt lands against the spend it belongs to.

03

Keep the PayPal reference attached

The PayPal transaction reference travels with the document forwarded to Ramp, so each entry traces back to the payment it came from.

04

Catch a duplicate early

Well checks a PayPal invoice against what it has forwarded and what Ramp holds, so the same document is not filed twice.

16 signals and actions across PayPal and Ramp

  • When a PayPal payment is refunded

    Pulls from PayPal transaction events. Detects refunds against captured payments and links back to the order.

    Trigger·Transaction
  • When a PayPal payment is captured

    Pulls from PayPal transaction events. Captures completed PayPal payments with buyer, amount, and order id.

    Trigger·Transaction
  • When a PayPal subscription renews

    Pulls from PayPal transaction events. Detects recurring billing cycles and matches the new charge to the contract.

    Trigger·Invoice
  • When a new buyer's first PayPal capture is recorded

    Pulls from PayPal transaction events. Recognises a first-time buyer from the capture and prepares a customer record.

    Trigger·Company
  • When a PayPal checkout completes

    Pulls from PayPal transaction events. Picks up the moment a buyer finishes checkout, before the bank settlement.

    Trigger·Transaction
  • When a PayPal payout settles

    Pulls from PayPal transaction events. Tracks settlement batches with the covered captures and processing fees.

    Trigger·Transaction
  • When a PayPal capture is recorded with its merchant fee

    Pulls from PayPal transaction events. Pulls the merchant fee out of the capture so net revenue is correct.

    Trigger·Transaction
  • When a PayPal payment is held pending review

    Pulls from PayPal transaction events. Detects pending captures and waits for the resolution before posting.

    Trigger·Transaction
  • When a PayPal capture includes a currency conversion

    Pulls from PayPal transaction events. Pulls the FX rate and conversion fee from the capture.

    Trigger·Transaction
Reference
Field mapping for PayPalRamp
4 fields across 1 record type, open to see the full table.

Transaction fields

4 fields flow from PayPal into Ramp.

PayPal fieldRamp field
capture.amount.currency_codetransaction.currency_code
capture.create_timetransaction.user_transaction_time
capture.idtransaction.id
capture.seller_receivable.feetransaction.amount

Connect PayPal and Ramp in three steps.

  1. PayPal logo1

    Connect PayPal

    Click Connect with PayPal; the PayPal MCP server registers a Well client automatically. PayPal's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.

    • AuthOAuth 2.0
  2. 2

    Map your accounts

    Well discovers PayPal's completed payments, refunds, disputes, holds, and currency-conversion events and the the Ramp Bill Pay drafts queue awaiting approval. Payouts are anchored to the matching bank deposit with the fee split into its own ledger line, so reconciliation shows gross revenue and processor fees separately.

    • Auto-post above85% confidence
    • Overridemanual anytime
  3. Ramp logo3

    Connect Ramp

    Click Connect with Ramp; the Ramp MCP server registers a Well client automatically. Ramp's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.

    • AuthOAuth 2.0
    • First sync~30 min

How PayPal and Ramp stay secure with Well

Well connects to PayPal through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived PayPal secret; the server refreshes its own tokens on each session. Well's storage region is configured per workspace regardless of where PayPal and Ramp host theirs.

MCP server authStorage region per workspaceGDPR-aligned
Scopes Well requestsmcp.paypal.com/mcp
  • Read PayPal records

    Scoped to completed payments, refunds, disputes, holds, and related records. No access to anything else in your PayPal account.

    granted
  • Deliver documents to your Ramp inbox

    Well forwards the extracted document to your Ramp email-in address; Ramp reads draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and related records from it and you review and post. No write credential to Ramp is requested.

    granted
  • Modify or delete PayPal records

    Not granted. PayPal is read-only on Well's side; the source of truth never moves.

    refused
  • Read other workspaces' data

    Encryption keys are per-workspace; another tenant's records are inaccessible by design.

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

Frequently asked questions about PayPal and Ramp on Well

01What PayPal data does Well pull into Ramp?
PayPal streams completed payments, refunds, disputes, holds, and currency-conversion events to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Ramp as draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and line items pre-filled by Ramp's OCR, with the PayPal event ID preserved on the entry for audit.
02How often does PayPal data sync to Ramp?
PayPal pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches Ramp within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
03How does Well match PayPal records to entries in Ramp?
Well scores every candidate match between PayPal records and existing Ramp entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Ramp updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.
04What happens to historical PayPal data when I first connect to Ramp?
PayPal exposes the last full year through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Ramp ledger, and re-running the backfill is safe because Well tracks the PayPal record IDs and updates existing Ramp entries instead of duplicating them.
05Does Well handle multi-currency records between PayPal and Ramp?
PayPal carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.
06How does Well authenticate with PayPal and Ramp?
PayPal's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. PayPal and Ramp together cover multiple regions; Well's storage region is configured per workspace.
PayPal logoRamp logo

Connect PayPal and Ramp

Link both tools to Well so PayPal invoices reach Ramp already matched to spend.

  • Read-only scopes on PayPal
  • AES-256 at rest, TLS 1.3 in transit
  • GDPR-aligned
  • Revocable Ramp access in one click