IP Blacklist Lookup API + Stripe Integration

Why connect them

The IP Blacklist Lookup API in Stripe.

Stripe is the leading payment infrastructure for the internet. Integrating APIs with Stripe enables enhanced fraud prevention, customer validation, and payment intelligence. Protect your revenue with data-driven payment workflows.

What you can build

Workflows worth wiring.

Validate customer emails before processing subscriptions

Check customer locations against payment addresses for fraud detection

Enrich customer profiles with data for better risk assessment

Verify business information for B2B payment processing

Templates

Ready-made ideas.

New payment received in Stripe Fetch IP blacklist lookup for customer IP → add isIPBlacklisted and threatLevel to Stripe payment metadata

IP Blacklist Check on Stripe Payments

Attach IP blacklist status to Stripe payments for fraud screening and risk assessment.

New payment received in Stripe Fetch IP blacklist lookup → if isIPBlacklisted is true, flag payment with threatLevel in Stripe metadata

Stripe High-Risk Payment Alert

Flag Stripe payments from blacklisted IPs with their threat level for manual fraud review.

Setup

Connect it in a few steps.

Set up with Zapier

1
Set the trigger. Create a Zap with Stripe as the trigger app and "New payment" as the event. Connect your account.
2
Add the API action. Add APIVerve as the action, select the IP Blacklist Lookup API, and map your trigger data to the request.
3
Send it back. Add a second Stripe action for "Create charge" and map the returned fields (like ipAddress) into it.
4
Test & turn on. Test the Zap with real data to confirm the mapping, then turn it on.

Set up with Make

1
Add the trigger. Create a scenario and add a Stripe module set to "New payment". Authenticate your account.
2
Call the API. Add an HTTP module pointing at api.apiverve.com/v1/ipblacklistlookup with your x-api-key header. Pass the trigger's data as the input.
3
Parse & map. Add a JSON module to read the response, then a Stripe module for "Create charge". Map fields like data.ipAddress into place.
4
Activate. Run once to confirm the mapping, then switch the scenario on and set its schedule.

Set up with n8n

1
Add the trigger node. Start a workflow with a Stripe trigger node for "New payment" and connect your credentials.
2
Add an HTTP Request node. Point it at api.apiverve.com/v1/ipblacklistlookup using Header Auth (x-api-key). Feed in the trigger data.
3
Map with expressions. Add a Stripe node for "Create charge" and reference the response with expressions such as {{ $json.data.ipAddress }}.
4
Execute & activate. Execute manually to verify, then activate the workflow for production.

The payload

What Stripe receives.

ipAddress"185.220.101.1"

isIPBlacklistedtrue

inboundfound, description

outbound—

threatLevel"high"

ipDetailsip, country, region, timezone, city, coordinates, countryName, regionName, postalCode, continent, continentName, accuracyRadius

IP Blacklist Lookup API + Stripe