Stripe
Source-reviewed capability blueprint for Stripe: Process payments through Stripe from supported Hoop checkout and payment surfaces. Confirm Hoop availability before setup.
This source-reviewed capability blueprint describes expected behavior and vendor requirements. It does not confirm that Hoop has enabled this connection for your account.
Overview
This profile describes the expected connection path if it is enabled in Hoop. Connect one Stripe account to process new Hoop-originated payments and record their outcomes. Hoop-created products and prices can be created in Stripe, while eligible live recurring Stripe prices can be imported manually. This is not a general Stripe ledger sync.
Expected data flow
Hoop payment request to Stripe
Expected when enabled: A supported Hoop checkout or payment surface sends the new transaction to Stripe for processing.
Stripe payment outcome to Hoop
Expected when enabled: A supported outcome for a Hoop-originated transaction can update the corresponding payment record and automation path in Hoop.
Hoop product or price to Stripe
Expected when enabled: A product or price created for a supported Hoop payment surface can create its corresponding Stripe record.
Eligible Stripe recurring price to Hoop
Expected when enabled: An eligible live recurring Stripe price can be imported manually as a Hoop product and price record.
Expected capabilities
- Expected when enabled: Process supported one-time and recurring Hoop payments through Stripe
- Expected when enabled: Record outcomes for new Hoop-originated transactions
- Expected when enabled: Create corresponding Stripe products and prices from Hoop
- Expected when enabled: Manually import eligible live recurring Stripe prices
Expected setup
- 01
Expected setup step when enabled: An active Stripe account
- 02
Expected setup step when enabled: Admin or authorization permission for the Stripe connection
- 03
Expected setup step when enabled: Stripe connected from Payments in the matching Hoop account
- 04
Expected setup step when enabled: The correct live or test mode and supported payment methods configured
Expected requirements and limits
- Expected constraint for this path: Only one Stripe account can be connected to each Hoop account.
- Expected constraint for this path: Historical and directly created Stripe payments do not backfill into Hoop.
- Expected constraint for this path: Only eligible live recurring Stripe prices can be imported; one-time and metered prices are excluded.
- Expected constraint for this path: Stripe-side price changes do not automatically update Hoop because Stripe price records are immutable.
- Expected constraint for this path: Payment methods, fees, currencies, and regional availability depend on Stripe and the connected account.
- Authentication
- Expected authentication if this path is enabled: Open Payments, choose Connect with Stripe, then sign in and approve the secure Stripe authorization.
- Account requirements
- Setup assumptions only; confirm Hoop access first. An active Stripe account that can process the required payment methods and currencies.
Sources
The linked sources and profile copy were reviewed on Aug 9, 2026. These sources document the connected service's rules and APIs; they do not confirm that the connection is enabled in Hoop or in a particular account. The next source review is due Nov 9, 2026.
