Lender FAQ

1. Who is responsible for use of Instamo?

Responsibility depends on how Instamo is deployed.

Where we engage with intermediaries (brokers), Instamo operates as a secure autofill environment. The adviser remains fully responsible for login, review, and submission - exactly as they are today when using Chrome, Edge, or Safari Autofill.

There is no fundamental difference in behaviour from the browser tools advisers already use. However, Instamo operates within a zero-trust, secure environment - comparable in philosophy to privacy-focused tools such as DuckDuckGo or ProtonMail. Data is not cached in shared browser environments, and the risk of incorrectly re-keying and storing inaccurate data locally is removed.

Where we engage directly with lenders, Instamo provides an end-to-end automation journey configured to your requirements. This can include Single Sign-On (SSO), accelerated 30-second Decisions in Principle, 60-second Full Mortgage Applications, and bespoke pre- and post-application workflows. In these cases, deployment and governance are structured in partnership with the lender.

2. How does Instamo actually work?

Instamo works like Chrome, Edge, or Safari Autofill - but purpose-built for regulated mortgage workflows.

It simply populates visible form fields inside a lender’s portal using adviser-approved client data. It does not access databases, integrate into backend systems, or bypass lender controls. It types into the same fields a human would - just more consistently and without re-keying risk. Effectively Instamo is a super controlled, secure browser like Chrome, Safari or Edge.

3. Does Instamo store or reuse login credentials?

No. Advisers always log in manually using their own lender credentials. Instamo does not store, reuse, inject, or auto-fill login information. We act just like a normal browser.

Credentials remain within the adviser’s browser session and are never transmitted to Instamo servers.

4. How is this more secure than manual admin data entry?

Manual re-keying of financial data introduces operational risk - including typing errors, field mismatches, omissions, and inconsistent formatting.

Instamo eliminates the risk of an administrator incorrectly keying sensitive income, credit, or affordability data by mapping structured fact-find information directly into visible lender fields.

Fewer human touchpoints means lower error rates, stronger data integrity, and reduced compliance exposure.

5. What is the difference between the broker solution and the lender solution?

The broker solution is secure autofill. It behaves just like standard browser autofill advisers already use today - but purpose-built for mortgage portals. It runs at a natural human pace, with the adviser present, reviewing and pressing submit. Nothing is accelerated.

The lender solution is infrastructure enhancement. It acts as a configurable submission layer that sits alongside your existing portal - without requiring core system redevelopment.

At lender level, we can intelligently optimise speed - enabling approximately 30-second Decisions in Principle and 60-second Full Mortgage Applications where appropriate.

We also design workflows with you - including affordability calculations, net income validation, structured pre-submission checks, SSO integration, and configurable post-submission journeys.

6. Can Instamo submit applications or trigger credit searches?

No. Instamo will never click “Submit” or initiate any action that could trigger a soft or hard credit search.

Submission remains a deliberate adviser action unless explicitly configured in a lender-approved automation environment.

7. Are advisers always in control?

Yes. Instamo is human-in-the-loop by default. Advisers initiate automation, monitor progress in real time, review populated data, and manually confirm submission unless operating within a lender-configured automated flow.

8. Does Instamo scrape or manipulate lender systems?

No. Instamo does not scrape data, parse HTML, manipulate backend systems, or interfere with portal logic.

It interacts only with visible input fields - exactly as a human user would.

9. Where does automation originate from?

All automation originates from static, UK-based IP addresses. Dedicated IPs or subnets can be configured for isolation and transparency.

10. Are sessions visible and auditable?

Yes. Instamo behaves like a controlled autofill session rather than a background system integration.

The adviser can see fields being populated in real time, exactly as if they were typing themselves. Nothing happens invisibly or behind the scenes.

Where required, sessions can be logged to show who initiated the autofill, when it occurred, and what data was populated - creating a clear and defensible audit trail.

11. How does Instamo align with FCA and operational resilience expectations?

Instamo is designed around operational resilience, third-party risk control, and auditability.

With UK-based infrastructure, full session logging, human-in-the-loop controls, and no backend system interference, the platform supports FCA, PRA, and FSMA 2023 operational resilience standards.

12. Who can we contact with further questions?

We welcome direct engagement with lender risk, compliance, and technology teams.

Please contact us at hello@instamo.co.uk.