> For the complete documentation index, see [llms.txt](https://even-financial.gitbook.io/developer-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://even-financial.gitbook.io/developer-center/embeddable-integrations/mobile-sdks/personal-loans.md).

# Personal Loans

## Choosing an Integration Approach

Engine offers two integration paths for personal loans. Both connect users to the same Engine marketplace and produce a similar end-user journey (application form → offer wall). They differ in how that experience is rendered and maintained inside your app.

<table><thead><tr><th width="180">Approach</th><th>Summary</th></tr></thead><tbody><tr><td><strong>Recommended</strong></td><td>Renders Engine's screens natively inside your app. Mature, widely deployed, and supports color customization. Best choice for most React Native integrations today.</td></tr><tr><td><strong>Experimental</strong></td><td>Embeds the Engine marketplace flow as a widget, sharing one implementation across multiple tech stacks (React Native, Flutter, and soon Swift/Kotlin). Newer and evolving, with a smaller bundle size — a good fit if you want a single cross-stack integration.</td></tr></tbody></table>

{% hint style="info" %}
The Experimental approach is labeled experimental while we finalize the cross-stack API. For production React Native integrations today, we recommend the Recommended approach.
{% endhint %}

## Which should I use?

* **Use the Recommended approach** if you are integrating in React Native and want the most stable, battle-tested option with native rendering and branding customization.
* **Consider the Experimental approach** if you need the same integration across multiple tech stacks (Flutter, Swift, Kotlin) and want a single shared implementation with a smaller bundle size.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://even-financial.gitbook.io/developer-center/embeddable-integrations/mobile-sdks/personal-loans.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.