Check payment intent details from source documents
Pull the payment intent referenced in an authorization document into the same workflow, with its Stripe details ready for review.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Retrieve payment intent
Retrieves a paymentintent by its id; `client secret` is required if a publishable api key is used.
Why this helps
Payment follow-up gets harder when the status is in Stripe and the reference is buried in a document.
- Reduce manual searches for payment status.
- Use the payment intent reference in the source document.
- Prepare a concise summary for the next follow-up.
Setup
Build it in a few focused steps.
- 1Connect Affinda and Stripe once in the Notis portal.
- 2Create an automation for payment intent lookups.
- 3Tell Notis to extract the payment intent ID, retrieve the Stripe payment intent, and report its relevant status details.
- 4Choose the webhook trigger and a channel for run reports.
- 5Test with one document referencing a known payment intent.
Questions about this workflow
What reference is required?
The document should include the Stripe payment intent ID. If a publishable API key is used, the retrieve action also requires the client secret.
Does retrieving the payment intent change its status?
No. This action retrieves the intent details.
What if the document has no payment intent ID?
Ask Notis to flag the item for follow-up instead of guessing which payment intent it refers to.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Affinda to Stripe. A trigger fires from one place; an action lands in another.
Affinda 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.
Affinda 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.