Skip to main content
Gavel uses Bundles with Stripe Connect as the standard way to collect payment from clients. You create a bundle, set a flat-rate price, connect your Stripe account, and choose exactly where in the workflow sequence the payment step appears — before the client begins, or just before documents are generated. This page walks you through the full setup and explains how to test your paywall before going live.
The older Stripe Paywall Question feature is deprecated. Existing workflows that use it will continue to work, but you cannot add new Stripe Paywall Questions to new workflows. If you have an existing workflow with a legacy Stripe question that you want to include in a bundle, remove the old paywall question first, then configure pricing through the bundle instead.

Step 1 — Connect Stripe to your Gavel account

Before you can charge clients, you need to link a Stripe Connect account to Gavel. This is a separate onboarding from a standard Stripe account.
1

Start creating a paid bundle

Go to the Bundles page from the Dashboard and click + New Bundle. Fill in the bundle name and description, select at least one workflow, and click through to the Bundle Pricing step.
2

Select Flat Rate

Choose Flat Rate as the pricing option. If your Stripe Connect account has not yet been linked, Gavel displays a yellow banner with a link to begin Stripe onboarding.
3

Complete the Stripe onboarding

Click the link in the banner. You will be taken through the Stripe Connect setup flow — entering your business details, bank account information, and identity verification. Once you complete onboarding, Stripe redirects you back to your Gavel bundles page automatically.
If you previously used the legacy Stripe integration (Stripe Paywall Questions), you connected a standard Stripe account at that time. To use bundles with Stripe Connect, you will onboard a Stripe Connect account, which links through your existing Stripe account.

Step 2 — Configure the payment step

Once Stripe Connect is linked, you set the price and decide where in the user’s journey payment is collected.
1

Enter your flat rate

With Stripe connected, enter the amount you want to charge. Gavel currently supports a single flat-rate price per bundle.
2

Choose when payment is required

Select where the payment step appears:
  • Before the beginning of a workflow — the client pays before they can start any workflow in the bundle.
  • Before documents are generated — the client completes the questionnaire first, then pays before receiving their documents.
You can add more than one payment step by clicking Add another payment step, allowing you to charge at multiple points (for example, a deposit before starting and a final payment before document delivery).
3

Save the bundle

Click Finalize to save. Your bundle is now live with payment gating enabled.

Step 3 — Share or embed the paid bundle

Once your paid bundle is configured, share it with clients in one of two ways:

Share a direct link

Click the copy icon next to the bundle on the Bundles page and paste the URL into an email or website button. Clients who open the link see the bundle’s start page and pricing before they begin.

Embed a bundle card

Click the Generate Code icon (</>) on the Bundles page to get HTML snippets you can embed on any web page. The card displays the bundle name, description, and a call-to-action button.

Step 4 — Test your paywall

Before sharing a paid bundle with real clients, test the payment flow to confirm it works correctly.
1

Enable Test Mode

If you are using a legacy Stripe Paywall Question, ensure the Test Mode checkbox is checked on the Stripe payment question in your workflow builder. For bundles with Stripe Connect, use your Stripe dashboard’s test mode environment.
2

Run the bundle

Open the bundle link or click Run on the Bundles page to start the workflow as a client would.
3

Enter Stripe test card data

When the payment screen appears, use Stripe’s test card numbers. A commonly used test Visa card is:
FieldValue
Card number4242 4242 4242 4242
ExpiryAny future date
CVCAny 3-digit number
ZIPAny 5-digit number
Stripe provides a full list of test card numbers for different scenarios (declines, authentication challenges, etc.) in their documentation.
4

Verify the flow

Confirm that the payment step appears at the correct point in the workflow and that the workflow proceeds as expected after a successful test payment.
5

Disable Test Mode before going live

If you are using a legacy Stripe Paywall Question, uncheck Test Mode on the question before sharing the workflow with real clients. For Stripe Connect bundles, ensure your Stripe account has completed live mode onboarding.
Test payments do not create real charges, but they do create test records in your Stripe dashboard. Verify you are in Stripe’s test mode view when reviewing those records — live mode will not show test transactions.

Viewing payments in Stripe

After real clients complete payments, all transaction data is available in your Stripe dashboard at dashboard.stripe.com. Use the toolbar to navigate to:
  • Products — your Gavel bundles appear here as Stripe products
  • Payments — a log of every charge
  • Customers — client records created when they pay
  • Reports — revenue summaries and exports