Data Panda brings your PayPal data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
PayPal started in 1998 as Confinity, renamed itself PayPal in 2001, was acquired by eBay in 2002 and spun out as an independent public company again in 2015. The portfolio now includes the PayPal button and PayPal Business platform, Braintree for developer-side card processing, Venmo for peer and business payments in the US, Xoom for international remittance, Zettle for in-person card acceptance, Hyperwallet for mass payouts and Honey for consumer deal discovery. The merchant side supports more than two hundred markets and around two dozen currencies.
The reason to pull PayPal into a warehouse is that for most merchants PayPal is not the only payment rail. It is the wallet that sits next to the card, the iDEAL button and the Bancontact button on the same checkout page. Without a warehouse, PayPal revenue lives in the PayPal business dashboard, card revenue lives in the gateway dashboard, and the accounting ledger gets one net payout from each. In a warehouse, the PayPal transaction, invoice, product and subscription line up against the webshop order, the CRM account and the finance booking, and cross-channel revenue finally reads as one story.
PayPal, card and local methods on one timeline, with the fees and refunds already split out.
Let the rest of the stack react to what PayPal knows first.
Use PayPal history to predict the next drop-off and the next refund dispute.
Internal tools around payment data that otherwise stays in the PayPal business portal.
A list of concrete reports, automations and AI features we have built on PayPal data. Pick the one that matches your situation.
Does the PayPal payout on the bank match the transactions behind it?
Each PayPal payout is broken down to the underlying transactions, fees and refunds on the warehouse side. The gap finance used to hunt for between the PayPal business dashboard export and the bank statement becomes a single reconciled view, with the adjustment that caused any mismatch already tagged.
How does PayPal compare to card and local methods on our checkout?
Conversion, fee rate and refund share per payment method per country, on one timeline. The question of whether to push PayPal harder in the Netherlands or favour iDEAL stops being a hunch and starts being a number next to a cohort of real customers.
Which recurring PayPal agreements are about to churn?
Active, paused and cancelled PayPal subscriptions joined with renewal history and failed-retry events. Recurring revenue tied to PayPal billing agreements shows up on the retention board next to the card-based renewals, instead of hiding in the merchant account.
Every PayPal payout split to its transactions, fees and refunds, next to the bank line and the accounting booking. Month-end reconciliation between the PayPal dashboard, the ledger and the bank statement stops being a manual Excel job on the fifth of the month.
For account owners, PayPal payment and invoice state on the CRM record. Accounts that paid via PayPal show up next to card-paying accounts in the same customer view, with renewal history and failed charges tagged on the fiche instead of in a separate dashboard.
Payment-method mix per country, refund rate per product and dispute outcomes per account. The call on whether to push PayPal in a new market or hold back for a local method draws on the same warehouse data that finance and ecommerce use.
Every Shopify order paid through PayPal is matched to the PayPal transaction that funded it, and each PayPal payout is traced back to the orders it paid out for. Refunds and disputes flow back to the original order, so ecommerce margin numbers stop drifting from the finance view.
PayPal payouts land in Exact Online as bank journal entries, with PayPal fees split out and the underlying charges matched to the invoices they settle. Month-end reconciliation between PayPal, the bank and the ledger stops being a three-tab spreadsheet.
Successful PayPal charges, failed charges and refund events push into HubSpot as contact timeline activity and deal property updates. Customer success sees a failed renewal the same hour PayPal does, not on a weekly report pulled from the PayPal dashboard.
Failed PayPal charges, cancelled subscriptions and completed orders feed Klaviyo segments in near real time. Recovery emails go out the same day the charge failed, and customers who reactivate are removed from win-back flows instead of getting another reminder.
These are the 4 tables we currently pull from PayPal into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your PayPal data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Through the PayPal Business connector we pull the business-facing tables: transactions, invoices, products and subscriptions. That covers revenue reconciliation, invoice status, recurring agreements and catalogue joins. It does not cover the consumer-side of PayPal or Venmo peer activity, and anything that sits only in the PayPal resolution centre for disputes is exposed through the transaction dispute flag rather than the full case trail.
Yes. Each PayPal Business account is synced into its own schema in the warehouse, with a shared customer and product layer on top. Groups with one account per country or per brand keep per-entity reporting while getting one roll-up view across the group.
We review your PayPal setup and the systems around it. Together we pick the first thing worth building.