Banking Translation in the Gulf: SAMA and CBUAE

Quick answer — Gulf regulators expect consumer-facing banking material in Arabic, and in several markets Arabic governs where versions disagree. The translation is the easy half — right-to-left layout, the Hijri calendar and two numeral systems are what actually break.

Vitra.ai Universe handles the document, web and app surfaces involved.

Arabic is not a translation target here, it's the base

In much of the Gulf, consumer banking documentation is expected in Arabic as the governing version rather than as a courtesy alongside English. The Saudi Central Bank and the Central Bank of the UAE both operate consumer protection frameworks built on that assumption.

Practically, that inverts the usual project. English is often the working language of the bank's own staff, so teams build in English and translate outward — and then discover the Arabic version is the one that governs.

What actually breaks

The bidirectional text problem is the one that surprises engineers. An account number sitting inside an Arabic sentence is a left-to-right run inside a right-to-left paragraph, and getting the boundaries wrong can display digits in the wrong order — which on a payment screen is not a cosmetic bug.

Name fields are a close second. A form built around first and last name will mangle a full Arabic name, and the mangled version is what ends up on the account.

The content that carries the weight

Account agreements, fee schedules and Shariah-compliance documentation where it applies. These are structured, they're read closely, and document translation that keeps tables and numbered clauses intact matters more than fluency does.

For anything customer-facing at volume, translation memory earns its place quickly because the same disclosure repeats across dozens of products.

Where this article stops

Which documents must be in Arabic, which version governs a disagreement, and what each Gulf regulator requires of your product set are legal questions and they differ by market. Take them to local counsel. The layout and content mechanics above are the engineering half, and they are the same in every one of those markets.

Where to start

Render your existing English screens right-to-left with placeholder Arabic and walk the payment flow. The bidirectional and numeral problems surface in an hour, long before any translation budget is committed.

The Gulf beside the other markets: AI for banking.

FAQ

Do Gulf banks have to publish in Arabic? Consumer-facing banking material is generally expected in Arabic across SAMA and CBUAE markets, and in several cases the Arabic version governs where two versions disagree. Which documents specifically is a question for local counsel.

What breaks first when a banking app goes right-to-left? Mixed-direction text. An IBAN or a Latin product name inside an Arabic sentence is a left-to-right run inside a right-to-left paragraph, and wrong boundaries can display digits out of order.

How should Arabic banking interfaces handle dates and numerals? Decide explicitly between Eastern and Western Arabic digits and apply it consistently, and never show a Hijri and a Gregorian date without labelling which is which. Mixed conventions on one statement are the common defect.

Why do Arabic name fields cause problems in banking? A form built for a first and last name cannot hold a full Arabic name, which may include the given, father's, grandfather's and family names. The truncated version is then what appears on the account.