Displaying 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 collect and send to Engine’s API in order to generate offers

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

Required Fields

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

• Financial Services partner Logo

• Offer Amount ($)

• Offer Term Length (#)

• Offer Term Unit (ie. Month)

• Offer Term Description

• Offer APR Amount (%)

• Offer APR Description

• Offer Monthly Payment Amount ($)

• Offer Monthly Payment Description

• Pre-Approved or Pre-Qualified designation

• Offer Disclaimer

• Offer More Information

Here is an example of how an unsecured personal loan product is represented on Engine’s owned experiences:

Upon clicking the Disclaimer & more info linked text, this pop up appears which displays the Offer Disclaimer and More Information:

For Secured Loan or Line of Credit products, two additional fields must be displayed:

• Product Type Label (ie. Secured Loan)

• Product Type Disclaimer

Here is an example of how these products are represented on Engine’s owned experiences:

Secured Loan:

Line of Credit:

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.”

Offer Display Logic

Engine recommends partners building a Native API integration to display the highest Rec Score offer (Engine’s Machine Learning Algorithm offer score) from each Financial Services partner and group offers based on the Financial Services partner.

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

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

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.

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.”

\