Prove Pre-Fill Sandbox Testing

​

Overview

When you interact with the Sandbox environment, you’ll be able use the test users to simulate different behaviors. Simulate the possession checks using the client-side SDK. The testing environment doesn’t send text messages or validate real customer information.

Unless specified below, you can introduce failures in the tests that would otherwise be successful:

• If you call a step out of order, you will receive:

  • Status Code: HTTP 403

  • Response: {"code":1003,"message":"step not allowed"}

• If a required field is missing, you will receive:

  • Status Code: HTTP 400

  • Response: {"code":1001,"message":"field 'flowType' is missing"}

​

Steps

Follow these steps for each of the tests:

• For Start:

  • Send into request:

    • flowType: use either mobile or desktop

    • phoneNumber

    • finalTargetUrl: https://www.prove.com

    • dob or last4SSN

  • Response returns:

    • authToken

    • correlationId

    • next = v3-validate

• For Validate:

  • Send into request:

    • correlationId

  • Response returns:

    • success = true

    • challengeMissing = false

    • next = v3-challenge or v3-complete

• For Challenge, if the earlier Validate call returned: next = v3-challenge:

  • Send into request:

    • correlationId

    • dob or last4SSN

  • Response returns:

    • success = true

    • Individual information

    • next = v3-complete

• For Complete:

  • Send into request:

    • correlationId

    • Individual information

  • Response returns:

    • success = true

    • changeDetected

    • next = done

​

Short-Term Test User

Use this test user when performing initial testing with cURL or Postman. This test user skips the client-side SDK authentication to walk you through the sequence of API calls.

After initial short-term testing, implement the client-side SDK and use the remaining test users to test your implementation. Refer to the Quick Start Guide to gather required components.

​

Prove Pre-Fill Test Users

Use the following list of Prove Pre-Fill Test Users. Follow the instructions in the Staging environment to test out your implementation to ensure it’s working. Refer to the Outcomes Table to review scenarios to test and interpretation of success and failed states.

When prompted for your one-time password (OTP) during mobile flow testing, you must use 1234 to simulate a successful OTP. Any other combination of numbers simulates a failure. Use Marcia Longo to test your OTP setup.

​

Prove Pre-Fill Outcomes and Test Scenarios

The following table provides Pre-Fill outcome possibilities including which sandbox users to test with and interpretations of each success and failed state in Production. The Prove Pre-Fill Test Users table has the comprehensive list of test users including mock data. When troubleshooting success=false in the API response, refer to the following section.

​

API Response Troubleshooting Tips

Use the following table for help troubleshooting when success=false in an API response. For Production, refer to the Pre-Fill Outcomes and Test Scenarios table.

If you receive 400 or 500 response errors when running these test scenarios, refer to the Error and Status Codes page.

If you still have issues, send your correlationId from a failing request. Use either the Support button in the Portal or contact your account representative.