Do you see jigged addressses in your database?
They are an early indicator of fraud and our API can detect them for you.

Illustration of fraudster jigging their address and Antijig detecting the jigged address.
Fraudster with packages.

Fraud has many faces

Online merchants lose money due to fraudulent returns, chargebacks, promo abuse, and new scams surface all the time. Bots and resellers target limited products and flash sales, frustrating genuine customers and damaging your brand.

Fraudster hiding their location.

Address jigging is the common factor

Whatever the fraud pattern, repeat offenders can easily be blocked. Therefore fraudsters manipulate ('jig') their shipping address to create new accounts, while still receiving products to their home address.

Antijig Logo.

Use jigging to your advantage

Jigging is a telltale sign of fraudulent activity, so use it to detect fraud early. The Antijig API helps you catch jigged addresses with high accuracy, using artificial intelligence trained on large address datasets. Integrate our API into your existing fraud prevention solution or use it in retrospective analysis.

  • Always up to date
  • Reliable and fast
  • Simple API

Protect your business now

Take a look at our public API or contact us
for a custom tailored solution for your use case.

Frequently Asked Questions

  1. What are some common jigging patterns?
    Common jigging patterns include adding random characters (e.g. 4-letter jig), duplicating parts of the address (main main street instead of main street), or adding fake floor/apartment information. There are plenty of jigging tutorials online, see here, here, or here.
  2. Why not use geotagging?
    These are two different solutions to two distinct problems and can be used simultaneously. If someone is jigging their address, it is a clear sign they are up to a fraud of some kind. Detecting these jigs can inform other systems to treat that user with caution. Geotagging converts addresses to latitude and longitude coordinates. While modern geotagging services resist typos, they often cannot encode intentionally manipulated addresses. Therefore Antijig API provides a best guess cleaned address for downstream use in geotagging systems.
  3. Why not use address autocorrect in the frontend?
    While autocorrect can help improve data quality, your customers must always have the option to override the database result. Any database has missing addresses, especially in areas with weaker public infrastructure. If you log a customer's override decision, Antijig API can help you distinguish genuine overrides due to missing database coverage from fraudulent jigging of an address.
  4. Where can I get an API Key?
    You can sign up to our free plan on RapidAPI or contact us directly at support@antijig.com and tell us about your case to get more free credits.
  5. Can you group jigged versions of the same address together?
    In these cases our best guess cleaned address is a great starting point. We get good results in combination with LSH, Geohash, and clustering techniques. Get in touch if you want to learn more.
  6. The API does not fit my use case. Can I get a custom solution?
    Addresses are incredibly complex and our training data might differ slightly from your use case. Contact us for a custom-tailored, on-premise solution.