Payments and Escrow in Real Estate Platforms: Architecture, Compliance, and Fraud Prevention

Real estate transactions move more money than almost any other consumer context. An earnest money deposit on a median-priced home is $5,000 to $15,000 – wired or transferred in a single transaction, often under time pressure, by a buyer who has never done this before and whose primary concern is not missing the contract deadline. A commission disbursement at closing moves $15,000 to $30,000 to an agent who is watching for the confirmation. A capital call on a real estate syndication moves hundreds of thousands from investor accounts to a fund’s operating account on a defined timeline that has legal consequences if it slips.

Every one of these transactions is a moment where the platform either earns the user’s trust permanently or loses it in a way that’s hard to recover from. A payment that fails silently, a disbursement that takes three days longer than the user expected, a wire instruction that turns out to be fraudulent – these are not edge cases. They’re the failure modes that real estate payment infrastructure is specifically designed to prevent, and the design decisions that prevent them are the subject of this post.

Payment infrastructure in real estate platforms is also the area where the compliance obligations are most specific, most non-negotiable, and most consequentially violated. Trust account segregation requirements, earnest money deposit timing rules, RESPA escrow account compliance, and AML transaction monitoring all apply to different parts of the payment stack depending on what the platform does and in which states it operates. Getting these wrong is not just a software quality problem – it’s a licensing risk and a regulatory exposure that in serious cases affects the entire business.

The Payment Categories That Real Estate Platforms Handle

Before designing payment infrastructure, it’s worth mapping the distinct payment categories a real estate platform may handle – because each has different timing requirements, different compliance obligations, different fraud profiles, and different user experience expectations.

Earnest money deposits are the highest-anxiety payment in a residential transaction. The buyer is transferring a meaningful sum – typically 1–3% of the purchase price – into trust, often within 24 to 72 hours of offer acceptance, with the understanding that it’s at risk if they back out without a valid contingency. The platform needs to collect this deposit through a reliable, fraud-resistant channel, confirm receipt immediately to reduce buyer anxiety, and hold it in a properly segregated trust account until the transaction closes or terminates. Minnesota statute requires earnest money to be deposited within three business days of receipt or final acceptance of the purchase agreement. Oregon law requires immediate deposit into a clients’ trust account pursuant to written agreement of all parties. These timing rules vary by state and are actively enforced by real estate licensing boards.

Commission disbursements flow from closing to the brokerage and then to the agent, typically on the same day as close of escrow. The timing expectation has shifted significantly: agents who were accustomed to waiting two to three business days for ACH settlement are increasingly expecting same-day or next-day disbursement, driven by platforms that offer Same Day ACH, Real Time Payments, and FedNow for commission payouts. The platform’s commission disbursement infrastructure needs to handle the calculation – drawing from the commission engine that computes the agent’s net after split, team override, franchise royalty, and fees – and then execute the payment to the correct bank account with a confirmation record that ties back to the transaction.

Rent collection is the highest-volume, most recurring payment category in property management platforms. Unlike the one-time payments in a sales transaction, rent is processed monthly for every active lease – predictable in amount, predictable in timing, and problematic in its failure modes. A tenant who misses an autopay date, an ACH return for insufficient funds, a late fee that posts to the wrong period – each of these creates a reconciliation issue that compounds if the platform’s payment logic doesn’t handle it automatically and correctly.

Capital calls in investment platforms are the payment category with the highest individual transaction amounts and the most formal process requirements. A capital call notice must be sent to investors with sufficient lead time – typically ten business days per most operating agreements – must specify the exact amount per investor, must reference the operating agreement provision authorizing the call, and must provide clear instructions for how funds should be remitted. The platform needs to track which investors have confirmed receipt of the notice, which have funded, and which are approaching or past their funding deadline – because a capital call that closes with less than full funding has immediate implications for the investment’s ability to proceed.

Payment Rails: Choosing the Right Mechanism for Each Payment Type

The payment rail – the underlying network over which funds travel – determines the speed, cost, reversibility, and fraud profile of every transaction. In 2025, real estate platforms have more options than ever, and choosing the right rail for each payment category is an architectural decision that affects both user experience and operational cost meaningfully.

ACH remains the workhorse of real estate payments. Standard ACH settles in one to two business days, costs a fraction of a wire transfer, and is appropriate for the vast majority of real estate payment flows where same-day settlement isn’t required. Same Day ACH settles within hours on the same business day, which addresses the timing expectations of agents and buyers without the cost of a wire. Dwolla’s Same Day ACH implementation for one digital real estate payments platform produced 212% growth in new client contracts after launch – a data point that reflects how significant the timing improvement is to the user experience.

Real Time Payments (RTP) and FedNow are the newer rails that enable instant, irrevocable fund movement at any time – including weekends and holidays. RTP, operated by The Clearing House, processes transactions in seconds with immediate finality. FedNow, launched by the Federal Reserve in 2023, provides similar capability through a different network. Both are being adopted for commission disbursements and earnest money deposits because the instant, irrevocable nature of the transaction eliminates the settlement uncertainty that drives post-payment support calls. Modern Treasury’s infrastructure specifically targets title and escrow companies with FedNow and RTP integration, framing the cost structure as materially more economical than wire transfers while matching or exceeding their speed.

Wire transfers are still used for high-value transactions – closing disbursements, large capital calls, down payment funding – where the amount exceeds ACH limits or where the counterparty expects a wire. The compliance obligation for the platform here is less about the payment mechanism itself and more about the wire instruction delivery process, which is the primary attack surface for the wire fraud that has cost the real estate industry hundreds of millions of dollars annually. The FBI’s Internet Crime Report consistently ranks real estate wire fraud among the highest-loss categories of cybercrime. The platform’s role is to ensure wire instructions are communicated through an authenticated channel – never via email alone, never via a channel that an attacker who has compromised an email account can intercept and substitute. Encrypted, portal-authenticated wire instruction delivery – where the buyer confirms receipt and accuracy of wire instructions by logging into the platform – is the architecture that eliminates the primary fraud vector.

Trust Account Architecture: The Compliance Foundation

Trust accounting is the legal and operational foundation of real estate payment infrastructure for any platform that holds client funds – brokerages collecting earnest money, property management companies holding security deposits and rental proceeds, escrow companies managing closing funds. The requirements are statutory obligations enforced by state real estate licensing authorities, and violations result in license suspension, fines, and in serious cases, criminal prosecution.

The core trust accounting requirement in every US state is fund segregation: client funds held in trust must be maintained in a dedicated trust account completely separate from the company’s operating account. Commingling – depositing trust funds into an operating account, or depositing operating funds into a trust account – is a per se violation regardless of intent. The platform’s bank account architecture must enforce this separation at the infrastructure level.

The reconciliation requirement adds a second layer of obligation. The trust account balance must reconcile to the sum of all individual client ledger balances at all times – not approximately, not at month end, but at all times. If the trust account holds $847,293, the sum of all individual client balances must also equal exactly $847,293. A discrepancy of any amount triggers an immediate investigation, not a note to review next month.

The platform’s data model for trust accounting must record every transaction – receipt, disbursement, transfer – against both the trust account balance and the individual client ledger it belongs to, simultaneously and atomically. This is the architectural requirement that makes trust accounting harder than general ledger accounting: every transaction has two dimensions that must stay in sync. Using database transactions – where both postings succeed or both fail together, with no partial state – is the implementation requirement that prevents reconciliation failures under error conditions.

The Federal Reserve’s Consumer Compliance Outlook identified RESPA Regulation X escrow account violations as among the top-cited compliance violations in 2023. The most common failures: providing the escrow annual statement outside the required window, and failing to conduct surplus/deficiency analysis within 30 days of completing the escrow account computation year. Both of these are calendar and workflow management failures as much as technical ones – but the platform’s infrastructure needs to support the workflow that prevents them, including automated reminders, scheduled analyses, and documented completion records.

Earnest Money Deposit Flow: The Full Lifecycle

The earnest money deposit flow illustrates the full payment lifecycle a real estate platform needs to support – from collection through holding through disbursement – with compliance implications at every step.

Collection begins when the purchase agreement is accepted and the earnest money deadline is set. The platform should trigger a payment request automatically at acceptance – generating a unique transaction identifier tied to the specific property and purchase agreement, sending the buyer a notification through their preferred channel with a direct payment link, and confirming that the payment link is authenticated. The buyer must log into their portal to initiate the payment rather than following a link that could have been intercepted. Earnnest, which has positioned itself as the largest digital earnest money service in the US, has built its entire product around removing the email-and-check workflow from this step – and agent adoption at brokerages using it has been near-complete once agents experience a single transaction where the earnest money issue didn’t become a deadline problem.

Holding begins when funds are received and must immediately comply with the state’s deposit timing requirement. The platform should post the receipt to the client’s individual trust ledger in real time and trigger a confirmation to all parties – buyer, listing agent, buyer’s agent – with the receipt timestamp and transaction identifier. The trust account balance for this transaction should be visible to the buyer in their portal throughout the holding period.

Disbursement occurs at one of three outcomes: transaction closes, transaction terminates with mutual agreement, or transaction terminates with dispute. Each requires a specific authorization – a signed release from both parties or a court order in the dispute case – before the platform can process the disbursement. The authorization document should be collected through the platform’s e-signature workflow, stored against the transaction record, and linked to the disbursement event in the audit log. The disbursement itself should execute only after authorization is confirmed, using the appropriate rail for the recipient, with a confirmation record that closes the client ledger balance to zero.

Fraud Prevention: Wire Fraud, ACH Return Fraud, and Identity Verification

Real estate fraud has become one of the highest-loss cybercrime categories precisely because real estate transactions involve large, time-pressured fund movements between parties who may have limited familiarity with each other’s normal communication patterns.

Wire instruction substitution is the most financially damaging vector. The prevention is to remove email as the channel for communicating wire instructions entirely. Wire instructions should be generated by the platform, delivered exclusively through the authenticated portal, and confirmed by the recipient through a secondary verification step – a call to a verified phone number, an in-app confirmation code, or a biometric authentication event. Any wire instruction that arrives via email should be treated as potentially fraudulent by default.

ACH return fraud occurs when a payment is made from a bank account that either lacks sufficient funds or has been opened fraudulently. Standard ACH is reversible – an NSF or unauthorized return can claw back funds up to five business days after settlement, which creates exposure for platforms that release proceeds before the ACH has fully cleared. For high-risk payment categories – earnest money deposits, large security deposits – the platform should require micro-deposit bank account verification before the first ACH transaction, and hold collected funds for the ACH return window before treating them as fully settled.

Plaid’s identity verification and bank account connection API has become the standard for ACH fraud prevention in real estate platforms: it verifies the user’s ownership of the bank account they’re connecting, checks the account’s history for risk signals, and returns a confidence score the platform can use to determine whether to hold funds for the full return window or release them on an accelerated schedule for verified, low-risk accounts. Stripe Identity provides document verification for platforms that need to verify a user’s identity before they can initiate large payment transactions.

Rent Collection: Designing for Volume and Variance

Rent collection is the payment category where platform design has the most direct impact on property manager efficiency. At scale – 5,000 or 10,000 units – even a 2% payment failure rate means hundreds of manual follow-up workflows per month if the platform doesn’t handle failures automatically.

The autopay architecture that works at scale allows tenants to authorize automatic monthly ACH debits, with the debit scheduled for a configurable day relative to the rent due date. The platform sends a pre-debit notification three to five days before the scheduled debit, confirming the amount and giving the tenant an opportunity to flag any issues before the debit runs. On the debit date, the platform initiates the ACH, monitors the webhook for settlement confirmation or return, and branches accordingly: successful settlement posts to the tenant’s ledger and generates an automatic receipt; an NSF return triggers a retry queue, posts a returned payment event, and optionally applies a returned payment fee per the lease terms; an account-closed return flags the tenant for follow-up and suspends future autopay attempts.

Late fee logic is the payment calculation that most frequently surfaces data model problems. Late fees vary by lease – flat fee versus percentage of rent versus escalating per-day charges – and by state law. Many states cap late fee amounts or restrict when they can be applied relative to the due date. The late fee engine needs to read the fee terms from the individual lease record, check the applicable state cap and grace period rules, and apply the fee only when both conditions are met. Late fees applied incorrectly are not just operationally embarrassing – in states with strong tenant protection laws, they create legal exposure that compounds at portfolio scale.

Build vs Integrate: The Payment Infrastructure Decision

The payment category is where the build versus integrate decision is most clearly resolved in favor of integrating with specialized infrastructure. Payment processing at the low level – ACH network connectivity, card processing, fraud detection, bank account verification – requires regulatory relationships, compliance certifications, and operational infrastructure that no real estate software company should attempt to replicate internally.

The right architecture uses specialized payment infrastructure for the execution layer and builds the real estate-specific logic – trust account management, commission disbursement calculation, earnest money lifecycle tracking, rent collection with lease-specific late fee logic – on top of it. Stripe handles card processing and ACH origination for platforms that don’t require specialized real estate payment features. Dwolla handles high-volume ACH with the addenda records and webhook reliability that reconciliation requires. Modern Treasury provides FedNow and RTP integration for platforms where instant settlement is a product requirement. Plaid handles bank account verification and fraud signal enrichment.

The real estate-specific layer built on top of this infrastructure is where the actual product differentiation lives: the trust account ledger that maintains fund segregation and supports daily reconciliation, the earnest money lifecycle state machine that enforces authorization requirements for each disbursement event, the commission engine integration that drives disbursement amounts, the rent collection workflow that handles returns and late fees per lease terms. That layer is what a real estate software development team should be building. The payment rails beneath it are infrastructure that specialized providers have spent years making reliable and compliant.

Where Payment Infrastructure Projects Go Wrong

The most consistent failure is treating trust accounting as a reporting feature rather than a data model requirement. Teams build the payment collection and disbursement flows correctly and then add a trust account report that summarizes the transactions. The reconciliation problem surfaces the first time the report doesn’t balance – typically the first time the system encounters a failure case like a returned ACH or a partial disbursement – because the data model wasn’t designed to enforce the dual-entry constraint that trust accounting requires. Retrofitting a trust-accounting-compliant data model into a system built without it is one of the most expensive refactors a real estate platform can undertake.

The second failure is underspecifying the late fee engine before build. Late fee logic looks simple until the development team encounters the first lease with a percentage-based fee, the first state with a grace period that differs from the others, and the first tenant who made a partial payment that the platform needs to decide whether to treat as late or current for fee purposes. Each of these is a decision with legal implications that should be resolved in the specification phase. Discovering them in production, after late fees have been incorrectly applied to tenants, is the failure mode that generates the most consequential support and legal exposure.

The third failure is building ACH without planning for the return window. Teams launch rent collection, see the first month’s payments settle smoothly, and conclude the infrastructure is working. Three weeks later, the first batch of NSF returns arrives. If the platform released collected funds to the property owner’s disbursement account before the return window closed – a common mistake when the business logic treats settlement notification as equivalent to final funds – the platform is now holding a negative balance in the trust account. The reconciliation problem is both financial and regulatory. Designing the return window hold period into the disbursement logic from the start is the planning decision that prevents this failure entirely.

If you’re building payment infrastructure for a real estate platform – earnest money collection, commission disbursement, rent collection, or capital call management – and you need the trust accounting, fraud prevention, and compliance architecture to hold up under regulatory scrutiny and at operational scale, the real estate software development work we do starts with the payment flows and the data model that supports them, not the UI. We’ve built payment infrastructure for property management platforms, investment platforms, and brokerage systems operating across multiple states with distinct trust accounting requirements. Let’s talk through what your payment architecture actually needs to handle.