eContract Data
Overview
Auto lenders may send data to Informed in the form of an electronic Retail Installment Sales Contract (RISC), or eContract, as well as images of paper documents for ancillary product contracts and consumer stipulations.
Electronic RISC data can be sent in the structured_data element that is part of the JSON payload for creating documents. In order to send eContract data using the structured data node it is required to specify the document_type as retail_installment_sales_contract_electronic.
Please note that the document type for the eContract structured_data has recently changed from retail_installment_sales_contract to retail_installment_sales_contract_electronic. For the time being, both will be accepted values, but the correct document type is retail_installment_sales_contract_electronic.
It is important to understand that not every single field shown in the full example is required in order to use the basic eContract functionality in the Informed platform. The primary goals of using the eContract data is that Informed is able to check for ancillary product contracts and their premiums, as well as the "Amount Financed" which will be used to compare to the Amount Due on the Buyers Order. Thus, at a minimum, it is possible to send just those data elements in order to leverage the basic eContract functionality available.
If you will be including the insurance_charges, taxes, or fees elements, it is required that there is both a specified type and a premium or amount element.
Fees
The list of common type values for fees are shown below:
- inspection
- state_emissions
- emissions_testing_charge
- delivery_charge
- documentary_stamp
- filing
- documentation
- document_processing_charge
- title
- license
- public_official
- conveyance
- admin
Taxes
The primary type value for this category is:
- sales_tax
Insurance/Other Charges
Appropriately mapping the various ancillary products and add-ons in the insurance_charges section is very important, as this is the information that is used to trigger the automatic verifications (sometimes referred to as "auto-stipping") when the contract_type is Electronic.
If the contract_type is Paper, then this information is read off the actual image of the Retail Installment Sales Contract itemization page.
The type values shown below are what you should be mapping your incoming eContract add-ons against.
- vsc or warranty or vehicle_service_contract
- warranty_service_contract
- gap
- theft_protection
- appearance_protection
- tire_wheel_plan or tire_wheel
- maintenance_plan
- windshield_protection
- paintless_dent_repair
- key_replacement
- bundled_product
Minimum eContract Data
The following sample JSON snippet shows the recommended minimum amount of information required to be present in the structured_data node in order to process an eContract.
Please note that the document_reference_id key-value pair is a required element when submitting structured eContract data. You should use a unique value for every eContract that you send (e.g., a UUID or hash or some other convention that fits your workflow.)
{
"image_files": [...],
"structured_data": [
{
"document_type": "retail_installment_sales_contract_electronic",
"document_reference_id": "partner reference id",
"source": "DealerPortal",
"url": null,
"extracted_data": {
"contract_date": "2021-05-09",
"dealer_name": "Toyota of Hollywood",
"dealer_address": "6000 Hollywood Blvd, Los Angeles, CA 90028",
"number_of_monthly_payments": 72,
"amount_financed": 22136.05,
"insurance_charges": [
{
"term": {
"month": null,
"mileage": null
},
"type": "vsc",
"provider": "AUL Corp",
"premium": 3500
},
{
"term": null,
"type": "gap",
"provider": "Allstate",
"premium": 500
}
],
"other_charges": []
}
}
]
}
Ideal eContract Data
When sending the minimal amount of information, there are some verifications that cannot be performed due to a lack of data to which to compare other document values. In order to maximize the value of sending eContract data while still not sending every field availabe in the full example, it is recommended that you send at least the data represented in the following sample JSON snippet.
Please note that the document_reference_id key-value pair is a required element when submitting structured eContract data. You should use a unique value for every eContract that you send (e.g., a UUID or hash or some other convention that fits your workflow.)
{
"image_files": [...],
"structured_data": [
{
"document_type": "retail_installment_sales_contract_electronic",
"document_reference_id": "partner reference id",
"source": "DealerPortal",
"url": null,
"extracted_data": {
"contract_date": "2021-05-09",
"dealer_name": "Toyota of Hollywood",
"dealer_address": "6000 Hollywood Blvd, Los Angeles, CA 90028",
"vin": "1HGCR2F52GA195235",
"year": 2016,
"make": "Honda",
"model": "Accord",
"number_of_monthly_payments": 72,
"vehicle_cash_price": 18998,
"amount_financed": 22136.05,
"odometer": 62940,
"vehicle_condition": null,
"insurance_charges": [
{
"term": {
"month": null,
"mileage": null
},
"type": "vsc",
"provider": "AUL Corp",
"premium": 3500
},
{
"term": null,
"type": "gap",
"provider": "Allstate",
"premium": 500
}
],
"other_charges": [],
"lender_name": "Acme Financial, LLC"
}
}
]
}
Full eContract Data
The following JSON snippet showcases the full range of additional data elements that are available and recommended to be sent in the structured_data node for eContracts.
Please note that the document_reference_id key-value pair is a required element when submitting structured eContract data. You should use a unique value for every eContract that you send (e.g., a UUID or hash or some other convention that fits your workflow.)
{
"image_files": [...],
"structured_data": [
{
"document_type": "retail_installment_sales_contract_electronic",
"document_reference_id": "partner reference id",
"source": "DealerCenter",
"url": null,
"extracted_data": {
"applicants": {
"applicant1": {
"first_name": "Jo",
"middle_name": null,
"last_name": "Boren",
"suffix": null,
"address": {
"street_address": "8717 South 4th Avenue",
"street_2": null,
"city": "Inglewood",
"state": "CA",
"zip": "90305"
}
},
"applicant2": {
"first_name": "Lucinda",
"middle_name": null,
"last_name": "Bonadio",
"suffix": null,
"address": {
"street_address": "2317 North Winery Avenue",
"street_2": null,
"city": "Fresno",
"state": "CA",
"zip": "93703"
}
}
},
"contract_date": "2021-05-09",
"dealer_name": "Toyota of Hollywood",
"dealer_address": "6000 Hollywood Blvd, Los Angeles, CA 90028",
"vin": "1HGCR2F52GA195235",
"year": 2016,
"make": "Honda",
"model": "Accord",
"vehicle_cash_price": 18998,
"apr": 11.49,
"finance_charge": 8748.35,
"amount_financed": 22136.05,
"total_of_payments": 30884.4,
"total_sales_price": 33884.4,
"down_payment": 3000,
"number_of_monthly_payments": 72,
"monthly_payments_due_date": null,
"usage_type": "Personal",
"odometer": 62940,
"vehicle_condition": null,
"monthly_payment": 428.95,
"form_number": "553-CA-ARB-eps 7/16",
"document_language": "English",
"revision_date": "7/16",
"first_payment_date": "2021-06-23",
"late_fees_due_date": null,
"late_fees_percentage": null,
"late_fees_cap": null,
"total_cash_down": null,
"deferred_down": null,
"rebate": null,
"insurance_charges": [
{
"term": {
"month": null,
"mileage": null
},
"type": "vsc",
"provider": "AUL Corp",
"premium": 3500,
"benefit_amount": null
},
{
"term": null,
"type": "gap",
"provider": "Allstate",
"premium": 500,
"benefit_amount": null
}
],
"other_charges": [
{
"type": "emissions_testing_charge",
"amount": 50,
"category": "government"
}
],
"taxes": [
{
"type": "sales_tax",
"amount": 85
}
],
"fees": [
{
"type": "documentation_fee",
"amount": 85
},
{
"type": "other_fee",
"amount": null
},
{
"type": "other_fee",
"amount": 30
},
{
"type": "license_fee",
"amount": 3
},
{
"type": "registration_fee",
"amount": 192
},
{
"type": "other_fee",
"amount": null
}
],
"trade_in_allowance": null,
"trade_in_pay_off": null,
"trade_in_vin": null,
"trade_in_make": null,
"trade_in_model": null,
"trade_in_year": null,
"trade_in_odometer": null,
"assigned_without_recourse": true,
"lender_name": "Acme Financial, LLC"
}
}
]
}