Sandbox

The partner-testing domain allows for testing certain edge cases, which can be activated using various techniques outlined in this document.

Sandbox testing features

• Payment
  • Payment errors
• Testing Personas
  • Deny-listed Driver
  • Prefill Needs Driver's License
  • Prefill Many Drivers & Vehicles Mandy
  • Prefill No-hit Nancy
  • Underwriting Declined
  • Underwriting Pending

Submit payment

API reference

The test environment uses Braintree's Sandbox, which only accepts specific test credit card numbers. Use values from their documentation to trigger different responses:

• Card numbers
  • Valid cards: simulate various card provider types
  • Cards to simulate unsuccessful verification response
• Transaction/payment amounts

Payment errors

Payment processing is affected by the "charged" transaction amount in testing, due to having Braintree's Sandbox enabled. When binding out a quote, your payment will depend on your selected coverages, covered drivers and vehicles, as well as invoice period. As a result, quoted profiles can be modified in order to test specific payment processor responses from Braintree. For example, you will see a Processor declined error if checking out with a monthly payment ranging from $2000.00-2999.99, or a 3000 failed processor response if paying the full-term price for a quote between $3000.00-3999.99.

Please refer to Braintree's Sandbox documentation describing transaction amounts for more information.

Testing Personas

When working with a quote, there are hard-coded "Personas" that you can use for testing. The Personas are designed to go through certain paths in the code when generating a quote. The Persona used during the flow is based off of the license number you provide for the Primary Named Insured driver. The single exception follows below

A prefill driver, Sang Starnes, will always be presented. The default coverage for this prefill driver is Covered. To decline coverage please include the following excerpt:

        {
            "id": "{{id}}",
            "status": "Not in household"
        }

Accepted statuses are: Covered, Declined, Not in Household.

Deny-listed Driver

If any driver on a quote has one of these driver's licenses, then Root may not rate the quote. This is to simulate a driver who Root has decided is not desirable for any reason.

Prefill Needs Driver's License

A prefill report can be ordered without a driver's license, but our vendors sometimes need it in order to find records. You can trigger this response by having the pni driver with first name NODRIVERSLICENSE. This will always trigger a 400 bad_request reponse in our testing environment

Prefill Many Drivers & Vehicles Mindy

When the PNI has this license number pattern we will find many drivers and vehicles in our prefill report in our testing environment.

Prefill No-hit Nancy

When the PNI has this license number pattern we will not find any prefill data in our testing environment.

Forcing Underwriting Declined

When a PNI has a driver's license ending in 555 they will receive a quote status of underwriting_declined after finalization.

Forcing Underwriting Pending

When a PNI has a driver's license ending in 444 they will receive a quote status of underwriting_pending after finalization. One hour later that quote will become underwriting_approved.

Higher Down Payment

When any covered driver has a driver's license ending in 777, the finalized quote will require a higher payment for the first month of coverage and lower payments for subsequent months, if paid monthly.

Lower Down Payment

When any covered driver has a driver's license ending in 776, the finalized quote will require a lower payment for the first month of coverage and higher payments for subsequent months, if paid monthly.