01
MRR you can audit
New, expansion, contraction and churn MRR, each traceable to the underlying invoices.
MRR movements
Finance
PayPal + Kimo
Transactions, disputes and payouts. Turn invoices, charges and subscriptions into MRR, retention and margin that match your books.
- Auth
- OAuth 2.0
- Sync
- Hourly
- Setup
- ≈ 2 min
Live demo workspace with fictional data · no signup, no credentials needed
kimo / connectors / paypalSyncing
Sync loghourly
- Succeeded:invoices+693 rowsnow
- Succeeded:accounts+1,474 rows2m ago
- Succeeded:transactions+2,255 rows4m ago
- Succeeded:invoices+636 rows6m ago
Rows synced · 30 days
73M
Workspaces
23%
What you can do
What teams build with PayPal
PayPal on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.
02
Net revenue retention
Cohort NRR by plan and segment, refreshed automatically for the board pack.
NRR by cohort
03
Failed payment alerts
Catch spikes in failed charges or overdue invoices before they become churn.
Dunning watch
Objects & tables
Exactly what gets synced
Kimo maps PayPal into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.
3 tables · 14 fields
Tables
invoices
Incremental≈ 352,000 rows| Field | Type | Notes |
|---|---|---|
| id | id | Primary key |
| customer_id | id | References customer |
| amount_due | decimal | Measure |
| status | enum | Low-cardinality dimension |
| due_date | date | Incremental cursor |
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model
From raw PayPal tables to a certified metric
A starter model Kimo suggests the moment PayPal is connected. Every join is editable.
PayPal · Recurring revenue
Invoices and subscriptions joined with accounts to produce MRR movements.
- PayPalinvoices
- PostgreSQLaccounts
- HubSpotdeals
Model
customer_id · account_id
Measuresmrrnew_customers
MRR · last 30 days
$221.2K+5.8% wk/wk
Fictional data · hover the chart for daily values
Setup
Connect PayPal in 2 min
No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.
- 1
Click “Connect PayPal”
You are redirected to PayPal to sign in. Kimo never sees your password.
- 2
Approve read-only scopes
Kimo requests the narrowest scopes available. You can revoke access at any time.
- 3
Pick accounts
Choose which accounts to sync. Add more later without reconnecting.
- 4
First sync and schema mapping
Kimo backfills history, maps invoices and suggests joins with your other sources.
Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.
Connect PayPal
Step 2 of 3 · Kimo demo workspace
Kimo wants read-only access to your PayPal account
read-only accessread
Accounts
- Northwind · PayPal
- Northwind EU · PayPal
Read-only access
Illustration only · placeholder values, never real secrets
Works great with
Pair PayPal with the rest of your stack
Kimo suggests these joins automatically when both sources are connected.
FAQ
PayPal questions, answered
By default Kimo syncs PayPal hourly. You can change the schedule per table, or trigger a sync manually from the connector page.
PayPal · OAuth 2.0 · Hourly
See your PayPal data in Kimo in 2 min.
Try it on the live demo workspace first, then connect your own account when you are ready.