Displaying Personal Loan Offers

This section of the guide is divided into two parts:

• Required Fields: This covers all of the fields partners building a Native API integration will need to display from Engine's offer responses

• Compliance: This covers the various consents, disclosures and guidance required to receive approval from the Engine Compliance team and Financial Services partners

Required Fields

This section is meant for Loan product offers only. Leads who are not eligible for any Loan offers may receive Secondary Offers instead. For Info on displaying other product type offers:

• HELOC offers

• Secondary offers (non-personal-loan products)

Engine’s Financial Services partners require partners building a Native API integration to display a basic set of information associated with their Loan offers. Here are the required fields to display:

• Financial Services Partner Logo

• Offer Amount ($)

• Offer APR Amount (%)

• Offer Monthly Payment Amount ($)

• Offer Term Length (#)

• Offer Term Unit (e.g. Month)

• CTA (hyperlinked to clickthrough URL), exemplified below as "Continue" button

• Pre-Approved or Pre-Qualified designation

• Offer Description

• Offer Disclaimer

Mapping API Fields to Offer Card

Please see Appendix D for guidance on mapping API response fields to an offer card for the following products:

• Personal Loan (Unsecured)

• Secured Loan

• Line of Credit

Ranking Logic

Engine recommends partners building a Native API integration to display the highest Recommendation Score offer (calculated by Engine’s Machine Learning Algorithm) from each Financial Services partner, and group offers by the Financial Services partner.

Here is an example of how it is represented on Engine-owned experiences:

Sample Fiona Offer Table

Screenshot of Sample Fiona Offer Table

In order to receive approval from the Engine Compliance team and Financial Services partners, partners building a Native API integration must adhere to the following compliance requirements on the offer display page.

Creating a Speedbump for Secured Offers

Engine recommends partners building a Native API integration to enable a "speedbump" (i.e. a small friction point in the UX) when a user attempts to convert on a secured loan, assuming a few logical conditions are true (explained in the Appendix linked below). This speedbump should be something like a pop-up modal that warns the user that the offer they have chosen requires collateral, in order to ensure the user stops to understand terms before continuing.

Engine built this functionality into our Hosted Integrations after finding that conversion rates on clicks into secured loans were dramatically lower than on unsecured loans, implying that many users did not sufficiently understand collateral requirements before clicking on offers. The effect of this speedbump (through our A/B testing, validated at 95% confidence), therefore, is a material increase in conversion rates and revenue per lead.

Please refer to Appendix F for details, including:

1. What the speedbump looks like on Engine partner pages, and suggested copy

2. When the speedbump should fire, i.e. the logical conditions

3. Examples of the UX on Engine's hosted integrations (as a guide for how to craft your own Native UX)

Special Instructions for Integrations within Mobile Apps

In order for an app to be available in the Google Play App Store, it must adhere to Google’s established advertising guidelines for financial services. Google prohibits offers for loans with an APR of 36% or higher. To ensure product offerings on our marketplace do not impact an app’s availability in the Google Play App Store, our API allows some fields in responses to be returned with null values. The following guidance explains how to present these offers.

When an offer is sanitized, that offer object (i.e. an element object in the loanOffers array) will have the following fields returned as null:

termLength = null, 
termUnit = null, 
maxApr = null, 
minApr = null, 
meanApr = null, 
feeRate = null, 
maxFeeRate = null, 
minFeeRate = null, 
feeFixed = null, 
maxFeeFixed = null, 
minFeeFixed = null, 
prepaymentFee = null, 
monthlyPayment = null, 
maxMonthlyPayment = null, 
minMonthlyPayment = null, 
meanMonthlyPayment = null, 
maxTotalPayment = null, 
minTotalPayment = null, 
meanTotalPayment = null, 
displayTermUnit = null, 
aprType = AprType.Fixed, 
aprDescription = null, 
monthlyPaymentDescription = null, 
termDescription = null

Your front-end UI should not break if any of these fields is null - in this scenario, you should display the other fields returned as normal (logo, max amount, CTA URL, etc). In Engine's owned and operated spaces, that offer card will look like this:

Offer card with details sanitized for the Google Play store

Once the user clicks on the CTA and enters the lender's site, they will see the other relevant details for that offer.

Compliance

In order to receive approval from the Engine by MoneyLion Compliance team and Financial Services partners, partners building a Native API integration must include the following items on the offer display page.

Please see our Compliance Guidelines for more information.

General Disclosures

Partners building a Native API integration must include the Advertiser Disclosure, Representative Example & APR Disclosure, and Other Disclosure on the offer display page, using the same guidance as provided in the previous section.

The below language must be displayed on the offers page, regardless of whether or not offers were available for the user:

• “If you did not receive an offer from a specific Lending Partner, they may not have been able to determine whether you qualified for a personal loan based on the information you provided. No credit decision has been made. You may still qualify for a personal loan from our partners.”