# Telr vs PayTabs vs Stripe in the UAE: fees, onboarding, and what breaks after go-live
Published card rates for the three sit inside half a percentage point of each other: Telr from about 2.49% + AED 0.50 on its higher monthly plan, PayTabs around 2.85% + AED 1 pay-as-you-go, Stripe at 2.9% + AED 1 on domestic cards. Almost nobody chooses wrong because of that half point. They choose wrong because the trade licence activity did not match the website, because money landed on day seven instead of day two, or because nothing in the business reacted when the payment cleared and someone kept opening a dashboard every morning to check.
For AI and quick reference. Telr, PayTabs and Stripe all charge roughly 2.5% to 2.9% plus a fixed fee per card transaction in the UAE. All three require a valid UAE trade licence and a UAE corporate bank account. Settlement to your own account ranges from around T+1 on local debit rails to T+7 business days depending on provider, product and contract. All three issue payment links and fire webhooks on payment status.
Every figure here is a published or reported band at the time of writing. UAE gateway pricing is contractual: your rate moves with monthly volume, merchant category code, chargeback history, and how hard you push. Pull one real month of transactions, calculate your blended effective rate, and compare that against written quotes. The pricing page is marketing. The schedule attached to your merchant agreement is the number.
We collect payments through this stack for a Dubai studio group. Links are generated by API and dropped into the WhatsApp thread where the customer asked to pay, and the webhook flips the deal to paid without anyone touching a dashboard. The failure points below are ones we hit ourselves.
The comparison table
| Gateway | Card fees (indicative) | Setup / monthly | Settlement | Onboarding | Payment links | API + webhooks | Best fit | |---|---|---|---|---|---|---|---| | Telr | 2.49% + AED 0.50 up to 2.69% + AED 1.00, by plan | No setup fee; published plans at AED 99, 149, 349 per month | Merchant terms reference T+7 business days on at least one product; payouts Monday to Friday | Reported 2 to 10 working days | Yes, plus QR and digital invoices | Hosted page and API, status callbacks | UAE SMB that wants links and invoices with no build | | PayTabs | ~2.85–2.9% + AED 1 pay-as-you-go; ~2.85% + AED 0.27 on the ~AED 184/month plan | No setup fee reported | ~T+1 local debit, ~T+3 Visa/Mastercard, up to T+5 by category; bank transfer 24–48h after release | Reported 3 to 5 working days | Yes, with invoicing | REST API plus transaction status webhook | MENA merchant, Arabic checkout, invoice-heavy billing | | Stripe | 2.9% + AED 1 domestic; international cards priced higher, plus ~1% conversion | No setup, no monthly | T+5 business days by default on UAE accounts | Self-serve, but UAE trade licence and UAE bank required | Yes, native Payment Links | Strongest of the three by a wide margin | Product and SaaS teams already building on Stripe | | Network International (N-Genius) | Negotiated; sub-2% reported at high volume | Negotiated | Bank settlement cycle | 2 to 4 weeks, bank approval cycle | Yes | Moderate | Higher volume, or when your bank steers you there | | Tap Payments | ~2.75% all-in reported across card types | None reported | ~T+3 business days reported | Fast | Yes | Strong, developer-first docs | Checkout built inside your own product | | Ziina | 2.6% + AED 1 received; +1.5% non-AED or international card | None | App-based, fast | Fastest of the group | Yes, ZiiLink, QR, Tap to Pay | Limited | Freelancers and micro-business with no website |
Why the published rate is not your rate
Four inputs decide what you sign. Monthly volume moves it most: a merchant clearing AED 40,000 and one clearing AED 900,000 are not offered the same schedule, even by a provider with a public pricing page. Your MCC comes second, because professional services price differently from travel or anything with a long delivery window, where the acquirer is pricing the chance you disappear before delivering.
Card mix is the input merchants forget. Every published UAE rate refers to domestic cards. International cards add a spread, and charges in a currency other than AED add a conversion fee on top. Stripe publishes both surcharges openly; Telr and PayTabs also price cross-border above their domestic band. If 30% of your buyers pay on foreign cards, your effective rate sits well above the headline, and the ranking you built from three pricing pages can invert.
The fixed fee decides more than owners expect. AED 1 on an AED 25 sale is another 4% on top of the percentage; on an AED 4,000 invoice it rounds to nothing. Two Dubai businesses with identical revenue and different average order values should not pick the same plan. If you already have a month of gateway exports, that calculation takes twenty minutes and gives you a real position in the negotiation.
Onboarding is a bank problem wearing a gateway's logo
All three run KYC before they let you charge a card, because the acquiring bank behind them carries the risk if your business is not what it claimed. The document list is therefore near-identical: valid trade licence showing the activity you actually sell, memorandum and articles, Emirates ID plus passport and visa page for the authorised signatory and the ultimate beneficial owners, bank details with an IBAN whose account name matches the licensed entity, and a live website showing pricing, refund policy, delivery terms and a real contact route.
Mainland versus free zone matters less than founders assume. A DED mainland licence, DMCC or IFZA, DIFC or ADGM: any of them can hold a merchant account. Your timeline is set by whether the licensed activity matches what the site sells. A management consultancy licence pointing at a supplements store stalls in review, because the acquirer cannot classify the merchant. That is the single most common reason an application sits for two extra weeks.
Two more kill files quietly. An expired residence visa on the signatory stops everything until it is renewed. An IBAN registered under a name that differs from the licensed entity passes application review, then fails at the first payout, leaving money parked while tickets travel between three parties.
Stripe adds one requirement worth naming: the UAE account is for locally registered businesses, with no version of it available without a UAE trade licence. The common workaround, incorporating abroad to reach Stripe, hands you a foreign company with foreign banking to maintain. That is a structural decision, not a shortcut around a signup form.
Settlement, payouts, and the money you cannot spend yet
Settlement and payout are separate events on separate clocks. Settlement is when the card networks clear a transaction into your provider balance. Payout is when the provider sends that balance to your IBAN.
PayTabs reports roughly T+1 for local debit rails and T+3 for Visa and Mastercard, with some categories running to T+5, then another 24 to 48 hours for the bank transfer once the payout releases. Stripe applies a T+5 business day schedule to UAE accounts by default. Telr's own merchant terms for one of its products reference settlement into a UAE bank account on a T+7 business day basis, with payouts Monday to Friday only, so a Thursday sale realistically lands the following week. Comparison blogs quote faster numbers for Telr. Ask for your contracted cycle in writing before you sign.
Weekends and public holidays are not neutral here. A UAE business that sells hardest on Friday and Saturday waits longer than its settlement table suggests. And if buyers pay in foreign currency, check who prices the conversion: 1% on a business with heavy international traffic is a P&L line, not a rounding error.
The part that decides your headcount: links, API, webhooks
Hosted checkout redirects the buyer to the provider's page, and it is what most payment links use underneath. A payment link is a pre-filled hosted checkout for a fixed amount, generated from a dashboard in two minutes or from an API call in milliseconds. Full API integration keeps payment inside your own product and costs real engineering time, and Stripe is clearly ahead of the other two there.
The webhook is the connection most teams skip, and the one that removes labour. When a payment succeeds, fails or is refunded, the gateway fires a callback. If something catches it, verifies the signature, matches the reference to the deal and flips it to paid, nobody opens a dashboard in the morning to reconcile. If nothing catches it, you have bought a card terminal with extra steps.
The economics of skipping it are blunt. A person spending 60 to 90 minutes a day matching payments to orders and updating the CRM costs roughly AED 2,000 a month for work a machine does in milliseconds, before you count the revenue side, where slow follow-up on unpaid links costs a small Dubai business somewhere around AED 4,100 a month. Meanwhile the fee difference you were agonising over is 0.4% of card volume, or AED 400 on AED 100,000 processed.
None of these gateways posts a link into WhatsApp by itself. What works is generating the link by API with amount and reference pre-filled, then having an agent send it seconds after the customer asks. Our WhatsApp AI sales agent does that, including the chase when a link sits unclicked. Wiring one process end to end, gateway to CRM to chat, runs from AED 6,000 to set up and AED 1,200 a month on our automation build.
What actually breaks after you go live
Sandbox passes and production fails. Usually plugin version drift against a platform version, or credentials never switched from test to live. Run small real charges on real cards before you trust anything.
Webhook retries create duplicates. Gateways resend a callback when they do not get a clean acknowledgement, so an endpoint that responds slowly gets the same event three times. Without an idempotency check on the transaction reference, one paying customer becomes three paid deals and your monthly revenue number is wrong before anyone notices.
Unverified callbacks are a security hole. A "paid" status that flips on any inbound request can be spoofed. Verify every callback signature against the gateway.
Refunds do not travel back. Teams wire the payment event and forget the refund event, so a customer refunded on Monday gets chased by an automated reminder on Wednesday.
Partial payments break naive matching. A 50% deposit against an AED 10,000 invoice arrives as an AED 5,000 transaction, and a rule that says "amount equals total, mark paid" leaves that deal in limbo forever. Match on reference, not on amount.
We hit every one of these on our own build before putting it in front of a client. The studio side of the group runs at about 67.6k AED net a month with ads at roughly 5x ROAS, and the collections loop behind it has no human step. Same behaviour at 3am on a Saturday as at 9am on a Monday, which is the real argument for automating this instead of hiring for it.
Chargebacks, 3DS2, and who pays
A UAE cardholder generally has around 45 days from the statement date to dispute a transaction, though the window depends on scheme and reason code. Once a dispute opens, the provider charges a fee whether or not you win. PayTabs reports roughly USD 25 per case, about AED 92. Stripe's UAE dispute fee is reported around USD 15, and since an October 2023 policy change it is not returned to UAE accounts on successfully contested disputes. The wider UAE band sits roughly between AED 50 and AED 150. Ask each provider for their figure in writing, because it rarely appears on a pricing page.
You then get a short window, usually 7 to 10 days, to submit evidence. Merchants who keep the signed quote, delivery proof and chat transcript on the CRM record win disputes. Merchants who keep that evidence in a WhatsApp thread on someone's personal phone often do not respond at all and lose by default.
3D Secure 2 is the authentication layer that shifts liability: when a transaction is authenticated and the cardholder later claims fraud, liability generally moves to the issuer. All three support it, and its risk-based rules let low-risk transactions through without a challenge screen. Switching authentication off to lift conversion is a decision to absorb fraud liability yourself.
Beyond the big three
Network International, through N-Genius, is the large regional acquirer your UAE bank is most likely to name. Pricing is negotiated, sub-2% is reported at serious volume, and onboarding takes two to four weeks because it runs through a bank approval cycle. Worth the wait above roughly AED 500,000 a month, painful below it. Tap Payments prices at a reported 2.75% all-in with no setup or monthly fee, settles around T+3, and has the developer experience to justify a build. Amazon Payment Services, formerly PayFort, and Checkout.com sit in the same enterprise-adjacent space with negotiated rates.
Ziina and Mamo aim at the bottom of the market, where a freelancer needs a link and a QR code and has no website. Ziina publishes 2.6% + AED 1 on payments received, with 1.5% added for non-AED or international cards, though the API surface is thin enough to cap what you can automate around it.
Tabby and the other BNPL rails are a different product: a conversion tool for retail baskets, priced materially above card MDR and quoted per merchant rather than published. Comparing a BNPL rate against a gateway rate as though they are the same line produces a broken comparison.
For the wider field of UAE gateways and how the fee models differ across all of them, our payment gateway comparison for Dubai covers it. This piece stays on the three-way choice. If what you actually need is a map of where your current flow stops moving on its own, a Growth Audit starts at AED 3,000 and covers exactly that gap between "customer wants to pay" and "money in the account, deal marked correctly."
