PayPal to Snowflake integration for analytics-ready payments data

Through the PayPal Transaction Search API, which returns transaction level detail with fees, then staged as files and merged into Snowflake. PayPal has no direct Snowflake integration, so a connector authenticates with your REST app credentials, pages through the transaction history, and maintains an incremental watermark on transaction date.

The Transaction Search API limits how far back and how wide a single query can reach, so a multi year backfill has to be chunked into date windows rather than requested in one call. Plan the initial load as a sequence of windows with retry handling, and keep the incremental job on a short rolling window afterwards.

As their own column and their own amount, never netted into the gross. PayPal deducts fees before settlement and applies additional fees on currency conversion, so a table with only the net figure cannot reproduce gross revenue or fee ratios. Keep gross, fee and net as separate numeric columns.

An explicit NUMBER with precision and scale, such as NUMBER(19,4). Snowflake's NUMBER type defaults to a precision and scale of (38,0), which silently truncates the cents if a loader relies on the default. Currency codes belong in their own column so multi currency accounts can be reported correctly.

The PayPal to Snowflake integration from Adapters loads transactions, fees, refunds, and payer detail from the PayPal Transaction Search API into Snowflake tables on an incremental schedule, so revenue and reconciliation models read a full history instead of downloading activity reports by hand. Field mapping is no-code.

Yes. This PayPal to Snowflake connector ships prebuilt: the field mapping is wired the moment you pick the pair, transforms are included, and the first sync can run within minutes. No code or engineering sprint required.

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.

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.

No. Fields are auto-mapped the moment you pick the pair, and you can rewire any mapping visually before the first sync. Incremental loads page the PayPal Transaction Search API in 31-day windows using the updated date so each run only pulls new and changed activity; amount and fee strings cast to Snowflake NUMBER, currency codes carry through, ISO 8601 timestamps become TIMESTAMP_NTZ in UTC, and fees join to their transaction so gross, fee, and net models read one deduplicated table.