# Dos & Don’ts for All HELOC Supply Partners

## **Dos**

* DO focus on the consumer shopping angle. For example, include language like:
  * “This is a shopping option”
  * “Consider these options, but there are more”
  * “This does not include all lenders or available HELOCs that may be available to you”
* DO clearly show Engine by MoneyLion’s (formerly Even Financial’s) NMLS ID on all solicitations and advertisements.

## **Don’ts**

* DO NOT recommend or endorse a lender or Engine by MoneyLion (e.g. “Company A is a preferred HELOC lender”, “Company B is our HELOC partner”, “Company C is a superior HELOC provider”, etc.).
* DO NOT make or receive payouts based on a lead’s performance after the lead is transferred to a lender, if services are not performed after this event.
  * e.g. if services are not performed after lead transfer, making or receiving a payout based on a HELOC approval or funding violates RESPA. \*Engine by MoneyLion maintains contractual payouts with HELOC lenders at Fair Market Value. Payouts occur prior to full approval/funding\*.
* DO NOT engage leads in states where Engine by MoneyLion does not hold an active mortgage license.
  * Current as of 4/2/2024, that list of states is: HI, MA, MD, NH, NV, NY, UT, VA
* DO NOT enter into exclusive agreements where services are performed for one lender.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://even-financial.gitbook.io/developer-center/native-api-integrations/heloc/dos-and-donts-for-all-heloc-supply-partners.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.