Add IP reputation context to failed payment intent reviews
When a payment intent fails, have Notis check the associated IP in Abuselpdb so you can review payment and threat context together.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
Check IP Reputation
Tool to check the reputation of an ip address. use when you need to determine if an ip address has been reported for abusive activity within a specified look-back period. example: checkip(ipaddress='8.8.8.8', maxageindays=90).
Why this helps
Payment failures demand investigation, but switching between Stripe and IP intelligence tools makes it easy to miss useful context.
- Adds an abuse reputation signal to payment failure review.
- Reduces manual app switching during triage.
- Keeps the check tied to a real Stripe failure event.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Abuselpdb once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe in one instruction that on a failed payment intent, check its associated IP reputation in Abuselpdb; the IP must be available in the event context.
- 4Pick the Stripe Payment Intent Failed trigger and choose where run reports go.
- 5Test with one real failed payment intent and confirm the IP is present.
Questions about this workflow
Does this workflow automatically block an IP?
No. It checks the IP reputation and returns context for review; no blocking action is listed.
What if the Stripe event does not include an IP address?
The check needs an IP address. Supply it in the prompt or event context if Stripe does not provide it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Abuselpdb. A trigger fires from one place; an action lands in another.
Stripe triggers
Abuselpdb actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Retrieve IP Blacklist
Tool to retrieve a list of the most reported ip addresses. use when building dynamic blocklists or threat intelligence feeds.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Bulk Report
Tool to submit multiple ip abuse reports in bulk. use when you need to report a large set of ips at once by uploading a csv file with required headers. csv must include columns: ip, categories, reportdate, comment.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Check Block
Tool to check the reputation of all ip addresses in a cidr range. use when you need aggregated abuse data for a network block.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Check IP Reputation
Tool to check the reputation of an ip address. use when you need to determine if an ip address has been reported for abusive activity within a specified look-back period. example: checkip(ipaddress='8.8.8.8', maxageindays=90).
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Clear Address Reports
Tool to remove all reports associated with a specific ip address. use when you need to purge your own abuse records after verifying control of the ip.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Get Abuse Reports
Tool to retrieve a list of abuse reports for a specific ip address. use when you need to fetch historic reports with optional filtering by status, date range, reporter, and pagination.
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 Abuselpdb, 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 Abuselpdb.