Open Banking Integration for Lettings: A Guide for Agents
A tenant wants the flat. The landlord wants an answer. You're still waiting for a blurry PDF called “final-final-bankstatement2”.
By the time the applicant finds three payslips, forwards a bank statement from the wrong account, and says their freelance income “doesn't always show the same way”, the property has already lost momentum. Then comes the manual slog. Chasing employers. Comparing names and dates. Squinting at cropped screenshots. Wondering whether that salary credit is genuine, whether the statement has been edited, and whether anyone in the chain has time to do this properly.
That old workflow doesn't just waste time. It creates risk. Good tenants get delayed, weak applications sit in limbo, and your team spends hours doing detective work that software can do more consistently.
Open banking integration matters because it tackles that exact mess. For letting agents, it isn't some abstract fintech trend. It's a practical way to verify affordability using bank-permissioned data, without asking applicants to hand over passwords or email sensitive documents back and forth. Used well, it helps you move from “please resend page 4” to a faster, cleaner decision process.
The End of Chasing Payslips and Bank Statements
Monday morning often starts the same way. One applicant hasn't uploaded anything. Another has sent screenshots instead of statements. A third has a full-time salary going into one account and side income landing somewhere else entirely. Your negotiator is trying to progress the let while your admin team is stuck in a loop of reminders.
That's the core problem with manual referencing. It's not just admin-heavy. It breaks down precisely when an applicant's finances don't fit a neat template. If someone has one employer, one account, and one monthly salary, the process is manageable. Once they're self-employed, freelance, gig-based, recently changed jobs, or split money across multiple accounts, the paperwork starts hiding more than it reveals.
Why the old process creates blind spots
A bank statement is only as useful as the person reviewing it. Two agents can read the same statement and come away with different conclusions. One spots regular income. The other notices gambling spend, returned direct debits, or large unexplained transfers. Neither has much help from the format.
Then there's fraud. Edited PDFs, selective screenshots, missing pages, and statements from accounts that don't show the full picture are all familiar problems in lettings. The old process relies on applicants sending documents and on staff spotting what's wrong. That's an expensive way to manage risk.
Most referencing delays don't come from complex compliance. They come from fragmented information and too much manual checking.
Open banking integration changes the source of truth. Instead of asking the applicant to collect proof and present it in the right format, the system retrieves permissioned bank data directly through the regulated banking framework. For agents, that means less paper chasing and fewer judgement calls based on partial evidence.
What changes in day-to-day lettings
The immediate benefit is operational. Staff stop spending so much time requesting documents, following up, and re-checking the same files. Of greater significance, the quality of the affordability view improves.
You can assess the applicant in front of you, not the applicant who happens to have the tidiest paperwork. That's a big difference in a market where speed matters and good applicants won't wait around forever.
What Is Open Banking Integration
At 5:20 pm on a Friday, the applicant says they can afford the rent, but their income comes from two part-time jobs, weekend freelance work, and the occasional family transfer. That is where open banking integration earns its place in lettings. It gives your referencing process direct, permissioned access to the bank data needed to assess affordability without relying on a stack of PDFs that someone in the office has to interpret by hand.
Open banking works like a temporary key card. The tenant does not share their banking password, PIN, or full login details with you or your referencing provider. They approve limited access to specific account information for a set purpose, usually income verification and affordability checks, and only for the period covered by that consent.
For agents, the point is simple. You get a cleaner view of how money really moves through the applicant's account, which matters far more in lettings than neat paperwork ever did. That is especially useful when you are dealing with self-employed tenants, multiple income sources, irregular pay dates, or applicants whose financial picture does not fit the standard three-payslip template.
What integration means for a letting agent
For a developer, integration means systems talking to each other through APIs. For a letting agent, it means your referencing platform can prompt the applicant to connect their bank account within the referencing journey, collect the agreed data, and use it to support an affordability decision.
You are not building connections to HSBC, Barclays, Monzo, or NatWest yourself. Your software provider or referencing partner handles that technical layer in the background.
The practical benefit is similar to how finance teams manage receipts efficiently with Xero. The value is not the word "integration". The value is fewer manual steps, fewer copy-and-paste errors, and less time wasted chasing missing information. In tenant referencing, that means less rekeying from statements, fewer judgment calls based on partial documents, and a more consistent process across your team.
What the tenant sees
A well-designed open banking flow should feel controlled and predictable. The applicant selects their bank, is redirected to a secure bank or banking app environment, logs in there, and approves the request. Their credentials are entered with their bank, not into your agency system.
That distinction matters. It reduces one of the biggest trust barriers in referencing, especially with applicants who are wary of sharing financial information.
A good applicant journey makes three points clear:
- What you are checking. Usually income patterns, regular commitments, and affordability indicators.
- Why you are checking it. To support the tenancy referencing decision.
- How consent works. Access is limited, specific, and time-bound.
If you are reviewing suppliers, this guide to tenant screening software for letting agents helps put open banking in the wider context of digital referencing tools.
Practical rule: If a provider cannot explain the tenant journey in plain English, your team will struggle to explain it to applicants under time pressure.
How Open Banking Helps You Place Tenants Faster
Speed in lettings isn't a vanity metric. It affects fall-throughs, landlord confidence, and how many live deals your team can handle without drowning in admin.
Open banking helps because it removes one of the slowest parts of referencing. Instead of waiting for applicants to assemble evidence, you ask them to approve access to their bank data through a structured digital flow. That shortens the gap between application and decision, especially when the applicant's income doesn't fit neatly on three payslips.
Faster decisions without guesswork
By March 2022, 10 to 11% of digitally enabled UK consumers were active users of at least one open banking service, up from 6 to 7% in March 2021, according to the Open Banking Impact Report key insights on adoption and business use. For agents, the practical takeaway is simple. A growing share of applicants already recognise this kind of consent-driven bank connection, so you're not introducing a completely foreign process.
That familiarity matters at the sharp end of a tenancy. If the applicant understands the flow and can complete it on their phone in a few steps, you cut out the dead time between “please send documents” and “have you had a chance to upload them yet?”
If you want a benchmark for where delays usually creep in, this breakdown of how long tenant referencing takes shows why paperwork and chasing are usually the bottleneck.
Better data, fewer forged documents
Manual document review has a built-in weakness. You're reviewing what the applicant sends, in the format they choose to send it. Open banking changes that. The data comes from the bank connection under the applicant's consent, which reduces the chance of edited statements or selective omissions.
That doesn't mean fraud disappears. It means the fraud problem shifts from “can we spot a fake PDF?” to “can our provider interpret the data and flag issues properly?” That's a better place to be.
A strong affordability review can also surface patterns that a quick glance at statements might miss:
- Income consistency. Is regular money coming in, even if payment dates move around?
- Account behaviour. Are there signs of persistent strain, missed commitments, or unusual volatility?
- Multi-account reality. Does the applicant spread salary, bills, and spending across different banks?
A smoother experience means fewer drop-outs
Applicants don't enjoy referencing. They tolerate it. The best process is the one that asks for the least unnecessary effort while still giving you confidence in the result.
A digital bank check usually feels easier than hunting down PDFs, especially for younger renters and applicants who manage everything on mobile. That improves the tone of the application. Your agency looks organised, not stuck in a paperwork maze.
A faster referencing journey doesn't just help operations. It tells applicants and landlords that your agency can actually get deals over the line.
Three Paths to Open Banking Integration
Monday morning. Your negotiator is chasing missing bank statements, a landlord wants an update, and the applicant says their freelance income lands in a different account. At that point, "integration" can sound like another tech project your team does not need. For most letting agents, it is a buying decision, not a build decision.
There are three practical routes. The right one depends on whether you are running a lettings business, a software product, or regulated financial infrastructure.
Path one is building it yourself
A direct build means connecting to banking interfaces yourself and taking responsibility for security, consent flows, data handling, and ongoing maintenance. That route fits fintech firms with engineers, compliance support, and a product team. It does not fit a typical branch or lettings operation that only wants faster, more reliable affordability checks.
The advantage is control over every step. The cost is time, money, and operational distraction. You would be building plumbing when the actual business goal is placing good tenants faster.
| Path | Best for | Main drawback |
|---|---|---|
| Build in-house | Large fintech or specialist platform | High technical and compliance burden |
| Use an aggregator or API provider | Software company with product team | Still needs integration and support effort |
| Use an end-to-end referencing platform | Letting agents and landlords | Less custom control |
Path two is using an aggregator
An aggregator sits in the middle. It handles connectivity across multiple banks and gives your software a more consistent way to request and receive account data.
That can work well for proptech vendors or larger groups building their own workflows. But an aggregator is still a component, not a finished referencing process. Your team or software partner still needs to handle applicant journeys, consent messaging, report logic, exception cases, support questions, and the day-to-day reality of fragmented income.
I usually explain this with a familiar proptech comparison. If you have looked at integrating payment processing APIs, the pattern is similar. The API solves the connection layer. It does not solve the full operational workflow your staff and applicants have to use.
As noted earlier, UK open banking is built on regulated API standards rather than old-style screen scraping. That is why aggregators exist in the first place. They reduce bank-by-bank complexity. They do not remove the work of turning raw financial data into a lettings decision your team can trust.
Path three is using an end-to-end service
For most letting agents, this is the sensible option. An end-to-end referencing platform already has the bank connection, the consent journey, the affordability logic, and the reporting layer built into one process.
That matters because lettings teams do not need open banking in isolation. They need a system that can cope with applicants paid weekly, applicants with side income, and applicants who spread money across multiple accounts. They need a report their negotiators can read quickly and a process that does not create more chasing.
You give up some custom control. In return, you get speed, support, and a workflow designed for live tenancy applications rather than a generic data feed.
Do not buy open banking because the supplier uses technical language well. Buy it because your team can make clearer decisions, spot risk earlier, and spend less time collecting paperwork.
The better question is simple. Which provider already turns bank data into a referencing process that works for UK lettings?
A Typical Open Banking Referencing Workflow
The easiest way to judge open banking is to follow a real applicant journey.
Take Sarah. She's applying for a rental property. She has a full-time job, but she also does freelance work on the side. Under a manual process, she's awkward to assess. Her salary lands in one account, freelance payments hit another, and the second income doesn't appear in tidy monthly amounts.
What the agent does
From the agent's side, the process is straightforward. Sarah receives a secure referencing request. Instead of being asked to upload a patchy bundle of statements and payslips, she's invited to complete a bank connection as part of the affordability check.
At this point, the agent's main job is communication. Sarah needs to know why the check is being requested, what it covers, and that she'll authorise the connection through her own bank.
What Sarah sees on her phone
Sarah taps the link, chooses her bank, and is redirected into a secure banking journey. She authenticates in the way her bank normally requires. That could be through her banking app, a biometric prompt, or another approved authentication step.
She then approves access to the relevant account information. If she receives income into more than one account, a good workflow lets her connect both.
Open banking proves its value in lettings, especially given that one of the biggest real-world referencing problems is fragmented income. Guidance around open banking use cases highlights applicants with multiple accounts, variable gig income, and irregular pay as cases where a well-designed integration can analyse transaction data to build a fuller income picture rather than relying on one obvious monthly salary line, as explained in Stripe's discussion of common open banking use cases and income verification.
What happens behind the scenes
Once Sarah consents, the platform retrieves the authorised transaction data and analyses it. The better systems don't just search for one salary keyword. They look for recurring patterns, classify credits, and separate regular income from one-off transfers or noise.
That matters because freelance income rarely behaves like payroll. Some months are stronger than others. Payment references vary. Clients pay late. A capable system has to interpret that context, not reject the application because it doesn't resemble a textbook employee record.
A strong workflow usually follows this pattern:
- Invitation sent. The applicant receives a secure request as part of referencing.
- Consent completed. They connect their bank account or accounts through the bank's own secure flow.
- Data analysed. Income, affordability signals, and account behaviour are reviewed.
- Report returned. The agent gets a usable output rather than raw banking data.
If a process only works for tenants with one salary and one current account, it doesn't work for modern lettings.
By the time the report reaches the agent, Sarah's affordability position is clearer than it would have been from a stack of manually reviewed PDFs. That's the key benefit. Less effort for the tenant, less ambiguity for the agency.
Understanding Regulations and Tenant Consent
Agents don't need to become compliance lawyers, but they do need to understand the practical rules well enough to answer tenant questions and spot weak providers.
At ground level, open banking rests on a simple principle. The tenant stays in control. Access to bank data must be permission-based, specific, and transparent. If that principle gets muddy, the process stops feeling safe, and applicants hesitate.
What good consent looks like
A proper consent journey shouldn't bury the important details in vague wording. The applicant should be told what data will be accessed, why it's needed, and what happens next. They should also know they're approving access through a secure banking flow, not handing credentials to a referencing company.
That sounds obvious, but poor implementations still create friction. If your team can't clearly explain the purpose of the check, applicants may assume you're asking for blanket surveillance rather than a targeted affordability review.
A good consent flow should include:
- Clear purpose. The applicant understands this is for tenant referencing and affordability assessment.
- Defined scope. The request is limited to the account information needed for that purpose.
- Visible control. The tenant can see they're granting permission and that the permission isn't indefinite.
Fairness matters as much as security
There's another issue agents often overlook. Not every applicant will fit neatly into a digital bank-data process. Some may have limited digital banking access. Some may be uncomfortable consenting. Others may have thin or unusual account histories that don't tell the full story.
Research from the World Bank and CGAP argues that open banking supports inclusion only when it's designed around underserved users as well as efficient digital users. In lettings, that means having a fair fallback process for applicants with non-traditional financial lives or those unable or unwilling to use open banking, as discussed in this paper on designing open banking for financial inclusion.
That has a direct compliance angle. Fair treatment isn't only about data security. It's also about not turning a convenient digital tool into an unspoken barrier to housing.
What agents should say when tenants ask questions
Most tenant questions are practical, not technical. Your team should be ready to answer them plainly.
| Tenant question | Strong answer |
|---|---|
| Do I have to share my password? | No. You authorise access through your bank's own secure process. |
| What are you looking at? | Information relevant to affordability and referencing, not unrestricted access. |
| What if I don't want to use it? | There should be a fallback route so your application can still be assessed fairly. |
For the wider compliance picture around identity, sanctions, and risk checks, this guide to anti-money laundering checks in tenant referencing helps join the dots.
How to Choose the Right Referencing Partner
Most providers can say they “offer open banking”. That tells you almost nothing.
The difference becomes evident when a live applicant tries to connect an account on a Friday evening, consent expires halfway through the journey, or the person you're referencing has three income streams and no standard payslip pattern. That's where weak systems crack.
Ask about reliability before features
Production-level open banking is an operational reliability challenge as much as a data-access one. Industry guidance points to the importance of handling authentication failures, consent expiry, monitoring, and partner-specific error mapping in real time, which is why these are the right pressure-test questions for vendors, as covered in Kong's guide on operational reliability in open banking implementations.
In plain English, don't just ask what the system can do on a sales call. Ask what happens when something goes wrong.
Here are the questions that matter:
- When a bank connection fails, what does the applicant see next? A dead end is not a workflow.
- How do you handle expired consent? If the answer is “the applicant starts again”, expect drop-offs.
- How are bank-specific errors translated for agents and applicants? Raw technical messages are useless in lettings.
- What happens outside office hours? Referencing doesn't only fail between nine and five.
Pressure-test how they assess real applicants
A provider may have solid bank connectivity and still be poor at affordability interpretation. That's a separate issue.
Ask how they handle applicants with:
- Multiple current accounts used for different income and spending patterns
- Variable self-employed or gig income that doesn't appear on fixed dates
- Joint applications where affordability needs a combined view
- Irregular deposits that need explanation rather than automatic rejection
You should also ask what the final output looks like. Agents don't need a dump of transaction lines. They need a report that supports an informed decision and highlights where human review is still required.
For a broader comparison of what to look for in a supplier, this guide on choosing a tenant referencing company for lettings is a sensible checklist.
Look for process maturity, not just product polish
Good demos hide bad operations. Ask to see the awkward bits. What happens when an applicant refuses consent? How are edge cases reviewed? How is data deleted? How are applicants supported if they get stuck?
The best vendor isn't the one with the slickest dashboard. It's the one your team trusts when the application is messy and the deadline is tight.
A reliable referencing partner should make your operation calmer. Fewer chasers. Fewer mysteries. Fewer “we're waiting on the applicant” excuses.
Embracing the Future of Tenant Referencing
The old referencing model asked applicants to prove their finances by assembling documents and asked agents to judge those documents under time pressure. That was always clunky. It now looks outdated.
Open banking integration gives letting agents a cleaner route. It improves affordability checks by pulling permissioned account data into the referencing process, reduces reliance on emailed statements, and handles real-life income patterns more effectively than a manual document pack ever could. For busy agencies, that means fewer delays and more confidence in the final decision.
The key shift is this. Adopting open banking isn't a technology project for most agents. It's a supplier decision. You don't need to build bank connections, manage API standards, or become a fintech business. You need a referencing partner that has already solved those problems and can present the result in a way your team can use quickly.
That's why open banking now sits in the same wider category as other practical automation tools reshaping agency operations. If you're already thinking about workflow efficiency, this look at transforming real estate with AI is worth reading alongside your referencing stack.
The agencies that move first won't win because they sound more forward-thinking. They'll win because they progress tenancies faster, reduce avoidable risk, and give landlords a more professional service.
If you want a faster, cleaner referencing process without the usual chasing, passref is built for UK letting agents who need reliable decisions quickly. You submit the applicant's name and email, and passref handles the secure workflow, automated follow-ups, affordability checks, identity checks, landlord and employment references, and clear Pass, Conditional, or Refer outcomes. It's a practical way to modernise tenant referencing without adding more admin to your team.