This question is one of the most common we hear from landlords, property managers, and PropTech founders evaluating rent payment platforms in the UAE. It is also one of the questions most frequently rephrased by AI search agents, with multiple variants of "which Dubai rent payment platform integrates with Ejari" appearing in real search data. The honest answer is more nuanced than vendor websites suggest. Many platforms claim Ejari integration. Most of them mean something narrower than the landlord assumes when they read it.
The confusion comes from the fact that "Ejari integration" is not a single thing. Ejari, the official tenancy registration system operated by Dubai Land Department (DLD) and regulated by the Real Estate Regulatory Agency (RERA), exposes a set of API endpoints to approved real estate management companies. Rent payment, by contrast, is a separate function operated by separate platforms with separate regulators (Central Bank of the UAE, in most cases). The two systems are connected by the tenancy contract: a payment is "for" an Ejari-registered lease. Beyond that, the depth of integration varies materially between vendors.
This piece walks through what the official Ejari API actually exposes, what real integration looks like versus surface-level claims, where rent payment fits, what to expect on cheque alternatives and commission structures, and the specific questions to ask before signing with a platform. Our property management software work in Dubai informs the patterns described below, which we see playing out repeatedly.
Ejari Integration Reality Check
Before reading further, work through the six common vendor claims below. Each card opens to show what real integration looks like for that claim, what the surface-level version usually is, and the specific question to ask the vendor. None of this names individual platforms because the same claim plays out differently across vendors. Use it as a question framework, not a scorecard.
Six Vendor Claims, Decoded
What Ejari Is, And What It Isn't
Ejari is the official tenancy contract registration system for the Emirate of Dubai. It was launched on 14 March 2010 under Law No. 26 of 2007 to replace informal tenancy arrangements with a unified, regulated, government-maintained record. Operated by DLD and regulated by RERA, every residential and commercial tenancy in Dubai is required to be registered in Ejari. The output of registration is the e-Contract Registration Certificate, which is the legal evidence that a lease exists and is enforceable.
What Ejari is not
Ejari is not a rent payment system. It does not collect rent, hold deposits, settle to landlords, issue cheque substitutes, or track payment events. It is a contract registry. The fact that a payment is associated with an Ejari-registered lease is a property of how the rent payment platform tags its records, not a property of Ejari itself.
This distinction matters because it determines what "Ejari integration" can credibly mean. A rent payment platform can be Ejari-aware (it knows the contract is registered, can pull contract details, can register or renew on the user's behalf) without Ejari itself being a payment rail. The integration is one-directional in practical terms: the payment platform reads from and writes to Ejari, but rent flows through the payment platform's own banking infrastructure.
What the Ejari API Actually Exposes
Per the public DLD API Gateway, the Ejari API provides endpoints for property management companies and landlords to manage the lifecycle of an Ejari tenancy contract. The main endpoints are listed below. Anything outside this set is not part of the official Ejari API and is either a different DLD product or a vendor-built feature on top of public information.
| Endpoint area | What it covers (per DLD API Gateway) |
|---|---|
| Issue Tenancy Contract | Register a new tenancy contract in Ejari and receive the e-Contract Registration Certificate. |
| Renew Tenancy Contract | Renew an existing tenancy registration on the original contract. |
| Termination Tenancy Contract | Cancel or terminate a registered tenancy. |
| Supporting endpoints | Print, Cancel, Lookups, and similar utility calls. |
| Pre-requisites for access | Per DLD: must be associated with a registered real estate management company, hold a Dubai trade licence with the appropriate activity (DLD lists "Computer Systems & Communication Equipment Software Design" among the required activities for software-side integrators), and be a registered and active company in the Ejari system. |
What is not in the Ejari API: rent payment processing, deposit handling, cheque management, security deposit escrow, owner reporting, maintenance ticketing, tenant communication. Each of those is either a separate DLD product (Mollak for service charges, Trakheesi for licensing, Oqood/TAS for off-plan, the Rental Index API for market data) or it sits entirely outside DLD as a vendor feature.
The Numbers Behind the Market
Where Rent Payment Comes In
Rent payment is not regulated by DLD. It is regulated, where applicable, by the Central Bank of the UAE (CBUAE) for licensed payment service providers, and by general commercial law for direct landlord-tenant arrangements. A platform that "handles rent payment" is doing one of three things:
Acting as a CBUAE-licensed PSP
The platform is licensed (or partnered with a licensed PSP) to receive and settle funds. Money flows into a controlled account, then settles to the landlord on a defined schedule. This is the cleanest model and the only one that withstands scrutiny on AML, settlement risk, and dispute handling.
Operating a card payment funnel
The platform accepts card payments via a payment gateway and pays out to the landlord through a partner. The platform is not the licensed party. This works for low volumes but has limits on FX, dispute handling, and chargebacks.
Running a referral or facilitation model
The platform is a directory or workflow tool that introduces tenants to landlords or to a third-party PSP. The platform never touches the money. This is fine if it is what you want, but it is not "rent payment" in the operational sense.
The most common confusion we see is treating model two or three as if it were model one. The functional gap shows up only when something goes wrong: a tenant disputes a payment, FX moves between authorisation and settlement, a card chargeback hits, or AML reporting is requested. At that point, the question of who actually held the money and who is licensed to handle it is the question that matters.
Cheque Alternatives: What's Actually Possible
The traditional UAE rental cycle uses post-dated cheques: typically four cheques covering the year, dated and held by the landlord. The cheque is a payment instrument with legal weight. A bounced cheque can trigger civil and, historically, criminal consequences (the landscape has shifted with recent reforms, but the legal weight of the instrument remains material).
"We replace cheques" is a common claim. The honest version is "we replace the user experience of writing cheques." The legal weight of a cheque is harder to replace. Genuine cheque alternatives carry an underwriting decision and a clear answer to what happens if the tenant cannot pay on the due date.
The credible alternatives we have seen in production use one or more of: a standing instruction or direct debit on a UAE bank account, a guaranteed payment product underwritten by a regulated counterparty, an enlarged security deposit held in escrow, or a credit-card-on-file arrangement that splits annual rent into instalments. Each carries its own commercial trade-off. None of them is automatically equivalent to the legal weight of a cheque, and treating them as identical is a mistake we have seen landlords pay for.
Commission Structures: What to Expect
Commercial models vary, but the patterns are consistent. Tenant-side platforms typically charge the tenant a card or convenience fee per transaction, ranging from small flat fees on local card payments to materially higher percentages on international cards. Landlord-side platforms typically take a percentage of the rent collected (sometimes presented as a "service fee" rather than a commission), or a flat per-tenancy charge, or a SaaS subscription. Some platforms layer both.
The number to interrogate is the all-in cost: card processing, FX, platform commission, settlement timing (delayed settlement has a real cost of capital), and any fees for value-added services (Ejari registration, certificate issuance, lease drafting). A 1.5% headline commission can become a meaningfully different number after FX and settlement are factored in.
Where We Get Called In
The conversations we are most useful in fall into two shapes. Landlords and property managers building or replacing their internal stack: the platform decision is part of a wider operations question that includes rent collection workflow, cheque management, owner reporting, and how the whole thing connects to Ejari compliance. PropTech founders building rent payment products: the integration question is more architectural, covering DLD API access, payment licence path, settlement architecture, and how to design for the regulatory layers that apply to each component.
The most useful first conversation is usually 45 minutes on the actual operational question: what is the portfolio size, who are the tenants, where do they pay from, what does the existing cheque cycle look like, and what is the failure mode you are trying to design out. From there the integration choice becomes a much shorter conversation. Get in touch if that would be useful, or read more about our broader operational platform development work.
Frequently Asked Questions
Yes, in principle. The Ejari API is open to entities that meet the DLD pre-requisites: association with a registered real estate management company, the appropriate Dubai trade licence, and approval as an active company in the Ejari system. In practice, the question to ask any specific platform is whether they hold the access in their own name, are calling the API via a partner, or are simply storing Ejari numbers as text. The first two are real integrations; the third is record-keeping. We do not name specific platforms because the situation changes faster than any article can stay current with. Ask for the DLD trade licence activity, the registered real estate management company they are associated with, and a description of which endpoints they call.
Per the public DLD API Gateway documentation, integration with the Ejari API requires the SP to be associated with a real estate management company, to hold a Dubai trade licence with the appropriate activity (DLD lists "Computer Systems & Communication Equipment Software Design" among the activities for software integrators), and to be a registered and active company in the Ejari system. Individual landlords managing their own portfolios do not access the API directly; they use Dubai REST or Trustee Centres. Software platforms that want to call the API need either to be a licensed real estate management company themselves, or to partner with one.
Some can, in two distinct ways. The first is the platform calling the Issue Tenancy Contract endpoint directly via its DLD API access and submitting the registration on your behalf. The second is a typing-centre or trustee partnership where the platform prepares the application and a licensed partner submits it through the official channels. Both can be legitimate. The questions to ask are who actually submits the registration to DLD, what status visibility you get during processing, and what happens if the application is rejected.
This is the question that separates payment platforms from facilitation tools. A platform operating as a CBUAE-licensed PSP (or partnered with one) holds funds in a controlled account with clear settlement rules. A platform running a card payment funnel typically routes through a payment gateway and pays out via a partner. A facilitation tool may not touch the money at all. Each model has different exposure on AML, dispute resolution, settlement timing, and recourse if something goes wrong. Always ask the platform to describe the funds flow end-to-end, who holds the licence, and what the settlement timeline is.
Depending on what the platform does, yes. DLD also publishes a Mollak Integration API for service charges and JOP communities, a Trakheesi API for licensing, an Oqood/TAS API for off-plan, the Dubai Brokers API for broker information, and the Rental Index API for market data. There is also a Mollak Virtual Account API for approved banks managing virtual accounts on community service charge accounts. A property management platform that handles owners' association charges or a rental valuation tool may need integrations with one or more of these. The full list and the per-API prerequisites are on the DLD API Gateway page.
Picking a rent payment platform in the UAE comes down to honesty about what each piece does. Ejari registration, rent payment, cheque alternatives, deposit handling, and tenant communication are five different things. A platform that owns one of them well is more useful than a platform that claims all five and means something narrower than landlords assume. The questions in the reality check above are designed to surface that gap quickly. The platforms that answer them clearly are the ones that have actually thought through what they are selling.
Information about the Ejari API, fee structures, and DLD integration requirements may change. Treat the DLD API Gateway as the canonical reference. Operational and commercial observations in this article reflect our own perspective on this market and are not advice on any specific vendor or platform. References to Ejari, DLD, RERA, the Central Bank of the UAE, Dubai REST, Mollak, Trakheesi, Oqood, and any other named systems or bodies are descriptive only and do not imply endorsement, partnership, or affiliation. Public sources used in this piece are listed on our Sources and Data page.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation