Skip to main content
Technical Preview

Overview

A deferred, non-priority client connector for a curated eight-operation slice of the Stripe API: balance, charges, PaymentIntents, customers, and products. It is kept as a reference. It is not part of the IIoT or enterprise-system catalog rollout.
Stripe calls need a secret key (sk_test_… or sk_live_…). A missing or invalid key returns HTTP 401. This template has not been verified with a live key. Prefer PaymentIntents over creating legacy Charges.

Basic Syntax

Events

Auth

Bearer secret key:
string
required
Stripe secret key. Publish it as api_token from a Hub secret. Never commit sk_ keys. Dashboard: Stripe API keys.
Balance smoke payload:
Create PaymentIntent (body is {payload}). Stripe also accepts form-urlencoded; this template sends application/json:

Try it

  1. Add the connector on a lab broker that is allowed to call Stripe.
  2. Publish the balance payload to integrations/stripe/request/Getbalance.
  3. Subscribe to integrations/stripe/response/Getbalance.
  4. Read a charge or intent by publishing api_token plus charge or intent to the matching request topic.
Probes: GET /v1/balance with no key returned HTTP 401, and an invalid sk_test_ Bearer also returned HTTP 401. lot_lint reported no findings on StripeRestApi.
Last modified on October 21, 2026