Telehealth in the UAE is licensed and mainstream — the DHA, DoH and MOHAP all run telemedicine frameworks, and remote consultation is a normal part of the health system. Payments, however, have not entirely caught up. Acquirers group telehealth with a set of categories they have historically lost money on, and they draw a hard line between a licensed consultation platform and anything that looks like online prescription fulfilment.
That distinction is the whole conversation. A DHA-licensed platform connecting patients to registered practitioners is underwritten very differently from a service that dispenses medication, and a platform doing both needs to explain the split clearly at application. Providers also ask how payment data sits alongside patient data, because a payment flow that touches clinical records raises questions no acquirer wants to answer for you. Below we compare processors working with licensed UAE telehealth and pharmacy merchants.
What Telehealth processors look for
Underwriting for this category is documentation-led. Having these ready before you apply is the single biggest lever on both approval odds and how fast you get a decision.
- A DHA, DoH or MOHAP licence covering telemedicine, and practitioner registration for every clinician
- A clear statement of whether you consult, prescribe, dispense, or some combination
- Separation of payment data from clinical records, with the architecture documented
- Patient consent and privacy documentation aligned with UAE data protection law
- Pharmacy partner details and dispensing arrangements where medication is fulfilled
- Subscription care-plan terms with a visible cancellation route, if you bill recurring
Frequently asked questions
Payment card data and patient data sit under different regimes, and the practical approach is to keep them separate rather than making your payment stack a clinical records system. Card data belongs in the PCI DSS compliant path; clinical data belongs in your health records environment, linked by a reference rather than merged. Underwriters ask about this because a design that mixes them creates exposure on both sides.
No, and the distinction matters more than merchants expect. Consultation platforms are underwritten as licensed professional services. Prescription fulfilment is underwritten as pharmacy, with tighter scrutiny. Say clearly which one you are on the application — a vague description gets a cautious answer.
For a UAE-facing telemedicine service, expect the licence to be a precondition rather than a nice-to-have. Which authority applies depends on the emirate and the activity. Acquirers verify it because their own regulatory relationship depends on your permission to operate.
Yes, and most care platforms do. Recurring billing brings the same underwriting questions as any subscription model: clear disclosure at signup, a recognisable descriptor, and genuinely self-service cancellation. Get those right and the recurring element is rarely the obstacle.
Keep card data inside the PCI DSS compliant payment path and clinical data inside your records environment, joined by an opaque reference rather than a shared record. Avoid putting any clinical detail into payment descriptors, metadata or receipts. This is an architecture question worth settling before you integrate, not after.