Get customer
Retrieve selected customer fields or a deleted-customer marker.
Connector library
Stripe connector.
Look up Stripe customers, invoice balances and PaymentIntent state, with bounded customer/invoice pagination and selected results that exclude payment client secrets.
Connector download
Download Stripe
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
v0.2.0.1 Choose version
- Release
- 2026-10-03
- Package
- Implemented source
- Schema credentials
- Bearer token
- Connection settings
- API Base URL
- Package size
- 9 KB
- SHA-256
56dd7bb62491097db5fdc74045e02fe4d7c1a5fdbb2186b048e32c40256c85d6
Version history
What's new
- v0.2.0.1Latest · 2026-10-03 · Implemented source
Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.
- v0.2.0.0Earlier · 2026-10-03 · Implemented source
Look up Stripe customers, invoice balances and PaymentIntent state, with bounded customer/invoice pagination and selected results that exclude payment client secrets.
- v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Retained immutable historical scaffold archive.
Included in this version
Included actions
Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.
Search customers
Retrieve one page, optionally filtered by exact case-sensitive email.
Get invoice balance
Retrieve invoice status, amounts and available embedded line items.
List invoices
Retrieve one page with optional customer and invoice-status filters.
Get PaymentIntent status
Retrieve payment state and amounts, excluding client secrets and payment-method details.
Vendor API
API and access
Implementation considerations
- Use server-side actions, provider IDs, webhook verification, and duplicate protection for all payment workflows.
- Do not treat the initial create call as completion; use status retrieval and webhook events for final state.
- Confirm whether the customer needs payments, invoicing, subscriptions, payouts, or refunds before enabling actions.
- Stripe PaymentIntents guide payment collection and move through statuses during authentication and payment completion.
- CXFabric payment workflows should rely on server-side actions, idempotency, status checks, and webhooks for reliable completion handling.
Related connectors
More in CRM & Accounting
Support
Need help with Stripe?
Tell us what you need to connect or change.