Skip to main content
Use the @bijection/connectors/stripe entrypoint to declare Stripe 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.

Customers

pull: Pull and reconcile

The following example matches configuration standard.

Configuration: standard

Case: stripe/customers/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: stripe. 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: customers
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: minimal

Case: stripe/customers/pull/minimal. Connection and resource configuration are declared by this exact case. Credential kind: stripe. 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: customers
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

notified: Notifications with reconciliation

The following example matches configuration standard.

Configuration: standard

Case: stripe/customers/notified/standard. Connection and resource configuration are declared by this exact case. Credential kind: stripe. 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: customers
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. Install the API key as a stripe credential (stripe.credential(name)); the API origin is fixed. Selected fields control stored data, not provider expansion. Semantics come from the admitted declaration: customer lists are live record observations continued from the last record key, with no snapshot or deletion claim; a customer is deleted only when Stripe answers deleted: true during point read-back. Signed customer.* events are refresh hints, deduplicated by event id. Inspect the installed source for its exact profile and limits. Authoring: this connector keeps its lower-level defineIntegration recipe. http.records does not express Stripe’s last-record-key continuation, its deleted: true tombstones or its point read-back, and adding provider flags for them would not generalize.

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.