Find a contact for a failed payment intent
Get the likely customer contact in view while you investigate a failed payment.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
Get Contacts
This tool retrieves a list of contacts from amcards. it is used for managing contacts by providing details like limit, skip, and filters (e.g., last name, first name, email). the tool returns an array of contact objects containing fields such as id, first name, last name, email, created at, and updated at.
Why this helps
Payment failures create urgent follow-up work, and looking up the person separately can break your focus.
- Start contact research from a failed payment intent event.
- Summarize potential matches instead of manually scanning the contact list.
- Flag when the available event details are insufficient for a confident match.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Amcards once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for payment failure lookup.
- 3Tell Notis to search Amcards contacts using customer details present in a failed payment intent and report likely matches or missing details.
- 4Choose the Stripe Payment Intent Failed trigger and select where run reports should go.
- 5Test with one real failed payment intent and check the reported match.
Questions about this workflow
Is this different from a failed charge trigger?
Yes. This workflow starts from the Stripe Payment Intent Failed event, while a failed charge uses the legacy Charges API event.
Can it contact the customer?
No. The listed Amcards action retrieves contacts only. Use the report to decide on the next step.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Amcards. A trigger fires from one place; an action lands in another.
Stripe triggers
Amcards actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Cards
This tool retrieves a list of all cards associated with the authenticated account. the action is completely independent and doesn't require any external resource ids or parameters beyond authentication. it allows users to monitor, track, and manage their cards.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Contacts
This tool retrieves a list of contacts from amcards. it is used for managing contacts by providing details like limit, skip, and filters (e.g., last name, first name, email). the tool returns an array of contact objects containing fields such as id, first name, last name, email, created at, and updated at.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Product Created Trigger
Triggered when a product is created in Stripe
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Connect any two apps with Notis in the middle.
Stripe and Amcards, 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 Amcards.