Skip to main content

​
Prerequisites

Begin by implementing Step 2: Authentication to authenticate the user’s device. This step is crucial as it establishes a trusted connection between the user and their phone number, which is the foundation for the Account Opening solution. Flowchart showing the authentication checklist for Prove Account Opening
1

Gather Required Inputs

Collect the required customer information from your CRM or database:
  • Phone number
  • First name
  • Last name
2

Call the Verify Endpoint

Make a request to the /v3/verify endpoint including the Authorization header. Generate a bearer token as outlined on the Authentication page.
cURL
curl -X POST "https://platform.uat.proveapis.com/v3/verify" \
-H "Authorization: Bearer <YOUR_ACCESS_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
    "verificationType": "accountOpening",
    "firstName": "Bettina",
    "lastName": "Halbert",
    "phoneNumber": "2001004049",
    "clientRequestId": "test-001"
}'
Replace <YOUR_ACCESS_TOKEN> with your acquired access token.
Include the following required parameters:
  • phoneNumber: the phone number of the customer.
  • firstName: the first name of the customer.
  • lastName: the last name of the customer.
  • verificationType: the type of verification. Set this value to accountOpening.
  • clientRequestId: client-generated unique ID for a specific session. Use this to identify specific requests.
Always give unique clientRequestId values for each request to enable proper tracking and troubleshooting.
The optional parameters you can also send in the request body include:
  • emailAddress: the email address of the customer.
  • ipAddress: the IP address of the customer’s device.
  • userAgent: the user agent of the customer.
  • clientCustomerId: the client-generated unique ID for a specific customer. Use this to link calls related to the same customer, across different requests or sessions.
  • clientHumanId: a client-generated unique ID for a consumer across business lines.
  • proveId: the Prove ID associated with the customer, if known.
3

Process the Response

The response includes comprehensive identity information and verification results:
Example Response
{
    "success": "true",
    "correlationId": "d427c049-0ae8-491d-8300-75d23610d0ff",
    "clientRequestId": "test-001",
    "phoneNumber": "2001004049",
    "proveId": "41570934-6d6b-476d-9425-3eaf305cf2e5",
    "provePhoneAlias": "4B2C...",
    "identity": {
        "firstName": "Bettina",
        "lastName": "Halbert",
        "assuranceLevel": "AL2",
        "reasons": [
          "AL2a"
        ]
    },
    "evaluation": {
        "authentication": {
            "result": "pass"
        },
        "risk": {
            "result": "pass"
        }
    }
}
  • success: the result of the verification.
  • correlationId: the unique ID that Prove generates for the flow.
  • clientRequestId: the client-generated unique ID for a specific session, provided in the request.
  • phoneNumber: the phone number provided in the request.
  • proveId: the unique Prove-assigned ID tied to the consumer.
  • provePhoneAlias: the unique Prove-assigned ID tied to the phone number.
  • identity: the verified identity information. This object has:
  • evaluation: object containing the results of the authentication and risk evaluations. Refer to the Global Fraud Policy for more details.
Optional parameters that may also return in the response if sent in the request:
  • clientCustomerId: the client-generated unique ID for a specific customer.
  • clientHumanId: a client-generated unique ID for a consumer across business lines.
Best Practices
  • Check the success field to handle different verification outcomes appropriately.
  • Save the proveId and correlationId for future reference and to enable cross-domain linking if needed.
  • Use assurance levels to implement adaptive security policies based on transaction risk.

​
Sandbox testing

​
Test users

You must use Account Opening project credentials when working with Account Opening sandbox test users. Attempting to use these test users with different project credentials results in an unauthorized access error.
The following test users are available for testing Account Opening using the /v3/verify endpoint in the Sandbox environment. Use these test users to simulate different verification scenarios and outcomes.
Phone NumberFirst NameLast NameVerification TypeExpected Outcome
2001004049BettinaHalbertaccountOpeningSuccess
2001004050LaurelVan Der BeekaccountOpeningFailed
Use these test phone numbers exactly as shown. The sandbox environment doesn’t validate real customer information.

​
Testing steps

Use test user Bettina Halbert to verify a successful verification:
cURL
curl -X POST "https://platform.uat.proveapis.com/v3/verify" \
  -H "Authorization: Bearer <YOUR_ACCESS_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "verificationType": "accountOpening",
    "firstName": "Bettina",
    "lastName": "Halbert",
    "phoneNumber": "2001004049",
    "clientRequestId": "test-001"
  }'
Expected response:
{
    "success": "true",
    "correlationId": "ab1e9b42-da4f-4d13-8690-5d32eae76c6f",
    "clientRequestId": "test-001",
    "phoneNumber": "2001004049",
    "proveId": "41570934-6d6b-476d-9425-3eaf305cf2e5",
    "provePhoneAlias": "4B2C...",
    "identity": {
        "firstName": "Bettina",
        "lastName": "Halbert", 
        "assuranceLevel": "AL2", 
        "reasons": [ 
          "AL2a"
        ]
    },
    "evaluation": {
        "authentication": {
            "result": "pass"
        },
        "risk": {
            "result": "pass"
        }
    }
}