MX Lookup API + Stripe

Send the response straight into Stripe — connected through Zapier, Make, or n8n, no code required.

WhenStripeNew payment
trigger
RunMX Lookup APIReturns the response
action
ThenStripeCreate charge

The MX 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.

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

Ready-made ideas.

New payment received Look up MX records → flag if no records

Check customer domains on payment

When a Stripe payment comes in, look up MX records for the customer's email domain. Flag payments where the mx array is empty.

New subscription created Look up MX records → tag customer

Verify subscriber domains on signup

Look up MX records for new Stripe subscriber email domains. Tag customers based on the primary mx exchange hostname.

Connect it in a few steps.

Set up with Zapier
  1. 1
    Set the trigger. Create a Zap with Stripe as the trigger app and "New payment" as the event. Connect your account.
  2. 2
    Add the API action. Add APIVerve as the action, select the MX Lookup API, and map your trigger data to the request.
  3. 3
    Send it back. Add a second Stripe action for "Create charge" and map the returned fields (like domain) into it.
  4. 4
    Test & turn on. Test the Zap with real data to confirm the mapping, then turn it on.
Set up with Make
  1. 1
    Add the trigger. Create a scenario and add a Stripe module set to "New payment". Authenticate your account.
  2. 2
    Call the API. Add an HTTP module pointing at api.apiverve.com/v1/mxlookup with your x-api-key header. Pass the trigger's data as the input.
  3. 3
    Parse & map. Add a JSON module to read the response, then a Stripe module for "Create charge". Map fields like data.domain into place.
  4. 4
    Activate. Run once to confirm the mapping, then switch the scenario on and set its schedule.
Set up with n8n
  1. 1
    Add the trigger node. Start a workflow with a Stripe trigger node for "New payment" and connect your credentials.
  2. 2
    Add an HTTP Request node. Point it at api.apiverve.com/v1/mxlookup using Header Auth (x-api-key). Feed in the trigger data.
  3. 3
    Map with expressions. Add a Stripe node for "Create charge" and reference the response with expressions such as {{ $json.data.domain }}.
  4. 4
    Execute & activate. Execute manually to verify, then activate the workflow for production.

What Stripe receives.

domain"yahoo.com"
mxarray of 3

Stripe + MX Lookup API FAQ

How do I enhance Stripe fraud detection with APIs?
Layer additional validation APIs on top of Stripe Radar. Check email validity, IP reputation, and address accuracy before or after payment.
Can I validate customers before Stripe subscriptions?
Yes. Intercept subscription creation requests, validate customer data with external APIs, and only proceed with Stripe if validation passes.
How do I enrich Stripe customer data?
Trigger on new Stripe customers, call enrichment APIs, and update Stripe customer metadata with additional information.

Connect the MX Lookup API to Stripe. One key, no code, live in minutes.

Scaling up?

Volume pricing, custom SLAs, and dedicated support for high-traffic teams.

Contact sales