PSD3 and Open Banking: What Real Estate Companies Need to Know

PSD3 is coming in 2027-2028. What changes for real estate payments: faster APIs, mandatory payee verification, variable recurring payments, and what to do now.

If you've ever lost a week chasing a misdirected rent payment because a tenant mistyped an IBAN, or had to explain to a landlord why their monthly settlement is delayed because the bank API went down during collection day — PSD3 is the regulation that fixes those problems.

PSD3 (the third Payment Services Directive) is the EU's upcoming overhaul of how digital payments work across Europe. The European Parliament and Council reached provisional agreement on PSD3 and its companion regulation (PSR) in November 2025. The final text is expected by mid-2026, with an 18-month transition period — meaning full compliance is required by late 2027 or early 2028.

If you already use open banking for rent collection, PSD3 makes your setup significantly better. If you're still on traditional direct debit or card processing, PSD3 is another reason to move — because the capabilities it introduces solve specific problems that property managers deal with today.

This article covers the four PSD3 provisions that directly affect real estate payments, what changes they trigger, and what you should do now versus what can wait.

Verification of Payee — No More Wrong-Account Payments

This is the PSD3 provision with the most immediate impact on property operations.

Under PSD2, if a tenant initiated a bank transfer to pay rent and typed the wrong IBAN, the money went to the wrong account. Recovering it required manual intervention, often taking weeks. Under PSD3, Verification of Payee (VoP) becomes mandatory for all EU credit transfers. Before a payment is executed, the tenant's bank verifies that the account holder's name matches the IBAN provided. If it doesn't match, the tenant gets a warning before the payment goes through.

For property managers, this eliminates a surprisingly common operational headache. Tenants changing properties, entering an old landlord's IBAN, or mistyping a single digit — these errors create reconciliation incidents that consume disproportionate staff time relative to the amounts involved. A single misdirected rent payment of €1,200 can take 5-10 hours to resolve when you factor in identifying the error, contacting the tenant, tracing the original payment, and coordinating with the receiving bank.

VoP was already required for SEPA Instant and SEPA Credit Transfers from October 2025. PSD3 extends it to all payment types and strengthens the liability framework — banks that fail to verify payee information share liability for misdirected funds.

What to do now: If you use open banking payment initiation, VoP is already active on SEPA transfers. Ensure your payment provider surfaces VoP confirmation in the payment flow so tenants see the verification step. If you use direct debit, VoP doesn't apply (it's a creditor-initiated payment) — this is one more advantage of moving to open banking initiation.

API Performance Standards — Reliability You Can Count On

PSD2 required banks to provide APIs for open banking, but didn't specify how fast or reliable those APIs had to be. The result: inconsistent API quality across banks, with some returning responses in milliseconds and others timing out regularly. For property managers running automated monthly rent collection, an unreliable bank API means failed payments that require manual follow-up.

PSD3 introduces concrete performance requirements. Banks must deliver API responses in under 500 milliseconds and maintain 99.95% uptime. They must also publish quarterly API performance reports, creating transparency and accountability.

For real estate operations, this means open banking becomes more reliable as a primary payment rail. If you've hesitated to move rent collection to open banking because of inconsistent bank API quality, PSD3 addresses that concern directly. A 99.95% uptime requirement means less than 4.4 hours of downtime per year — comparable to card network reliability.

Banks must also allow payment initiation providers to use their own interfaces during bank API downtime. This fallback provision ensures that a bank's technical issues don't block your rent collection — your payment provider can route through alternative channels until the bank's API recovers.

What to do now: Ask your open banking payment provider about their PSD3 readiness timeline and how they plan to leverage the new API performance standards. The best providers are already testing against PSD3-compliant API specifications.

Variable Recurring Payments — Solving the Variable Rent Problem

If you manage properties with variable monthly charges — utility contributions that change seasonally, service charges that adjust quarterly, or co-living spaces where the monthly amount depends on selected services — you know the limitation of current recurring payment methods.

SEPA Direct Debit mandates are set for a fixed amount. Variable charges require either mandate updates or separate one-off collections. Open banking under PSD2 requires Strong Customer Authentication (SCA) for each individual payment, meaning the tenant must approve every monthly charge in their banking app.

PSD3 introduces Variable Recurring Payments (VRP): the tenant authorizes a recurring payment with a maximum amount and frequency, and the property manager initiates each payment at the actual amount owed — without requiring individual SCA for each transaction (as long as the amount stays within the pre-authorized ceiling).

For a co-living operator managing 200 beds where monthly charges vary by €50-€200 depending on utility consumption and optional services, VRP eliminates the choice between fixed mandates (inaccurate) and per-payment authentication (friction). The tenant approves once, the operator collects the correct amount each month automatically.

What to do now: VRP implementation details are still being finalized by the European Payments Council (EPC). The framework won't be available until late 2027 at earliest. But if you're choosing a payment provider now, ask whether VRP is on their roadmap — providers that are architecturally prepared will be first to market when the standard is finalized.

Enhanced Fraud Protection and Liability

PSD3 broadens the liability framework for payment fraud. Under PSD2, fraud liability was primarily between the payer's bank and the payer. PSD3 distributes liability across the entire payment chain — including the payee's bank and the payment initiation provider.

For property managers, this means stronger protection when receiving payments. If a fraudulent payment is initiated to your account — whether through identity theft or authorized push payment fraud (where a criminal tricks someone into sending money to the wrong account) — the new liability framework ensures that all parties involved share responsibility for detection and resolution, not just you and your bank.

The practical benefit is reduced fraud-related operational overhead. Under PSD2, property managers receiving a fraudulent payment could face account freezes, extended investigation periods, and uncertain timelines. PSD3's clearer liability distribution should accelerate resolution.

PSD3 also introduces more flexible Strong Customer Authentication rules, allowing risk-adaptive authentication. Low-risk, recurring payments between established parties (like a tenant paying rent to the same account for the 12th consecutive month) may qualify for simplified authentication, reducing friction without compromising security.

What to do now: Ensure your payment provider has a clear PSD3 compliance roadmap. The transition period runs through 2027-2028, but providers that start adapting now will offer the smoothest experience for your tenants.

The Timeline — What Happens When

The key dates:

Publication of PSD3/PSR final text: expected mid-2026. Entry into force: 20 days after publication. PSR (the directly applicable regulation) takes effect 18 months after entry — approximately late 2027. PSD3 (the directive requiring member state transposition) takes effect 18 months after entry, with member states given that period to transpose into national law.

The compliance gap is significant: as of February 2026, 61% of EU payment institutions and 54% of traditional banks had not completed PSD3 compliance programs. This means the transition will likely be uneven — some banks will be ready on time, others won't.

For real estate companies, the practical guidance is: don't wait for PSD3 to adopt open banking. The core benefits — lower costs, instant settlement, no chargebacks — are available today under PSD2. PSD3 makes open banking better (more reliable APIs, VoP, VRP), but the business case already exists.

The cost of waiting is concrete. Every month between now and PSD3 implementation is another month of card fees or direct debit chargebacks that open banking would have eliminated. If you manage 500 units and switch from card to open banking today, you save roughly €140,000/year in processing costs — and by the time PSD3 arrives in late 2027, you'll have already saved over €200,000 compared to waiting. Companies that adopt now will be positioned to take advantage of PSD3 enhancements automatically as their payment providers upgrade.

For a comprehensive overview of how open banking works for property payments today, read our Complete Guide to Open Banking for Real Estate.

UrbanPay is a payments middleware company for real estate, headquartered in Madrid. We connect real estate companies to Open Banking, card processing, escrow accounts, and mass disbursement rails across 19+ European markets. Founded in 2025 as a joint venture between elsa.care (payments technology) and UrbanPath Group (real estate management).

Related Articles