connect

This block is part of the stripe group and was last modified in core v15.0.0.

connect stripeconnection v15.0.0

Opens a Stripe connection. Point it at a Stripe service provider so the secret key stays in the provider store and never appears in this blueprint : the API key pin is the older way and leaves the key readable to anyone who can open the flow.

In pins 4 + flow

flow
flow
provider
value
Name of a Stripe service provider (Settings → Service Providers). Preferred: the secret key is resolved when a call is made and never lands on a pin.
api key
value
A literal Stripe secret key (sk_live_… or sk_test_…). Only used when no provider is named. Stored in plaintext in this blueprint.
connected account
value
Optional. Act on behalf of a Stripe Connect account (acct_…). Overrides the provider's own setting.
api version
value
Optional. Pins the Stripe API version for every call on this connection.

Out pins 3 + flow

flow
flow
connection
stripeconnection
success
condition
False when the named provider does not exist, is disabled, or is not a Stripe provider.
error
value

stripe

payment

card

checkout

subscription

billing

connect takes the NAME of a Stripe service provider, not a key: the secret is held by the cluster, resolved at the moment of the call and never placed on a pin or in a simulation trace. One provider per environment means moving from test to live is this one value. The success out pin drives a branch, because a provider that is missing, disabled or of the wrong purpose fails here rather than at the first API call.

Used in these guides

These documentation pages use or explain this block:

Service Providers

Version history

Introduced in v15.0.0.

Service documentation

External API reference This block wraps a third-party service. Click here for the service's own documentation of the underlying endpoint.

Back to stripe Return to the main group to view all sub-groups Back to stripe Return to the group to view all blocks within this group