Skip to main content
Stripe Direct uses the customer’s own Stripe account. Choose this setup when the customer remains merchant of record. Stripe Managed Payments is a separate choice and requires the relevant eligibility and activation from Stripe.

​
Copy this prompt

Never paste Stripe keys into a chat. Enter them only in FloKit’s masked connection fields for the intended account and mode.

​
Before connecting

Prepare a Stripe administrator, matching secret and publishable keys, and an active recurring Product and Price for the subscription offer. Confirm amount, currency, billing interval, trial terms, promotion codes, tax settings, and access granted after purchase. Test-mode and Live prices are separate. The subscription setup in this guide uses an active recurring Price. The imported Stripe catalog is read-only in FloKit; edit provider Products and Prices in Stripe. Discuss a different billing model with your FloKit contact when selecting your checkout configuration.

​
Connect and test

1

Choose the account and mode

Select the correct App, open Governance → Integrations, and choose Stripe Direct. Confirm Test or Live mode before entering the matching secret and publishable keys.
2

Validate and sync

Run account verification and catalog sync. Confirm the account identity and the expected active recurring Price, including its amount, currency, and interval. Resolve a sync error before continuing.
3

Review the Package

Select Review and create Packages and connect the intended offer to the imported Stripe Product and Price. Review trial and promotion-code settings. This does not create or edit the Stripe catalog.
4

Provision notifications

Select Provision webhook. Use the FloKit-managed endpoint rather than creating a second destination manually. Resolve any permission error and complete the connection checks shown in FloKit.
5

Complete a controlled test

Use a published test Flow and the intended Stripe test mode. Confirm the expected payment, subscription, and access result in FloKit. A browser redirect is not payment confirmation.
6

Review Live separately

Before live traffic, confirm the Live account, Live Price, webhook, domain, and checkout settings. Obtain explicit approval before any real charge or ad activation.

​
Permissions and tax

The Stripe key must permit the account, catalog, checkout, subscription, tax-status, webhook, and payment-domain operations required by the selected setup. Use the verification result in FloKit to identify missing access. Never send the key in a support request. Configure required tax settings in Stripe and verify the checkout result. Connecting Stripe to FloKit does not itself activate Stripe Tax or settle your tax obligations.

​
Custom domains and wallets

In Governance → Domains, select Register with Stripe for the exact Flow hostname. This creates the payment-method domain only when it is absent. Continue only when the provider checkout-domain status is Approved. Approval for a parent or different subdomain is not approval for this hostname. See custom subdomain setup. If a Price is missing, check the connected account, mode, active status, and recurring billing interval before syncing again. If notifications fail, verify the key’s webhook permissions and use Provision webhook again.