Possession APIs

MP-1

Mobile Auth

Definition:

Passively authenticates every mobile login and signup without the use of passcodes, pop-ups, pins, or notifications, allowing businesses to seamlessly onboard customers faster and at a lower cost. Outputs include Authentication status, status description, transaction ID, Payfone alias, Mobile Number, Mobile Country Code, and Carrier.

Use Case:

OTP Replacement - no consumer interaction required, reducing abandonment and error. No false positives (verification comes directly from Mobile Network Operator)

Coverage:
MP-3

SMS Delivery

Definition:

A configurable second-factor authentication service that allows a client to issue and verify one-time passcodes via SMS. Outputs include authentication status code, status description, and transaction ID.

Use Case:

Sending an SMS OTP or Instant Link to customers

Coverage:
+200 Countries & Territories
MP-4

Voice Delivery

Definition:

A configurable second-factor authentication service that allows a client to issue or confirm a one-time passcode via a voice call. Outputs include authentication status code, status description, and transaction ID.

Use Case:

Sending a voice OTP to customers

Coverage:
+200 Countries & Territories
MP-6

Voice Biometrics

Definition:

An authentication service that verifies users on phone calls using their voice.

Use Case:

Use Case: Authenticate a user via voice print

Coverage:

Reputation APIs

MP-7

Trust Score®

Definition:

A real-time score of behavioral risk assigned to a phone identity token and phone number of the client’s customer that is a consumer. Outputs include requestId, status, trustscore,carrier, linetype, and countrycode. Other outputs that may be returned include reason codes, indicators, transactionId, troubleshootingId, description, response, transactionId, payfoneAlias, phoneNumber, lineType, carrier, country code, trustScore, statusIndex, isBaselined, phoneNumberVelocity, portVelocity, payfoneTenure, phoneNumberTenure, and portedDate.

Use Case:

Customer onboard or securing a transaction that leverages authentication using a phone number.

Coverage:
MP-8

Trust Score®+

Definition:

A real-time score of behavioral risk assigned to a phone identity token and phone number of the client’s customer that is a consumer; leverages mobile carrier data for improved efficacy and accuracy. Outputs include requestId, status, trustScore, carrier, lineType, and countryCode. Other outputs that may be returned include reason codes, indicators, transactionId, troubleshootingId, description, response, transactionId, payfoneAlias, phoneNumber, lineType, carrier, country code, trustScore, statusIndex, isBaselined, phoneNumberVelocity, portVelocity, payfoneTenure, phoneNumberTenure, portedDate, riskLevel, simTimestamp, carrierStatus, simVelocity, deviceVelocity, simTenure, and deviceTenure.

Use Case:

Customer onboard or securing a transaction that leverages authentication using a phone number.

Coverage:
MP-9

Trust Score®+ with Call Forwarding

Definition:

A real-time score of behavioral risk assigned to a phone identity token and phone number of the client’s customer that is a consumer; leverages mobile carrier data for improved efficacy and accuracy. Outputs include requestId, status, description, response, transactionId, payfoneAlias, phoneNumber, lineType, carrier, country code, trustScore, statusIndex, isBaselined, phoneNumberVelocity, portVelocity, payfoneTenure,phoneNumberTenure, and portedDate. Other outputs that may be included are reason code(s), carrierStatus, simVelocity, deviceVelocity, simTenure, deviceTenure. This product is only available for mobile numbers on Verizon, T-Mobile, and ATT (when applicable).

Use Case:

Prevent Voice OTPs to be delivered to a phone number that currently is forwarding calls to another phone number.

Coverage:

Ownership APIs

MP-10

Identity Verify

Definition:

Identity Verify matches name and address information against verified data. Prove applies its matching algorithm to calculate a matching score (or boolean) for each of the fields in order to confirm and establish a verified entity for each consumer. Outputs include requestId, verified, firstName, lastName, nameScore, addressScore, dob, lineType, carrier, countryCode. Other outputs that may be returned include, transactionId, troubleshootingId, description, streetNumber, street, city, region, postalCode, distance, last4, driversLicenseState, driversLiceseNumber, emailAddress, reason codes, indicators, and accountType.

Use Case:

Account Opening/Customer onboarding, Phone Ownership for OTP Security

    Coverage:
    MP-11

    Contact Compliance with Safe Harbor

    Definition:

    Verify that phone numbers have not been disconnected since the most recent Right Party Contacted Date, with Safe Harbor available via the RND. Provides line type and carrier for the current or newer phone number, where applicable.

    Use Case:

    Comply with the TCPA or FDCPA and avoid litigation when making outbound calls to various line types.

    Coverage:
    MP-12/13

    Contact Enrichment

    Definition:

    Contact Enrichment provides batch phone number enrichment and verification of a customer's contact list. Enriched phone numbers are ordered by how likely the number is to be answered (contactability ranking).

    Coverage:
    MP-19

    Identity Verify with KYC

    Definition:

    Allows the client to verify a consumer's personally identifiable information is valid and that consumer is the rightful owner of a given phone number based on the customer’s name, address and additional attributes such as national identity (e.g., SSN in the US) or date of birth.  These validations may assist with Know Your Customer (“KYC”) or other related compliance programs and may include sanction/watchlists and Politically Exposed Persons (PEP) checks as well as ongoing monitoring, if elected by a Client.

    Use Cases:

    Account Opening/Customer Onboarding

    Coverage:

    Software Licenses

    MP-17

    AT&T 2.0 Managed Services

    Definition:

    Using Mobile Auth or Real-time Carrier Attributes with AT&T customers requires additional setup and systems to support due to AT&T requirements for a BOSE, which is an acronym for Bank Owned Server Environment, although it is not restricted to banks.

    Use Cases:

    Using Mobile Auth or Real-time Carrier Attributes with AT&T customers

    Coverage: