Skip to content
adapters.io

PayPal to BigQuery integration for analytics-ready payments data

The PayPal to BigQuery integration from Adapters loads transactions, fees, refunds, and payouts from the PayPal Transaction Search API into partitioned BigQuery tables on an incremental schedule, so revenue, net-settlement, and cohort models run on a full history instead of a manual CSV export. Field mapping takes about a minute and no code is required.

Try it in the live demo

Field mapping auto-plugged · tap a port to rewire

5 sample records ready

Last updated July 2026

What running PayPal to BigQuery by hand costs you

  • The PayPal Transaction Search API returns data in paged windows with rate limits and a limited lookback, so backfilling a full transaction history into BigQuery by hand is fiddly to script.
  • PayPal reports gross amount, fee, and net separately, so a naive load into BigQuery leaves you reconciling fees before revenue and settlement numbers agree.
  • Refunds, chargebacks, and reversals land as later events against an earlier sale, and a flat dump into BigQuery misses those adjustments unless you re-pull the window.

The field mapping, out of the box

These cables are pre-wired when you pick the pair. Rewire any of them, or add your own, in the same visual data mapping tool you use for every adapter.

Input / PAYPAL

transaction_info.transaction_id
fct_transaction.transaction_id
transaction_info.transaction_amount.value
fct_transaction.gross_amount
transaction_info.fee_amount.value
fct_transaction.fee_amount
transaction_info.transaction_status
fct_transaction.status
payer_info.email_address
dim_payer.email
transaction_info.transaction_updated_date
fct_transaction.loaded_at

Transforms included

Incremental loads use the transaction updated date to re-pull the settlement window so refunds and reversals flow through; gross, fee, and net amounts cast to BigQuery NUMERIC with net computed as gross minus fee, currency codes stay ISO 4217, timestamps become TIMESTAMP in UTC, tables partition by transaction date, and writes MERGE on the transaction id so revenue and settlement models read one deduplicated history.

How it goes live

Three steps, minutes end to end, covered by flat data integration pricing from $49 a month.

STEP 01

Pick the pair

Connect PayPal and BigQuery with scoped credentials. About a minute each.

STEP 02

Confirm the mapping

The cables above are pre-wired. Adjust any field, preview the transform on sample records, done.

STEP 03

Schedule the sync

Hourly down to every minute, with retries, alerting, and a full log on every run.

Try it in the live demo Preloads PAYPAL → BIGQUERY with sample records

PayPal to BigQuery sync: common questions

How does the PayPal to BigQuery sync work?

The PayPal to BigQuery integration from Adapters loads transactions, fees, refunds, and payouts from the PayPal Transaction Search API into partitioned BigQuery tables on an incremental schedule, so revenue, net-settlement, and cohort models run on a full history instead of a manual CSV export. Field mapping takes about a minute and no code is required.

How much does the PayPal BigQuery integration cost?

Pricing is flat and monthly: Starter at $49, Growth at $149, Scale at $399. Every plan includes this pair, visual field mapping, and per-record logs. There are no per-task or per-row fees, so the bill stays the same as volume grows.

How often can Adapters sync PayPal to BigQuery?

Hourly on Starter, every 5 minutes on Growth, and down to every minute on Scale. Failed records retry automatically with backoff, and alerting plus a full per-record log come standard on every run.

Do I need to write code to connect PayPal and BigQuery?

No. Fields are auto-mapped the moment you pick the pair, and you can rewire any mapping visually before the first sync. Incremental loads use the transaction updated date to re-pull the settlement window so refunds and reversals flow through; gross, fee, and net amounts cast to BigQuery NUMERIC with net computed as gross minus fee, currency codes stay ISO 4217, timestamps become TIMESTAMP in UTC, tables partition by transaction date, and writes MERGE on the transaction id so revenue and settlement models read one deduplicated history.

More pairs from the API connector library

stripe quickbooks integration shopify netsuite integration salesforce hubspot integration airtable google sheets sync postgres to snowflake sync shopify quickbooks integration salesforce netsuite integration paypal quickbooks integration square quickbooks integration stripe netsuite integration hubspot quickbooks integration quickbooks to xero migration shopify xero integration salesforce to snowflake integration square netsuite integration hubspot xero integration salesforce to bigquery integration postgres to bigquery netsuite to snowflake integration quickbooks to bigquery integration stripe to snowflake integration shopify to snowflake integration quickbooks to snowflake integration hubspot to snowflake integration netsuite to bigquery integration stripe to bigquery integration shopify to bigquery integration paypal to snowflake integration square to snowflake integration square to bigquery integration netsuite to postgres integration salesforce to postgres integration xero to snowflake integration hubspot to bigquery integration xero to bigquery integration stripe to postgres integration snowflake to bigquery migration shopify to postgres integration hubspot to postgres integration bigquery to snowflake migration quickbooks to postgres integration xero to postgres integration square to postgres integration paypal to postgres integration snowflake to postgres

Browse the full api connector library, or request a pair you do not see.

PayPal and BigQuery, finally in agreement

Map the pair once and let it sync on schedule. Flat price from $49 a month, no per-task fees.

Try the live demo

No credit card required.