Skip to main content
Fraudulent Behavior

How to recognize potentially fraudulent behavior

Updated over a week ago

While most users/subscribers will have honest intentions when they start service with you, there may be instances where fraudulent behavior is taking place. This article is here to help you recognize those potentially fraudulent subscribers.

What type of fraud is there?

While this isn't an all-encompassing list, these are some common types of fraud you may encounter:

  • Credit card testing

  • Fraudulent purchase

  • User impersonation

How to recognize fraud:

Please use the following list as a reference on how to recognize potential fraud:

  • Use of likely false information. Such as:

    • Fake phone numbers

    • Fake email addresses like [email protected]

    • Fake addresses

      • While we will verify an address for validity, it may be possible for someone to use an address that obviously isn't their home (such as a grocery store)

  • Inconsistencies in customer details across multiple purchases. For example:

    • Using the same e-mail address but a different names for various payments.

  • Many payments (including those that have been declined) made with:

    • The same card but different user addresses

    • Many cards that use the same shipping address

    • The same customer name/email address but different card

  • Other suspicions behavior that could indicate “card testing” or stolen cards

    • Cards with contradicting information

      • Same card attempted with different expiration dates

      • Same card attempted with different names

    • Different cards with different (unrelated) names being attempted

  • User has directly contacted your customer support acting in a suspicious manor, possibly phishing for information, or other red flag behavior.

    • Not an absolute indication, but could point to their line being used fraudulently

What to do?

If you feel like you're dealing with a fraudulent user, please contact Gigs support for further assistance at [email protected].

Did this answer your question?