> 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/references-and-tools/appendix/appendix-f-secured-loan-speedbump-details.md).

# Secured Loan Speedbump details

This page contains instructions for when/how to display the [Secured Loan Speedbump](/developer-center/marketplace-integrations/native-api/personal/displaying-offers.md#offer-display-creating-a-speedbump-for-secured-offers)

## What does the speedbump look like?

Engine recommends partners building a Native API integration to create 2 variants of the speedbump, depending on whether:

1. The user clicked “Continue” on an offer in the offer wall itself, which fires a regular speedbump, which on Engine partner pages looks like:

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXchz3tdmt3U0zznwI9zOvzKrbSbhba_R2JfNkQJsYWYG8Ie6hNHgmx_QJDtcXMPC2dXwSvAwH4eGCACXuf2PQn22cvMinQt93_WTHPp4FgsdF9-Na5fnA665YquChMJnzUSh4Ek?key=5yZd6h3DOcrOyHCVA-Ec9g" alt=""><figcaption></figcaption></figure>

2. The user clicked the “More Info” button on an offer in the offer wall, which on Engine partner pages fires a modal containing that Financial Institution's description/disclaimer text. In this flow, the speedbump appears as an info bubble above the "Continue" button:

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXf5Dpue6ds5csnfqxP7atB9g2q_4YdXIJChFL_cOlN8Exam_KG_Be4Yz4Y1ydCfexBnpAOBH2eqiqEl-6IMgFcj0sHNemz2Q9Xtpyoov9A0XQZOiYd931DapqduIFg6dYzEG0yAoQ?key=5yZd6h3DOcrOyHCVA-Ec9g" alt=""><figcaption></figcaption></figure>

##

## When the speedbump should fire

Engine recommends using the following conditions when defining when the speedbump should fire for users:

<table data-header-hidden><thead><tr><th width="217.506591796875"></th><th width="490.564453125"></th></tr></thead><tbody><tr><td><strong>Condition</strong></td><td><strong>Rule</strong></td></tr><tr><td>Offer mix on rate table</td><td><p>Fire ONLY IF ALL are true:<br>(1) Count of lenders on rate table > 1<br>(2) 1 offer on rate table with <code>productSubType</code> “Secured Personal Loan”</p><p>(3) 1 offer on rate table with <code>productSubType</code> NOT “Secured Personal Loan”</p></td></tr><tr><td>User behavior</td><td><p>On Engine, a <strong>regular</strong> speedbump (variant 1 above) fires when users click "Continue" on the offer wall<br></p><p>On Engine, a <strong>more info</strong> modal variant of the speedbump (variant 2 above) fires when users click "More Info" on the offer wall</p></td></tr><tr><td>Rate limits</td><td>None, the speedbump can fire an unlimited number of times per lead and per session</td></tr></tbody></table>

## User Flow Diagram

{% file src="/files/xSIg9FG5mR4Y6nEKmnIw" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://even-financial.gitbook.io/developer-center/references-and-tools/appendix/appendix-f-secured-loan-speedbump-details.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.