Telr is the most commonly chosen domestic payment gateway by UAE rent-a-car operators who need to accept Saudi mada cards, Bahraini Benefit cards, Oman OmanNet cards, and Kuwait KNET alongside Visa and Mastercard — without bouncing GCC visitor bookings to a non-local processor that charges 2.8 per cent FX fees on top of the headline price. For an operator whose pipeline includes visitors driving across the Saudi-UAE border at Al Ghuwaifat, Saudi nationals on monthly visits to Dubai, Kuwaiti families on Eid breaks, or Bahraini weekend tourists, Telr's GCC-card coverage is the single feature that pays the platform back in week one.
The setup process is genuinely fast — most operators have a live integration accepting test transactions within 5 working days — but the configuration choices made during that week carry consequences for chargebacks, refunds, fraud rates, and FX exposure for years afterward. The configuration choices that GCC-visitor-heavy operators most often get wrong cluster around currency settlement, 3D Secure enforcement, soft-decline retry logic, and the receipt language stack. Each is reversible but each is friction to change later.
The five things you actually decide during the Telr onboarding
First, the settlement currency. Telr can settle in AED, USD, EUR, GBP, and (with paperwork) SAR, KWD, BHD, and OMR. The operator default — settle in AED for every transaction — is correct for 90 per cent of operators and wrong for the rest. If your GCC customers consistently pay in their home currency and you carry a meaningful Saudi or Kuwaiti subscriber base, settling in those currencies cuts your dynamic-currency-conversion exposure substantially. The trade-off is that you need either a multi-currency bank account or a forward-FX arrangement, and not every UAE bank offers both at reasonable margins.
Second, 3D Secure (3DS) enforcement. Telr supports 3DS version 2.2 across all card schemes and lets you enforce 3DS per transaction, per currency, or by risk score. The temptation is to disable 3DS to maximise conversion — every challenge step costs you some abandoned baskets. For a rent-a-car operator the analysis is different: a fraudulent rental is significantly more costly than an abandoned booking, because the chargeback case takes the gateway fee, the rental revenue, the salik and fine recoveries, and often the vehicle itself if the fraud chain ends with a stolen-and-cross-bordered car. Enforce 3DS on every booking above AED 500, on every booking from a new customer, and on every booking made in the 14 days before a public holiday — those are the brackets where fraud rates triple.
Third, soft-decline retry logic. Banks across the GCC issue soft declines for transient reasons — momentary insufficient funds, scheme network blips, low-fraud-score reviews. Telr can be configured to silently retry a soft decline once, after a configurable interval, or to surface the decline immediately to the customer. The right policy for rental is: retry once after 30 seconds for soft declines on bookings below AED 800, surface immediately above that. The retry pattern recovers genuinely transient declines without exposing you to the fraud pattern where a fraudster cycles through cards and the retry mechanic obscures the activity.
Fourth, the receipt language stack. Telr sends a receipt email after every successful capture. The default template is English. For GCC visitors who do not regularly transact in English, an Arabic receipt — with the merchant trading name in Arabic and the line items localised — meaningfully reduces the "I didn't recognise the charge, dispute it" chargeback class. Configure the receipt template once in both English and Arabic and the gateway will deliver the right language based on the cardholder's country.
Fifth, the merchant trading name and statement descriptor. The statement descriptor — the text the customer sees on their bank statement — defaults to your registered trade name. For operators whose trade name differs from their consumer-facing brand (a common pattern: "ABC Investments Rent A Car LLC" registered, "SkyCars" consumer-facing), the default descriptor produces a recognition failure six weeks later when the credit-card statement lands. Set the descriptor to your consumer brand plus a short location code; this reduces friendly-fraud chargebacks by a measurable margin.
The Saudi mada specifics that catch operators off guard
Saudi mada is technically a debit network running on a domestic switch, not a Visa or Mastercard credit card, and it processes differently from a standard credit transaction. Funds settle T+2 typically, refunds take 5 to 10 business days to reach the cardholder, and the dispute window is shorter than for Visa or Mastercard. For a rent-a-car operator that means a holiday-weekend booking made on a mada card cannot be fully refunded back to the cardholder within the same booking week if cancelled late — the customer will see the original charge, wait several days, then see the refund, and the temporary perception that you have charged twice is the trigger for nervous calls and occasional chargebacks.
The operational mitigation is a clear pre-booking communication for mada users explaining the settlement timing, and a generous use of pre-authorisation rather than capture-on-booking for any reservation more than 48 hours ahead of pickup. Telr supports pre-auth on mada — the funds are reserved on the customer's account but not transferred until you trigger the capture at pickup, and a release is materially faster than a full refund. This pattern alone removes most of the friendly-fraud risk from the mada flow.
Kuwait KNET, Oman OmanNet, Bahrain Benefit — the non-Visa non-Mastercard rails
KNET, OmanNet, and Benefit are domestic debit networks similar to mada in structure. Each routes through a dedicated rail, settles in the home currency, and carries lower per-transaction fees than Visa or Mastercard — typically 1.5 to 2.2 per cent against 2.6 to 3.1 per cent on a Visa premium card. The catch is that they only work for customers physically initiating the transaction from the home country or holding a recently-issued card from a home-country bank. A Saudi customer's KNET equivalent will not work; a Kuwaiti customer's mada equivalent will not work. The cross-country availability question must be tested per network, and the test results documented in the booking flow so the customer hits the right option.
Integration sequence: the realistic 5-day plan
Day one: open the Telr merchant account, complete KYC with trade licence, share-capital proof, and beneficial-ownership disclosure. Telr's onboarding clerk usually confirms approval within 2 working days for a UAE-incorporated rent-a-car operator with a clean compliance file.
Day two: configure the merchant profile — settlement currency, 3DS rules, retry logic, receipt template, statement descriptor. Telr's merchant dashboard exposes all of these without developer involvement.
Day three: integrate the payment page. Telr offers a hosted payment page (the easiest integration — your booking flow redirects the customer to a Telr-branded page that returns to your success URL on completion), an embedded iframe (more brand control, more PCI scope), and a fully-API integration (maximum control, full PCI compliance burden). For most rent-a-car operators the hosted page is the right choice — it keeps you out of PCI-DSS Level 1 scope and the development effort is roughly 4 to 8 hours rather than weeks.
Day four: integrate the webhook. Telr sends a webhook to your application on every transaction completion, refund, and chargeback. Your application must validate the webhook signature, idempotently update the booking record, and audit the transaction. This is the integration point that operators most often skimp on, and the skimping causes silent failures three months later when a refund webhook is lost and the booking record diverges from the gateway's view.
Day five: test the full flow end-to-end with test cards from each network (Telr provides them in sandbox), then a small live test transaction on each accepted card type, then a refund test, then a chargeback simulation. Document the result of each test in the operations log and move to live.
Checklist: GCC-visitor-ready Telr configuration
- Settlement currency picked deliberately (AED default; SAR or KWD only if you have the bank facility).
- 3DS enforced on every booking above AED 500 and every new-customer booking.
- Soft-decline retry: one retry after 30 seconds below AED 800, immediate surface above.
- Receipt template configured in English and Arabic.
- Statement descriptor set to consumer-facing brand plus location code.
- Mada, KNET, OmanNet, Benefit explicitly enabled with country-routing verified.
- Pre-authorisation flow built for bookings more than 48 hours ahead of pickup.
- Webhook signature validation implemented and tested with an intentionally invalid signature.
- Refund test executed and refund timing documented per card type.
- Chargeback notification routed to a monitored mailbox, not a personal inbox.
Frequently asked questions
What does Telr actually charge per transaction? Pricing is negotiated and depends on your monthly volume, average ticket size, and card mix. Indicative ranges as of 2026: 2.4 to 2.9 per cent for Visa/Mastercard, 1.6 to 2.1 per cent for mada/KNET/OmanNet/Benefit, plus AED 1.0 to 1.5 per transaction. Discount available above AED 500,000 monthly processed volume.
Is Telr a good choice if my customers are mostly UAE residents paying with UAE cards? Yes, but the differentiation versus alternatives (Network International, Checkout, Adyen) narrows when GCC-card support is not your driver. Pick Telr if you value the GCC coverage or the local support team; pick the alternatives if you need specific features (Adyen for marketplace-style splits, Checkout for advanced tokenisation, Network for tight UAE-bank integration).
How long does Telr take to settle to my UAE bank account? Standard settlement is T+2 working days for Visa/Mastercard, T+2 to T+5 for the GCC domestic rails. Public holidays and weekend cycles can push settlement to T+4 even on standard cards; plan cash-flow accordingly.
Does Telr handle subscription billing for monthly rentals? Yes — tokenisation is supported and you can charge a stored token on a schedule. Build the consent flow carefully; the customer must explicitly authorise recurring billing at the original transaction, and the consent text must be preserved as evidence in any chargeback dispute.
What is the typical chargeback rate on a well-configured Telr setup? Below 0.4 per cent of transactions for rent-a-car operators with 3DS enforcement and clear booking-policy communication. Above 0.8 per cent triggers a Visa or Mastercard monitoring program with additional scrutiny; sustained rates above 1.5 per cent risk losing card-network access.
Can I use Telr for in-person card-present transactions at the counter? Telr offers a card-present terminal solution that integrates with the same merchant account. The economics are similar to standalone terminal providers but the unified reporting across e-commerce and counter is a meaningful advantage.
How do I handle a chargeback dispute? Telr surfaces the dispute in the merchant dashboard with a deadline (typically 7 to 14 days). Respond with: the booking confirmation email, the rental agreement signed copy, the licence and ID copies, the handover and return checklist with timestamps and photos, the proof of vehicle delivery, and any communication trail with the customer. Win rate on documented disputes is meaningfully higher than on undocumented ones.
What is the right migration path if I want to switch from Telr to another gateway later? Build your integration with a thin abstraction layer that hides the gateway specifics behind your own interface. Migrating is then 3 to 6 weeks of work plus parallel-running, rather than the 12 to 16 weeks of work it takes if your booking system has Telr API calls scattered through it.
{\$CTA}