Add an IP reputation check to completed checkouts
Have Notis check an available checkout IP in Abuselpdb so a completed payment can carry a security signal into your review.
Trigger
Checkout Session Completed Trigger
Triggered when a checkout session is completed 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
A completed checkout can still warrant scrutiny, yet the IP context may sit outside the payment record you are reviewing.
- Adds IP reputation context to completed checkout reviews.
- Makes a targeted check based on a real checkout event.
- Reduces repeated manual lookups.
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 after checkout completion, check the associated IP reputation; ensure the IP is available in the event context.
- 4Pick the Stripe Checkout Session Completed trigger and choose where run reports go.
- 5Test with one real completed checkout and verify the needed IP is available.
Questions about this workflow
Will this workflow report an IP as abusive?
No. It checks reputation and shares returned data for review; it does not submit a report.
What if checkout data has no IP?
The workflow requires an IP address. Supply it in the prompt or event context when it is not present in the event.
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.