> ## Documentation Index
> Fetch the complete documentation index at: https://help.leaf360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Arive

> Connecting Arive to Leaf360, matching statuses in both directions, and what actually moves across when a loan is pulled in or synced back.

Arive is a loan origination and point of sale system. Connecting it lets an administrator bring Arive loans into Leaf360, keep a loan's status in step in both directions, and, on many loans, keep the borrower's own details current as the loan moves.

## Where it is, and who sets it up

Open **Settings**, then **Integrations**. The **Arive** card sits among the built in connectors, described there as a loan processing platform connected with issued credentials and a portal link.

<Note>
  The Arive card is administrator only. It does not appear on the Integrations shelf for anyone else, and the connection it creates is shared by the whole company rather than owned by one person.
</Note>

## Connecting

Opening the card starts on a **Settings** tab with a choice of connection mode:

| Mode               | What it needs                                            |
| ------------------ | -------------------------------------------------------- |
| Direct credentials | Your company's Arive credentials, entered directly       |
| **Zapier**         | A webhook based connection instead of direct credentials |

Under direct credentials, an administrator enters the **Arive Portal URL**, then a **Client ID**, **Client Secret** and account key, each saved with its own button. A **Test Connection** button confirms the credentials work.

## Two mapping tabs, two directions

Once connected, Arive opens several tabs, and two of them are about keeping statuses lined up between the two systems.

**Status Mapping** is the writeback direction: when a loan's status changes in Leaf360, this mapping decides what status gets set on the matching loan back in Arive. It only appears in the direct credentials mode.

**Arive to Leaf360 Mapping** is the other direction: when a loan's status changes in Arive, whether by someone updating it there or by Leaf360 pulling the latest version, this mapping decides two things at once, which of your company's own loan statuses the Leaf360 loan should move to, and which lead stage and status the matching lead should carry. Each row can also be set to skip updating the loan status altogether, for an Arive status where you would rather leave the Leaf360 side untouched. An administrator can create a new loan status or lead status right from this tab if the one they need does not exist yet.

<Note>
  Both mapping tabs, along with **Loans**, **Webhooks** and the two event log tabs, only open once the connection shows as connected on the Settings tab.
</Note>

## Pulling and syncing loans

The **Loans** tab searches Arive directly, by borrower name, borrower email or loan number. Select one loan or many and click **Sync to Leaf360** to bring them in, or open a single loan and use **Sync Loan Status** to refresh just that one.

What comes across on a synced loan, based on the mapping above, includes the loan amount, credit score, purchase price, down payment and appraised value, the loan type (FHA, VA, USDA or conventional), lien position and amortisation details, occupancy, the property address, loan to value and debt to income figures, and the estimated and actual closing dates. On the borrower side it carries across the primary borrower and any co-borrowers, including date of birth and address, and Leaf360 checks co-borrowers by email, phone, name and date of birth together so the same person is not added twice.

<Note>
  On a loan that has just funded as a purchase, the borrower's address on their lead record updates to the property they bought. On every other loan, their stated home address is used instead, so a loan still in progress does not overwrite where a borrower says they currently live.
</Note>

## Arive loans imported by file

Loans brought in through the general loan importer, described on the [Loans](/mortgage-crm/loans) page, also recognise Arive's own column headers automatically when you upload a file exported from Arive, including a primary borrower and co-borrower's military service status and preferred language, alongside the rest of the borrower and loan fields. See [Import Data](/mortgage-crm/import-data) for importing outside of a specific loan pipeline.

## Common problems

<AccordionGroup>
  <Accordion title="I do not see the Arive card on the Integrations shelf">
    It is administrator only. Ask an administrator at your company to set it up, or to check whether it is already connected.
  </Accordion>

  <Accordion title="The mapping and loans tabs are greyed out">
    They only open once the Settings tab shows a working connection. Save credentials and confirm with Test Connection first.
  </Accordion>

  <Accordion title="A synced loan landed on the wrong status, or the matching lead did not move">
    Check the Arive to Leaf360 Mapping tab. The Arive status that loan carries may be mapped to a different Leaf360 status than you expected, or set to skip loan status updates entirely.
  </Accordion>

  <Accordion title="Changing a loan's status in Leaf360 did not update it in Arive">
    Writeback only runs in the direct credentials mode, and depends on the Status Mapping tab having an entry for that status.
  </Accordion>
</AccordionGroup>

## Related

* [Loans](/mortgage-crm/loans)
* [Pipeline Stages](/mortgage-crm/pipeline-stages)
* [Import Data](/mortgage-crm/import-data)
* [Integration settings](/mortgage-crm/integration-settings)