Sandbox Testing

Learn more about simulating the Prove Pre-Fill flow using our Sandbox environment.

Overview

When you interact with the Sandbox environment, you'll be able use any of the test users below to simulate different behaviors. No text messages will be sent in this environment and real user information will not validate properly either - you must use the test users.

A few things to note:

  • When prompted for your OTP during mobile flow testing, you must use 1234 to simulate a successful OTP. Any other combination of numbers will simulate a failure.
  • Use Milo or Martina when testing with Postman or curl because it doesn't require use of the client SDK. Otherwise, the success field of the Validate call will always return false.

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

  • If you call a step not specified in the next field (or out of order), you will receive:
    • Status Code: HTTP 403
    • Response: {"code":1003,"message":"step not allowed"}
  • If you don't pass in a required field, you will receive:
    • Status Code: HTTP 400
    • Response: {"code":1001,"message":"field 'flowType' is missing"

Steps

These are the steps you'll follow for each of the tests.

  • For Start:
    • Send into request:
      • flowType: use either mobile or desktop
      • phoneNumber: (use number from table above)
      • finalTargetUrl: https://www.prove.com
      • either dob or last4SSN (otherwise, pass it in to Challenge request)
    • Response will return:
      • authToken
      • correlationId
      • next = v3-validate
  • For Validate:
    • Send into request:
      • correlationId (from Start response)
    • Response will return:
      • success = true
      • challengeMissing = false
      • next = v3-challenge or v3-complete
  • For Challenge (only if the previous Validate call returned: next = v3-challenge):
    • Send into request:
      • correlationId (from Start response)
      • either dob or last4SSN (if you didn't pass it into Start request)
    • Response will return:
      • success = true
      • individual information (from table above)
      • next = v3-complete
  • For Complete:
    • Send into request:
      • correlationId (from Start response)
      • individual information (from table above)
    • Response will return:
      • success = true
      • changeDetected (true if the data doesn't exactly match what was returned from Challenge response)
      • next = done

Prove Pre-Fill with KYC Test Users

Below is the comprehensive list of Prove Pre-Fill with KYC/CIP Test Users. Follow the steps above in the UAT environment to test out your implementation to ensure it's working properly.

Phone NumberFirst NameLast NameAddressCityStateZipDate of BirthSSNEmail
2001004001SebastianLimmer2302 Ronald Regan ParkDaytonOH4547012/23/1977347465324[email protected]
2001004002LeenaTomashov4984 Sage HillSaint LouisMO631045/13/1965115925498[email protected]
2001004004JohnnieLammiman0571 Gale CourtWhite PlainsNY1063312/08/1977111258802[email protected]
2001001687AgrethaChene4861 Jay JunctionBostonMS0220812/29/1994369956933[email protected]
2001001688NevinChattey9398 Scott PlazaAustinTX787443/20/1980542742985[email protected]

📘

Test users are only available in the Sandbox environment.

Prove Pre-Fill with KYC Outcomes and Test Scenarios

The below table provides Pre-Fill with KYC outcome possibilities including which sandbox users to test with, testing notes and interpretation of each success and failed state in Production. The Prove Pre-Fill with KYC Test Users table above contains the comprehensive list of test users including mock data. If you are trying to troubleshoot Success=False in the API response, please see the next section.

API Response Troubleshooting Tips

Please see below table for assistance troubleshooting when Success=False in an API response. To understand what this indicates in Production, please see the Pre-Fill with KYC Outcomes and Test Scenarios table above.

Server Side CallPossible Behaviors Resulting in Success=FalseTroubleshooting Tips
/startNot ApplicablePlease see Error and Status Codes page for common 400 response errors
/validateClient Side SDK Authenticate() function wasn't called or was configured incorrectly*

*Required for all sandbox users
See our Client Side SDK implementation guide
/validate Wrong one-time passcode (OTP) enteredSee our Client Side SDK implementation guide
/challengeThe phone number entered isn't associated with the SSN/partial or DOB entered (eg you entered Johnnie Lammiman's Phone number with different last4 than test user data)See Pre-Fill Test User Table for sandbox test user data
/completeFirst Name or Last Name or SSN isn't associated with the phone number entered (eg you entered Johnnie Lammiman's Phone number with different last4)Please see Test Scenario Table for which test users fail each scenario

❗️

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

If you're still having issues, send us your correlation ID from a failing request. We may be able to provide additional insight after reviewing our logs using either the Support button in the Portal or contacting your account representative.


📘

Self-Serve

For the option, please contact your sales representative.