Decisions to make first
Does the launch use Stripe Billing?
The current Stripe Direct checkout creates a Stripe subscription Checkout Session. The selected offer must use an active recurring Stripe Price. If the customer is not using Stripe Billing, or the first offer is a one-time payment, stop before connecting the account and agree on a different checkout setup.Which Product and Price will be sold?
FloKit imports existing Stripe Products and Prices as read-only records. FloKit does not create or edit the customer’s Stripe catalog. Prepare one active recurring Price for the first launch and confirm:- Product name;
- Price ID;
- amount and currency;
- monthly or annual interval;
- trial length, if any;
- whether promotion codes are allowed; and
- the entitlement or access granted after purchase.
How will tax be handled?
FloKit does not activate Stripe Tax for the customer.- When Stripe reports that Stripe Tax is active on the connected account, FloKit enables automatic tax on the Checkout Session.
- When Stripe Tax is not active, FloKit omits automatic tax.
What is needed from the customer
The key must support the operations FloKit performs: validating the account,
reading Products and Prices, creating Checkout Sessions, provisioning the FloKit
webhook endpoint, reading subscription and tax status, and qualifying the
checkout payment domain when used.
Connect and qualify Stripe
1
Open Stripe Direct in FloKit
In the FloKit dashboard, select the correct App and environment, then go to
Governance -> Integrations and open Stripe Direct.
2
Enter the matching keys
Enter the Stripe secret key and publishable key for the same account and
environment.Use the test pair for sandbox qualification and the live pair only for the
approved production connection.
3
Validate the account
FloKit calls Stripe to confirm the account identity and whether the
credential belongs to Test or Live mode.
4
Sync the Stripe catalog
FloKit imports the account’s Products and Prices. Confirm that the expected
recurring Price is active and has the correct amount, currency, and
interval.
5
Map the first offer
FloKit creates or selects the App Package and binds it to the imported
Stripe Product and Price. Trial days and promotion-code support are set on
this binding.
6
Provision the webhook
Select Provision webhook in FloKit.FloKit creates or updates the connection-specific Stripe webhook endpoint
and stores the signing secret returned by Stripe. The customer does not
need to create a second webhook manually.
7
Qualify the connection
Run the Stripe qualification step. A connection must pass credential,
catalog, webhook, and provider checks before it can serve checkout traffic.
8
Run a controlled test purchase
Publish the test Flow, complete one Stripe test checkout, and confirm that
FloKit receives the provider event and records the expected transaction,
subscription, and entitlement state.
9
Repeat for Live
After the test environment passes, connect the live keys, sync the live
catalog, bind the live Price, provision the live webhook, and run the
separately approved live canary.
What the Stripe webhook does
The webhook is the authoritative return path from Stripe to FloKit. It is used to update payment, subscription, cancellation, refund, and entitlement state. A browser redirect after checkout is not treated as proof of payment. FloKit waits for the verified Stripe event and the canonical checkout status.Custom domains and wallets
When a published Flow uses a custom hostname, complete Stripe payment-method domain qualification for that exact hostname before launch. The FloKit fallback domain can be used for the first technical test so DNS does not block the connection.Ready for launch
Stripe Direct is ready when:- the connection reports the correct account and environment;
- the expected recurring Price is present in the synced catalog;
- the FloKit Package is bound to that Price;
- the webhook is provisioned;
- qualification reports
ready; and - one controlled test checkout is reflected in FloKit from the Stripe event.