Overview

Prove helps you pre-populate application forms with verified identity information and assess the trustworthiness of a phone number, reducing friction and fraud. Persona’s integration with Prove lets you enrich Inquiries and Workflows with trust signals and pre-filled PII, so you can route applicants dynamically, improve conversion, and reduce manual data entry.

With this integration, teams can verify a phone via OTP, evaluate risk using Prove Trust Score, and only then pre-fill identity details for qualified applicants—maintaining compliance with Prove’s usage guidelines while delivering a smoother user experience.

Benefits

Higher Conversion with Pre-Fill: Reduce keystrokes and drop-off by auto-completing identity fields after verification and risk checks.

Friction-Right Experiences: Use Trust Score thresholds to determine when to pre-fill, request more evidence, or fall back to manual entry.

Reduced Fraud and Risk: Leverage phone tenure, velocity, and other trust signals to better detect risky phone numbers and scenarios.

Configurable and Compliant: Follow Prove’s required sequence (OTP → Trust Score → Pre-Fill) with configurable thresholds and fallbacks.

Integration Features

Persona’s Prove integration supports strong risk screening and intelligent pre-fill to streamline onboarding and verification. Key capabilities include:

• Phone Intelligence & Risk Signals: Retrieve a Trust Score and supporting attributes to evaluate the trustworthiness of a phone number and its associated identity.
• Dynamic Routing: Use thresholds and response attributes to branch workflows, trigger manual fallback, or layer additional checks.
• Field Mapping into Inquiries: Map returned identity attributes into your Inquiry screens to display pre-filled, editable fields.

Setting up the Prove integration

Prerequisites

To set up the Prove integration, ensure you have:

• Admin access to your Prove account
• Necessary API permissions to access Prove credentials

Setting up the Prove Credentials

1. In the Persona Dashboard, navigate to Integrations > Marketplace and click on Prove.
2. Click Add Credential at the top of the page.
3. Enter a nickname and add your Prove credentials.
4. Use the Test button to validate the credential with sample inputs and confirm a successful response.

Using the Prove integration in a workflow

1. Create a new workflow, or open an existing one you’d like to update.
2. Add a new Action step > Integrations.
3. Select the Prove integration and choose your Prove credentials.
4. Configure the input fields to pass the correct information (for example, phone number captured earlier in the flow and consent status).
5. Save and publish the workflow.

Prove Operations Overview

In addition to syncing field values, Persona can retrieve trust signals and pre-fill identity data using Prove’s API. These actions support seamless two-way workflows, letting teams manage investigations without switching platforms.

See below for a comprehensive list of available Workflow Action steps and possible configurations for the Prove integration:

Trust Score

Returns a Trust Score for a provided phone number (or a persistent alias), along with supporting attributes like line type, carrier, country, tenure ranges, and velocity indicators. Use this result to dynamically route applicants after you’ve proven device ownership via Phone Number Verification.

Configuration Steps:

• Provide values for required fields:
  • Phone number
  • Unique request ID
  • End-user consent status
• Optionally include:
  • Payfone alias (if available)
  • Whether to include additional details
  • Customer subscriber identifier (for your internal reference)

Pre-Fill

Pre-fills identity information for an individual after a successful Trust Score check. Provide the previously verified phone number along with one piece of challenge PII (DOB or SSN) to retrieve name, addresses, and email(s) that can be mapped into your Inquiry for a faster, lower-friction experience.

Configuration Steps:

• Provide values for required fields:
  • Phone number (used in the prior Trust Score check)
  • Unique request ID
  • End-user consent status
• Provide one piece of challenge PII:
  • Date of birth, or
  • Last 4 of SSN, or
  • Full SSN
• Optionally include:
  • First/last name (if you want to narrow results)
  • Desired counts for addresses and emails to return
  • Customer subscriber identifier (for your internal reference)

FAQs

What sequence should I follow to use Pre-Fill successfully?

Follow this order: collect phone + challenge PII on the first screen → verify phone with OTP → call Trust Score → if it meets your threshold (e.g., ≥ 630), call Pre-Fill. Include a manual entry fallback if the Trust Score is below threshold or Pre-Fill returns no data.

What consent is required?

Each request should include the end user’s consent status. Ensure consent is collected and accurately reflected prior to calling Trust Score or Pre-Fill.

What fields can be returned by Pre-Fill?

When available, Pre-Fill can return name, date of birth, addresses (with city, region, postal code, and country), and email addresses. You can limit how many addresses or emails to return.

How should I format the phone number?

Use standard international format (E.164), including the leading plus sign for non-US numbers.

What happens if Pre-Fill returns no data?

Present a manual entry path so applicants can provide their information directly. You can also choose to request additional verification (for example, Government ID and Selfie) based on your risk appetite.