Confirm a Stripe payment after caller consent
When a caller has clearly authorized payment and the intent is ready, let Notis complete the confirmation step.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Why this helps
A payment that is ready for confirmation can be delayed while the caller's consent is relayed manually.
- Close the gap between clear consent and payment confirmation
- Require an identified payment intent
- Report when redirection or additional customer action is needed
Setup
Build it in a few focused steps.
- 1Connect Bolna and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the payment confirmation task.
- 3In one instruction, require clear caller consent and an identified payment intent before confirming.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real example and review the confirmation outcome in Stripe.
Questions about this workflow
Does every payment intent confirm without customer action?
No. Some payment methods require a customer redirect, and a return URL is necessary in that case.
Should the automation confirm an intent when consent is unclear?
No. The instruction should require clear caller consent and report ambiguous cases for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bolna to Stripe. A trigger fires from one place; an action lands in another.
Bolna triggers
Stripe actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel subscription
Cancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Create an invoice
Creates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations.
Create payment intent
Creates a stripe paymentintent to initiate and process a customer's payment; using `application fee amount` for a connected account requires the `stripe-account` header.
Create a price
Creates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` id or `product data`.
Create product
Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Connect any two apps with Notis in the middle.
Bolna and Stripe, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Stripe.