API Response (v1)

{
  "identity": {
    "firstNameMatch": true,
    "lastNameMatch": true,
    "score": 900,
    "firstSeenOn": "12-31-2020",
    "lastSeenOn": "01-25-2019"
  },
  "emailAddress": {
    "score": 9999,
    "firstSeenOn": "12-31-2020",
    "lastSeenOn": "01-25-2019"
  },
  "mobileNumber": {
    "score": 199,
    "firstSeenOn": "12-31-2020",
    "lastSeenOn": "01-25-2019"
  },
  "address": {
    "score": 9999,
    "firstSeenOn": "12-31-2020",
    "lastSeenOn": "01-25-2019"
  },
  "deviceId": {
    "score": 9999,
    "firstSeenOn": "12-31-2020",
    "lastSeenOn": "01-25-2019"
  },
  "geoLocation": {
    "score": 9999,
    "firstSeenOn": "12-31-2020",
    "lastSeenOn": "01-25-2019"
  },
}

Response Information

Each request group will have a corresponding response group definition when available

  • identity
  • emailAddress
  • mobileNumber
  • address
  • deviceId
  • geoLocation

Field specification

If any top-level response elements are present, the following fields WILL be present in the response.

“score” <int> Example: 800 “firstSeenOn” <date only> Example: “12-31-2020”. “lastSeenOn” <date only> Example: “12-31-2020”.

The following fields are unique and only available in the identity response section

“firstNameMatch” <bool> [true|false] “lastNameMatch” <bool> [true|false]

When the API is unable to locate any one of the requested element groups, it will be returned as null.

null indicates that either

  • The request did not have the group present
  • The group data elements could not be located

9999 indicates that we have a match for a category, but nothing positive / negative to report.

Identifier Match Responses

Ingo will respond as to whether Ingo has interacted with a customer using each of the following identifiers, along with the date each identifier was first used, and the date that each identifier was last used in the Ingo ecosystem. Identifiers will be reported separately - i.e. Ingo will respond on the email, address etc. separately, even if the Name/SSN do not match.

  • Full SSN OR Last 4 of SSN plus DOB
  • SSN + Last Name
  • Email
  • Mobile Number
  • Address Line 1 + Zip Code
  • Address Line 1 + Line 2 + Zip Code
  • Geolocation
  • Iovation Device Id
MAX------------------------------------------------------------MIN
|----->>---POSITIVE---->>----| NEUTRAL |  >> NEGATIVE BUCKETS >> |
1,000----(continuum)--------499-------300  <299>  <199>  <99>  <9>

Negative Responses (Less than 300)

If Ingo has had a negative experience with a particular identifier, Ingo will respond with a score indicating the nature of that negative experience in one of four discrete “buckets”, as follows:

Suspected Identity Theft (Code 9).

This code indicates that transactions associated with an identifier had indicators closely associated with stolen or compromised identities (whether or not transactions were accepted or turned out to be fraudulent), including but not limited to the following:

  • Attempting to transact from a high-risk country;
  • Attempting to transact using a high-risk foreign phone carrier;
  • Attempting to transact using a device from a high-risk manufacturer (for example a phone only sold in high-risk countries);
  • Attempting to transact using a device that is configured to use a currency or language associated with a high-risk country;
  • Attempting to register more than 3 accounts with a single device;
  • Ingo has been contacted and told that the account was created using their stolen identity; and
  • Attempted account creation which failed automated and manual customer identification procedures.

Likely Fraud (Code 99)

This code indicates that one or more transactions associated with that identifier were highly likely or confirmed to be fraudulent, including but not limited to the following:

  • Submitting a check with an altered amount, or maker payee;
  • Submitting a counterfeit or fake check;
  • Submitting a stolen check or a check made out to someone else which returned as a result; - Duplicate depositing a check with another financial institution or check casher before or after cashing the check with an Ingo partner.

Suspicious Activity (Code 199)

This code indicates that one or more transactions associated with that identifier resulted in a returned check under suspicious circumstances or other suspicious activity, but did not necessarily rise to the level of likely fraud, including but not limited to the following:

  • Submitting checks with very old dates;
  • Returned checks under potentially fraudulent or otherwise suspicious circumstances;
  • Returned single party checks (checks cashed by the same person who wrote the check);
  • Check rejected by the bank the check was written on for “possible fraud” or “return to maker”;
  • Checks returned due to possible collusion between the maker and payee;

High Risk Activity (Code 299)

This code indicates that one or more transactions associated with that identifier indicated high-risk behavior, but that does not rise to the level of likely fraud or suspicious activity, including but not limited to the following:

  • Cashing multiple bad checks that return unpaid;
  • Submission of multiple checks that are declined by Ingo, with no checks that are approved by Ingo;
  • Transactions that result in the customer being put on hold in Ingo’s system for reasons other than confirmed fraud; and
  • Unusually high velocity from a geocode.

NOTES:

Potential Identity Theft

Likely Fraud, Suspicious Activity, and High-Risk activity associated with a certain identity can be the result of the person who actually owns that identity engaging in certain behavior, but can also result from behavior by someone else using such person’s stolen or forged identity. Important Notes:

Addresses

A negative score on an address indicates that Ingo has seen the indicated activity at that address. Scores may be associated with a match of Address First Line + Zip Code – this is an indication of behavior at the building level, but may not indicate behavior in a particular apartment or unit. Apartment or unit information is only indicated if Ingo has matched the Address Line 1 + Line 2 + Zip code. Additionally, a match at an address does NOT necessarily indicate that the person currently at such address has engaged in such activity, as multiple people can live at one address, some addresses are for high occupancy buildings such as apartments, and people move regularly. We urge caution in using these scores in regard to making decisions about any particular individual.

Geocodes

Geocodes may be flagged for high-risk activity due to unusually high transaction velocity. This is an indicator, but not necessarily determinative, of high risk or fraudulent activity.

Transactional Experience Responses (300-1,000)

If and only if Ingo’s experience with an individual (SSN/name/DOB) does NOT fall into one of the foregoing negative categories, Ingo may return a score between 300 and 1,000 for the individual. Ingo does not return transactional scores for other identifiers such as devices, addresses, or email addresses. A score of 300-499 indicates negative or no positive experience with an individual. Scores above 500 indicate increasing levels of positive transactional experience with an individual, such as repeat usage of Ingo’s partner check cashing services with no check returns. The higher the score, the more extensive and positive Ingo’s experience.

Null Response (9999)

A response of 9999 indicates that Ingo has no reportable positive or negative transactional information about an indicator, either because they passed KYC but never conducted a transaction, or because the transactional information about such indicator is not reportable due to compliance or other reasons.

Validation Errors

When the request contains non-identity “invalid” field data Ingo will still send a valid response, however, the response will include a validationErrors property describing the invalid data and the corresponding response group will be null.

{
    "identity": {
        "firstNameMatch": true,
        "lastNameMatch": true,
        "score": 9,
        "firstSeenOn": "06-23-2021",
        "lastSeenOn": "06-24-2021"
    },
    "emailAddress": null,
    "mobileNumber": {
        "score": 299,
        "firstSeenOn": "12-11-2020",
        "lastSeenOn": "06-24-2021"
    },
    "address": {
        "matchType": "Full",
        "score": 9999,
        "firstSeenOn": "05-19-2020",
        "lastSeenOn": "06-24-2021"
    },
    "deviceId": {
        "score": 9999,
        "firstSeenOn": "12-13-2018",
        "lastSeenOn": "06-24-2021"
    },
    "geoLocation": null,
    "validationErrors": [
        {
            "fieldName": "EmailAddress",
            "error": "'Email Address' is not a valid email address."
        }
    ]
}