Skip to main content
Use the @bijection/connectors/paypal entrypoint to declare PayPal resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Transactions

search: Transaction Search in 31-day windows behind the three-hour lag

The following example matches configuration standard.

Configuration: standard

Case: paypal/transactions/search/standard. Connection and resource configuration are declared by this exact case. Credential kind: paypal. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: transactions
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Disputes

pull: Disputes by update_time with a carried position

The following example matches configuration standard.

Configuration: standard

Case: paypal/disputes/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: paypal. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: disputes
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: webhooks

Case: paypal/disputes/pull/webhooks. Connection and resource configuration are declared by this exact case. Credential kind: paypal. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: disputes
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection holds a paypal OAuth client-credentials grant (POST /v1/oauth2/token) for api-m.paypal.com or the sandbox. transactions.search reads Transaction Search for balance-affecting records in windows of at most 31 days. A pass walks from its start (since, which must lie within PayPal’s three years, or revisitHours, default 72, before where the previous pass stopped) to three hours before the pass began, PayPal’s stated availability lag. The window and page number live in the pass’s position, so every page of a window repeats the window’s request exactly. Identity is the account_number of a one-second search at since, so identification fails visibly once since leaves PayPal’s three years. A transaction is keyed by transaction_id, unique among balance-affecting records, and versioned by transaction_updated_date; amount and fee are PayPal’s exact decimal text with the currency. Status S, P, V and D are kept as stated; a status change older than the revisit window is not read again. disputes.pull reads every dispute on the first pass and afterwards update_time_after five minutes before the latest update_time read (PayPal accepts it within 180 days). Pages are newest-created first and numbered; a dispute created mid-pass repeats one row, never skips one. A query past 50 pages (2,500 disputes) is refused rather than read in part. A disputes listing names no merchant, so this resource’s connection is its own identity namespace. Status, state and life cycle stage are kept as stated; the amount is exact decimal text. Nothing is withdrawn. With updates: "webhooks" on disputes, a PayPal webhook delivery asks for the next pass. PayPal signs transmission id|transmission time|webhook id|CRC-32 of the body (RSA PKCS#1 v1.5, SHA-256) under the certificate paypal-cert-url names; the platform fetches it only from /v1/notifications/certs/ on PayPal’s API hosts (api.paypal.com and api-m.paypal.com, or the sandbox pair), checks its validity period and caches it, and never posts the event back to PayPal. Install the webhook id PayPal shows for the webhook as the listener’s signing credential. The CRC-32 is a checksum, not a digest, so a delivery proves only that a read is due; the event id is the delivery identity and the signed transmission time bounds replay to a day. Transactions declare no webhook: the search lags three hours, so a hint could not see the change. The verifier passes PayPal’s SDK vector in the platform’s unit tests; the production certificate host is PayPal’s API host by assumption, not by an observed delivery. Nothing here has run against PayPal or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.