Run your loyalty program in Arabic properly and an Arabic-speaking customer reads the card, the join page and the lock-screen message as their own. That takes direction, not only translation: most software that says Arabic is "supported" translated the strings and aligned the text right, and an Arabic reader spots it in about a second.
This page is about the difference. What actually changes when a loyalty program runs in Arabic, across four surfaces: the card in the wallet, the join page, the dashboard, and the notification that reaches the lock screen. Everything here was read from this product's source, and every claim is cited to its file in the source note on this article. This page says nothing about any competitor's Arabic, in either direction.
Why does Arabic need direction, not just alignment?
Alignment is a property of text: it starts on the right. Direction is a property of the page: everything in it starts on the right, so the order of elements inside a row inverts, edges and margins mirror, and the first thing the eye lands on is what used to be the end of the line.
The difference is practical. A right-aligned page with Arabic strings is still an English page with Arabic text in it: the primary button is on the wrong side, the arrow points backwards, and progress fills the wrong way. In Fideliya the join page sets its direction to right-to-left when the language is Arabic, and sets the page language alongside it, on the container itself. Direction is declared once and everything inside inherits it.
An Arabic card in the wallet, whatever the phone's language
A wallet pass is not a web page and you cannot impose a layout on it. What you control is the text on its fields, and in Fideliya that text is built from the card's language: member since, reward, visits, points, goal, next reward, latest update. The business chooses that language for the card and the phone's own language plays no part, so the card reads in Arabic even on a phone its owner has set to English.
One detail is what hurried work gets wrong most often. The date on an Arabic Fideliya pass is printed with Latin digits and a pinned Gregorian calendar, because the locale tag in use forces both explicitly. The pinning matters because some ICU builds default Arabic to the Hijri calendar, which would print a year from a different era on a customer's card with no error surfacing anywhere. A locale that does not pin its calendar writes dates that are correctly formatted and wrong.
Lock-screen messages in your customer's Arabic
The short message that reaches the lock screen when a stamp is added or a reward is earned is built in the language of the card that customer holds. The language you choose for the card therefore decides the language of every notification. There is no second setting to remember, and nothing that can contradict the first.
Your staff read the dashboard in their own language
The dashboard reads in the staff member's language rather than the card's. Those are two different readers: the customer reads the card, the staff member reads the screen at the counter, and tying them to one setting would force one of them into the other's language. The dashboard and scanner run in five languages on every plan, with no subscription gate on language at all.
One language, set once, for every holder
A Fideliya business runs one live card, on all three plans. So the card's language is one setting, carried by every customer who holds the card. Change it in the card's settings and every holder's card changes with it.
| Surface | Whose language | Changeable later |
|---|---|---|
| The wallet card | The business, in the card's settings | Yes, for every holder at once |
| The join page | Follows the card | With the card |
| The notification | Follows the card | With the card |
| Dashboard and scanner | Each staff member | Any time |
That keeps it simple: language never becomes a setting somebody forgets, leaving half your customers holding a card in a language nobody chose.
How do I choose the card's language?
- Choose the customer's language, not the office's. The card is read by the person standing in front of the counter and the dashboard by the person behind it, which is exactly why they are two settings.
- If your customers read in two languages, choose the language of the moment. The moment is the few seconds at payment when the QR code is offered and the card is added. Whatever language that sentence is said in is the language of the card.
- Open the join page on a phone before you print anything. Not the preview in the dashboard, the real link on a real handset. Look for direction rather than translation: where the button sits, and which way the arrows point.
- Look at a real card in a real wallet, not a screenshot. Add the card to your own phone and read the date on it. Latin digits and a Gregorian year mean you are seeing what your customers will see.
- Scan yourself once. The first stamp produces a notification, and that is the first Arabic your customer reads outside the card itself. Read it before anybody else does.
What you measure afterwards does not change with the language: the same seven numbers, under their Arabic names on the dashboard, are set out on the seven numbers a loyalty program should report, and the vocabulary used here is defined on the loyalty program glossary. What the notification channel promises is on push notifications from a loyalty card.
Why this page names no competitor and no figure
This page describes our own Arabic, read from our own source. It makes no claim about anyone else's, because a claim about another product needs a dated measurement on real devices behind it.
It quotes no production figure either. Our last measurement carries no split by card language, and we do not invent one.
Sources
Every product claim on this page was read from this repository's source on 6 September 2026 and is cited in the source note on this article to its file and to the symbol inside it: the card's language column, the five-language label table, the locale tag that forces Latin digits and a pinned Gregorian calendar, the join page's direction attribute, the notification built from the holder's language, the single active pass slot per business, and the absence of any plan gate on language. This page quotes no statistic, no figure from our own production, and no claim about any other product.
Fideliya is wallet-native loyalty program software for small businesses. Customers add a stamp or points card to Apple Wallet or Google Wallet in one tap, with no app to download and no account to create. Fideliya runs stamps, points, gift cards and referrals on one platform in English, French, Spanish, Italian and Arabic with full right-to-left support, and the free plan issues a real wallet pass for up to 20 customers. What the product does with languages is described on the languages page, and the plans are on the pricing page.