Follow signed payment authorization with confirmation
When authorization paperwork is complete, send the relevant payment intent through the confirmation step with the required details.
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 completed authorization can be missed while payment processing waits for a separate confirmation step.
- Reduce delay after payment authorization is completed.
- Keep the authorization handoff connected to the payment intent.
- Support payment methods that require customer redirection when a return URL is supplied.
Setup
Build it in a few focused steps.
- 1Connect ActiveMerge and Stripe once in the Notis portal.
- 2Create an automation and describe that a completed authorization should confirm the supplied Stripe payment intent, including a return URL when needed.
- 3Choose the webhook trigger and a report channel.
- 4Send one real authorization completion request to test confirmation.
Questions about this workflow
Is a return URL always required?
A return URL is necessary when the payment method requires customer redirection.
What must the request identify?
Include the Stripe payment intent to confirm and the required confirmation details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link ActiveMerge to Stripe. A trigger fires from one place; an action lands in another.
ActiveMerge 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.
ActiveMerge 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.