Pay a deposit to confirm a booking
After the visitor picks a slot with the Google Calendar step, create a payment link for the deposit product and send it in the confirmation message.
The Stripe step creates a Stripe payment link or a hosted Checkout page while the visitor is still in the conversation, from a product in your Stripe account or an amount the chat worked out, and hands the link to the next message.
Build on the Free plan. The Stripe step runs on Pro ($39/month) and above.
The moment a visitor decides to buy is the worst moment to send them looking for a checkout page. The Stripe step closes the gap: once the chat knows what they want, it asks Stripe for a payment link or a Checkout page and shows it in the next message, so paying is one tap away.
Payment happens on Stripe's own hosted page. Card details go to Stripe, not to your chatbot or to Conferbot, and the payment lands in your Stripe account with your usual receipts, payouts and reporting.
Pick a product and price from your Stripe account and a quantity, and the step creates a Stripe payment link. Add a success URL to send buyers to your thank-you page afterwards.
Create a hosted Stripe Checkout page with success and cancel URLs, the visitor's email filled in, and optional shipping address collection.
Instead of a saved price, set an amount (in the smallest unit, so 4999 is 49.99), a product name and a currency. The amount can be a variable, such as a quote the flow calculated.
Create a Stripe customer from the visitor's email, name and phone, and keep the customer ID for later steps.
Fetch the products and prices in your Stripe account, so the builder shows them in menus and a flow can present them to the visitor.
Look up the payment status of a Checkout session or payment intent by its ID, for example when a visitor asks whether their order went through.
Whatever the step creates, its main value is saved to the variable you name under Save result: the payment URL for links and Checkout, the customer ID, or the payment status. Put that variable in a button or message, such as Pay securely here: ${payment_url}.
| Field | What it does |
|---|---|
| Stripe account | A saved Stripe secret key. Keys starting sk_test_ run in test mode; sk_live_ takes real payments. |
| Operation | Payment link, Checkout session, Create customer, List products, List prices, or Check payment. |
| Product and price | Chosen from menus loaded from your Stripe account. |
| Custom amount | Used instead of a saved price: the amount in the smallest currency unit, a product name and the currency. |
| Currency | USD, EUR, GBP, CAD, AUD or INR. |
| Quantity | How many of the item. |
| Success and cancel URLs | Where Stripe sends the buyer after paying, or if they leave Checkout. |
| Customer details | Email, name and phone, usually ${email}, ${name} and ${phone}. |
| Save result | The variable that receives the payment URL, customer ID or status. |
About ten minutes. You need a Pro or higher Conferbot workspace and access to your Stripe dashboard's API keys.
In the Stripe dashboard, open Developers, then API keys. Start with the test-mode secret key (it begins sk_test_) so you can try the flow without real charges.
Drag the Stripe step into the flow, choose Connect Stripe Account and paste the key. Conferbot checks it with Stripe before saving, and the key is stored encrypted for your workspace.
For a fixed product, choose Payment link and pick the product and price. For a total the chat calculates, choose Checkout session and set a custom amount from a variable.
Add your success page and, for Checkout, a cancel page. Without them Stripe has nowhere sensible to send the buyer after paying.
Save the result to a variable such as payment_url, then add a message or button after the step that uses it.
Pay with one of Stripe's test cards, check the payment in Stripe's test dashboard, then connect your live secret key and publish.
After the visitor picks a slot with the Google Calendar step, create a payment link for the deposit product and send it in the confirmation message.
Ask the questions that set the price (size, quantity, options), calculate the total into a variable, and create a Checkout session for that custom amount with the visitor's email prefilled.
Recommend a product with a quiz or questions, then create a payment link for the one the visitor chose, so the recommendation and the purchase happen in the same place.
Collect attendee details, create the Stripe customer, then send a payment link for the ticket. Log the registration with the Google Sheets step.
A Stripe secret key can act on your whole Stripe account, which is why Conferbot checks it against Stripe before saving and stores it encrypted for your workspace. The step uses it only to create payment links, Checkout sessions and customers, and to read products, prices and payment status.
A key starting sk_test_ is labelled as test mode in the dashboard. Keep test and live keys as separate connections so a test flow can never charge a real card.
Delete the key on the Integrations page to disconnect it. If you think a key was exposed, roll it in the Stripe dashboard under API keys and paste the new one into the step; the old key stops working at once.
The step creates the payment page; the payment itself happens on Stripe's hosted page. That keeps card data out of your chatbot, and it means the conversation shows a link rather than a card form.
Stripe Checkout sessions expire after a period (24 hours by default), while payment links stay valid until you deactivate them in Stripe. Use payment links for messages a visitor may come back to later. See expires_at in Stripe's Checkout Sessions API.
Custom amounts follow Stripe's convention of the smallest currency unit: 4999 means 49.99 in USD or EUR. Calculate totals in that unit before the step.
Products, prices and payments in test mode do not exist in live mode. After switching keys, re-pick the product and price from the live list.
If Stripe rejects the request, the conversation continues and the result variable stays empty. Show a fallback such as "we will email you a payment link" when it is blank.
| What you see | Why, and the fix |
|---|---|
| The key is rejected when connecting | Paste the secret key (it starts sk_test_ or sk_live_), not the publishable key, which starts pk_. |
| No products in the menu | The account has no active products in that mode. Create a product and price in Stripe, or check you connected the right mode, then reload the list. |
| The payment link variable is empty | Stripe returned an error, often a missing price or an invalid amount. Pick a price, or set a custom amount and product name. |
| Buyers land on a strange page after paying | No success URL was set. Add your own success and cancel URLs to the step. |
| The amount is 100 times too small or large | The custom amount must be in the smallest unit. 49.99 dollars is 4999. |
Yes. The Stripe step creates a Stripe payment link or hosted Checkout page during the conversation and saves its URL to a variable, which you show to the visitor in the next message or button.
No. The visitor pays on Stripe's hosted page, so card details go to Stripe only. Conferbot just creates the link through Stripe's API.
Yes. Instead of a saved price, set a custom amount, product name and currency. The amount can be a variable, written in the smallest currency unit, such as 4999 for 49.99.
The step offers USD, EUR, GBP, CAD, AUD and INR for custom amounts. Saved Stripe prices use the currency set on the price in Stripe.
Yes. Connect your test-mode secret key, which starts with sk_test_, pay with Stripe's test cards, then switch to the live key when the flow is ready.
Stripe is a native integration, included on Pro and above. You can build and preview the flow on any plan.
Paste your Stripe secret key into the Stripe step. Conferbot checks the key with Stripe before saving it to your workspace, encrypted.
The Check payment operation looks up the status of a Checkout session or payment intent by its ID, and saves the status to a variable the flow can use.
Stripe payment links stay valid until you deactivate them. Checkout sessions expire, after 24 hours by default, so links are the better choice for messages people may return to later.
Start free with Conferbot - the free plan includes 600 conversations a month and needs no credit card, so you can build the flow and test it today. The Stripe step switches on with Pro.
Checked against Conferbot's product and Stripe's documentation on November 3, 2026: Stripe Payment Links, Stripe Checkout, Stripe API keys.
Explore features, connect third-party tools, and browse ready-made templates.
Deep-dive pillar guides, real use cases, and the chatbot & AI glossary.
Guides for flows that end in a sale or a deposit.