​
Platform integration

The Global Fraud Policy (GFP) serves as Prove’s comprehensive set of business intelligence for combating fraud across all its products. This policy translates collaborative intelligence—drawn from both Prove’s data and our clients’ firsthand fraud experiences—into a unified output including identification and authenticaiton results with specific failure reason codes designed to maximize pass rates for legitimate consumers while simultaneously mitigating risk. The automated engine that applies the GFP within Prove’s Products and Solutions includes the latest fraud insights and is updated regularly to account for ever-evolving fraud trends. For every Prove Platform transaction, the Platform will generate a result output status based on the GFP. The automated engine assesses a wide array of identity attributes—such as phone tenure and address matching—together with our proprietary risk intelligence. This analysis is structured through our comprehensive verification result framework, which generates a holistic assessment across four key categories:
  1. Identification - Validates personal details such as name, address, date of birth, and national identifier to confirm an individual’s identity, ensuring the accuracy of provided information.
  2. Authentication - Verifies a person is truly the identity they are claiming to be in the identification step.
  3. Compliance - The adherence to the appropriate regulatory rules to satisfy minimum requirements for that industry and use case.
  4. Risk - Other risks related to the transaction outside of identification and authentication.
This detailed, multi-faceted output is then seamlessly integrated into the final transaction output for your immediate use under the evaluation object.

​
Output examples

An example of a successful result output of the v3/complete API can be found below: 
{
    "success": true,
    "next": {
        "done": "done"
    },
    "evaluation": {
        "authentication": {
            "result": "pass"
        },
        "identification": {
            "result": "pass"
        }
    }
}
An example of a failed result output of the v3/complete API can be found below: 
{
    "success": false,
    "next": {
        "done": "done"
    },
    "evaluation": {
		"authentication": {
        	"result": "fail",
        	"failureReasons": {
           	 	"9161": "Very short tenure association between phone number and identity.",
            	"9171": "Potential injection attack due to 2 identities both with short tenure association to the phone number.",
            	"9180": "No phone ownership confirmed using 4 elements."
        	}
    	},
    	"identification": {
        	"result": "fail",
        	"failureReasons": {
            	"9001": "Identification is not confirmed using 4 elements."
        	}
    	}
	}
}
The Failure Reason code outputs from the Global Fraud Policy are as follows:
Failure ReasonCategoryResult Description
9001IdentificationIdentification is not confirmed using 4 elements.
9003IdentificationIdentity is not found
9011IdentificationIdentification is not confirmed using less than 4 elements.
9012IdentificationSSN does not match.
9013IdentificationBirth Date does not match.
9014IdentificationName does not match.
9015IdentificationAddress does not match.
9081IdentificationSSN is issued before the birth date.
9082IdentificationAddress is a correctional facility.
9083IdentificationDeceased indicator is present for individual.
9100AuthenticationPhone possession incomplete
9131AuthenticationIndicates the phone number is at a higher risk for fraud due to being listed as a non-mobile line on the Override Services Registry (OSR).
9132AuthenticationThis phone number is listed on a public website with the contents of its text messages posted publicly in order to allow a user to bypass phone possession check controls.
9133AuthenticationThe phone is not trusted based on the SIM Key Trust Score.
9134AuthenticationThe phone is not trusted because it is a non-fixed VoIP number.
9135AuthenticationPotential ATO due to recent SIM Swap under 24 hours.
9136AuthenticationPotential ATO due to recent Port under 24 hours.
9137AuthenticationPotential ATO due to call forwarding enabled for phone number.
9161AuthenticationVery short tenure association between phone number and identity.
9162AuthenticationShort tenure association between phone number and identity.
9163AuthenticationPotential recycled phone fraud due to a high number of identities associated to phone number with a newer owner present.
9164AuthenticationPotential recycled phone fraud due to identity having no recent association to phone number and a phone disconnect event is observed after the phone association.
9165AuthenticationPotential recycled phone fraud due to a newer owner observed and a phone disconnect event is observed after the phone association.
9166AuthenticationAddress is a correctional facility.
9167AuthenticationDeceased indicator is present for individual.
9168AuthenticationPerson verification was performed indicating phone ownership is not verified
9171AuthenticationPotential injection attack due to 2 identities both with short tenure association to the phone number.
9172AuthenticationPotential injection attack due to 3 identities all with short tenure association to the phone number.
9173AuthenticationPotential injection attack due to 4 identities all with short tenure association to the phone number.
9174AuthenticationPotential injection attack due to 5 or more identities all with short tenure association to the phone number.
9180AuthenticationNo phone ownership confirmed using 4 elements.
9181AuthenticationNo phone ownership confirmed using less than 4 elements