Localizing a Mobile App for Turkey: Language, Payments and Consent
Translating the interface is the easy part, and it is not where foreign apps lose Turkish users. The payment flow is. Instalment payment — taksit — is the default expectation for anything above a small amount in Turkey, and whether you can offer it is decided by the app stores rather than by your payment provider. Apple’s App Review Guidelines require in-app purchase for unlocking features, subscriptions, premium content and in-app currencies (section 3.1.1), while requiring the opposite for physical goods and services consumed outside the app, which “must use purchase methods other than in-app purchase” such as Apple Pay or traditional credit card entry (section 3.1.3(e)).
That single split decides your Turkish payment experience before any local decision is made. A subscription app runs on store billing and cannot present local instalment options inside the purchase flow; a delivery, booking or retail app takes payment itself and can. This article covers that constraint, the consent screens Turkish rules actually require, which messages fall under commercial electronic message rules and which do not, and the interface details that make Turkish strings break.
Table of Contents
- What in-app localization covers that ASO does not
- Payments: what the store rules let you do
- Consent screens and permissions
- Push and messaging: which rules apply
- Writing the Turkish interface
- Sign-up, identity and account deletion
- Forms, addresses and data entry
- Support and ratings inside the app
- Testing and release
- Common mistakes
- Frequently asked questions
What in-app localization covers that ASO does not
App store optimisation is about the listing: keywords, title, screenshots, ratings, the decision to download. In-app localisation is about everything after the download, and the two are usually owned by different teams with no handover between them.
| Layer | Covers | Decides |
|---|---|---|
| Store listing (ASO) | Keywords, title, screenshots, description, ratings | Whether they install |
| Interface language | Strings, dates, numbers, currency, pluralisation | Whether it feels built for them |
| Payment | Methods, instalments, store billing constraints | Whether they can complete a purchase |
| Consent and permissions | Privacy notice, explicit consent, push and location prompts | Whether you may process and message them |
| Account and support | Sign-up, verification, deletion, help in Turkish | Whether they stay |
The listing side is covered in our guide to app store optimization in Turkey, and the acquisition side in our guide to mobile app user acquisition in Turkey. This article is the four layers underneath them, where a well-marketed app loses the users it paid to acquire.
Payments: what the store rules let you do
Work out which side of the store payment rule your app falls on before designing anything, because it determines whether local payment expectations can be met at all.
Apple’s guidelines draw the line clearly. Section 3.1.1 requires in-app purchase where the app unlocks features or functionality — subscriptions, in-game currencies, game levels, premium content, unlocking a full version — and prohibits other mechanisms such as licence keys or codes for that purpose. Section 3.1.3(e) goes the other way for physical goods and services consumed outside the app: those payments “must use purchase methods other than in-app purchase,” such as Apple Pay or traditional credit card entry. Section 3.1.1(a) notes that outside the United States storefront, apps may not include buttons, external links or other calls to action directing customers to other purchasing mechanisms unless they hold an applicable entitlement.
What that means in a Turkish context:
- Digital products and subscriptions. The purchase runs through store billing, so the local instalment options Turkish buyers expect are not part of the flow. Price perception, trial design and plan structure carry the work instead — and pricing in lira with sensible tier steps matters more than it would in a market with a stable currency.
- Physical goods, delivery, bookings and services consumed outside the app. You take the payment, so the local checkout applies: Turkish cards, instalment presentation and the payment methods buyers recognise. Those choices are covered in our guide to payment methods and checkout localization for Turkey.
- Mixed apps. Many retail and service apps contain both, and the two flows have to look deliberate rather than inconsistent to the user.
Two further points worth settling early. Google Play operates its own billing and payment policies, and the current versions of both stores’ rules should be checked directly before you design the flow, because these policies change and regional entitlements differ. And wherever you do control the payment, show the total in lira with any instalment presentation visible before the user commits, rather than at the final step.
Consent screens and permissions
An app collects personal data from the first launch, and the consent pattern most foreign apps ship — one screen combining the privacy notice with a consent tick — is the construction Turkish practice treats as two separate acts.
In its decision numbered 2018/90 of 26 July 2018, the Personal Data Protection Board held that the obligation to inform and the taking of explicit consent must be carried out separately, and instructed the controller to separate the mechanism evidencing that the notice was read from the mechanism evidencing that consent was given. On a small screen the temptation to merge them is strong, and it is the merge that creates the problem.
Four design rules that follow:
Present the privacy notice as a notice. Readable in Turkish, on the device, before or at the point of collection — not as a link in a settings menu the user never opens.
Keep explicit consent separate and specific. Where consent is the basis you are relying on, it is its own affirmative action, unticked by default, and separate from accepting terms of use.
Do not bundle marketing permission with the account. An account creation flow that requires marketing consent to proceed is making consent the price of the service, which is the pattern Turkish enforcement has examined.
Treat the operating system permission as separate from the legal basis. A user tapping “Allow” on a push or location prompt has granted an OS permission. Whether you may process that data, and for what purpose, is a different question with a different record.
The surrounding framework is covered in our guide to KVKK compliance for foreign brands marketing in Turkey, and the same three-layer consent structure on the web in our guide to campaign landing pages for Turkey.
Push and messaging: which rules apply
Not every message your app sends is a commercial electronic message, and the distinction decides whether consent and registry obligations apply. Getting this wrong in either direction is costly: treating everything as marketing cripples your service communication, and treating marketing as service messaging creates exposure.
The Regulation on Commercial Communication and Commercial Electronic Messages defines a commercial electronic message in Article 4(1)(o) as data, audio and image content sent for commercial purposes in an electronic environment using channels such as telephone, call centres, fax, automatic dialling machines, smart voice recorder systems, electronic mail and short message service. In-app push notification is not named in that list, and the wording is illustrative rather than exhaustive — so whether a given push falls inside should be assessed rather than assumed in either direction. Where your app also sends SMS or email, those are squarely inside.
Article 6 sets out situations where prior consent is not required, and these matter more for an app than most teams realise:
- Article 6(1). Where the recipient provided their contact details to be reached, messages about changes, use and maintenance of the goods or services obtained do not need separate consent.
- Article 6(2). Messages concerning an ongoing subscription, membership or partnership, and collection, debt reminders and information updates, do not require consent — and may not promote or advertise goods or services.
- Article 6(3). Messages to recipients who are merchants or tradespeople (tacir veya esnaf) do not require prior consent, but once such a recipient exercises the right to refuse, consent must be obtained.
- Article 6(5). Messages sent under paragraphs 1, 2 and 4 are not checked against the İleti Yönetim Sistemi (İYS).
The practical design consequence is that your notification system needs a message type on every send — service or commercial — set at the template level rather than decided by whoever writes the copy. The moment a delivery update carries a discount code, it changes category. Where the follow-up moves to WhatsApp, that channel brings its own permission structure, covered in our guide to WhatsApp Business marketing in Turkey.
Confirm the classification of your own notification types with Turkish counsel rather than reasoning from the channel alone.
Writing the Turkish interface
Turkish breaks interface strings in ways that are invisible in an English build and obvious to a Turkish user.
Suffixes, not prepositions. Turkish attaches grammatical information as suffixes governed by vowel harmony, so the correct ending depends on the preceding word. A template that concatenates a fixed string onto a variable — a product name, a username, a city — will produce ungrammatical output for roughly half of the values it receives. The fix is not a better translation; it is avoiding templates that require the variable to inflect, or handling the inflection in code with proper rules.
Length. Turkish generally runs longer than English for the same content, and places the verb late. Buttons, tab labels and single-line notifications designed to English widths truncate.
The dotted and dotless i. Turkish distinguishes i/İ and ı/I, and case conversion is therefore locale-dependent: uppercasing “i” gives “İ” in Turkish and “I” in English. Any uppercase styling, search, sorting or string comparison that uses the wrong locale produces visibly wrong text or silently failed matches — a classic source of bugs in search and login flows.
Dates, numbers and currency. Turkish formatting uses a comma as the decimal separator and a dot for thousands, and the day-month-year order. A price rendered as 1,299.90 reads as a different number.
Register. Turkish distinguishes formal and informal address, and the choice has to be made once and applied consistently. Mixing them within one app is one of the clearest signals that strings were translated in batches by different people.
The equivalent discipline on the web side is covered in our guide to website localization for Turkey.
Sign-up, identity and account deletion
Three things in the account flow behave differently in Turkey.
Phone-first registration is normal. Many Turkish users expect to register with a mobile number and a verification code rather than an email address, and an email-only flow adds friction at the worst moment. Where you support both, make the phone route at least as prominent.
Identity fields need care. Asking for a national identity number at sign-up when the service does not require it adds friction and creates an obligation you did not need. Collect it only where there is a genuine requirement, and structure it properly where there is.
Account deletion is a store requirement, not just a legal nicety. Apple’s guidelines state that if an app supports account creation, it must also offer account deletion within the app (section 5.1.1(v)). That sits alongside data subject rights under Law No. 6698, which arrive in Turkish and are time-bound — so the deletion path needs to be in the app, in Turkish, and connected to a process that actually deletes rather than deactivates.
One operational point that catches foreign teams: deletion and data requests need a Turkish-speaking first line. A request routed directly to a global privacy inbox in English will be slower than the deadline it is subject to.
Forms, addresses and data entry
Every form in the app inherits the same structural mismatches that break web forms, with less screen to recover on.
- Names. Given name and family name, no middle name convention. Validation must accept ç, ğ, ı, İ, ö, ş and ü — a pattern that rejects a correctly spelled Turkish name loses the user silently.
- Addresses. Province, district, neighbourhood, then street and building, with the postal code playing a far smaller identifying role than in the United Kingdom or Germany. Province and district work best as pickers rather than free text.
- Phone. Accept the formats people actually type and normalise to the +90 international format behind the scenes.
- Keyboard and input type. The right keyboard for each field, and no autocapitalisation on fields where it corrupts the value.
Where the app’s forms feed a website or a web checkout, the same rules apply there, as covered in our guide to website performance and mobile experience for Turkish users.
Support and ratings inside the app
In-app support is a localisation surface that most foreign apps leave in English, and in Turkey it is also a reputation surface.
Help content in Turkish, written not translated. A help centre that reads as machine output undermines the app it is meant to support.
A support route that answers in Turkish, in the Turkish working day. An app that answers in English two days later generates store reviews about the support rather than the product.
Ask for the rating at a sensible moment. After a completed, successful action rather than on launch, and not immediately after an error.
Watch where complaints actually go. Turkish users escalate publicly, and complaint platforms carry real weight alongside store reviews, as covered in our guide to customer service localization and complaint platforms in Turkey.
Testing and release
Localisation defects are found by using the app as a Turkish user, not by reviewing a string file.
Test on a device set to Turkish. Language, region and keyboard, with a Turkish account and Turkish test data — not an English device with the app’s language switched.
Test the longest strings. Pseudo-localisation or a deliberately long test set catches truncation before a user does.
Test the payment flow end to end in both stores. Including the sandbox behaviour for store billing and the live behaviour for your own checkout, since they fail differently.
Test consent paths including refusal. The app has to work for a user who declines push, declines location and declines marketing consent. An app that degrades badly for that user is an app that will be uninstalled by them.
Keep release notes in Turkish. Small, visible, and frequently the only regular communication a user sees from the brand.
Medyae’s CRM and mobile application service covers Android and iOS development with the prototyping, UX and quality testing stages where these decisions are either designed in or discovered after launch.
Common mistakes
- Designing the payment flow before checking which store rule applies. Section 3.1.1 and section 3.1.3(e) point in opposite directions.
- Promising instalments in a subscription app. Store billing governs that purchase.
- One screen combining the privacy notice and consent. The Board’s 2018/90 decision treats them as separate acts.
- Requiring marketing consent to create an account. It makes consent the price of the service.
- Treating every push as marketing, or none of it. Article 6 sets out specific situations where consent is not required, and those messages may not promote.
- String templates that require Turkish suffixes. They produce ungrammatical output for half the values.
- Locale-blind uppercasing. The dotted and dotless i breaks display, search and matching.
- No in-app account deletion. Apple requires it where the app supports account creation.
- Email-only registration. Phone-first is the familiar pattern for many Turkish users.
- Testing in English with the language toggled. It hides truncation, formatting and keyboard defects.
Frequently asked questions
Can we offer instalment payments inside our app in Turkey?
It depends on what you are selling. Apple’s guidelines require in-app purchase for unlocking features, subscriptions, in-app currencies and premium content (section 3.1.1), so those purchases run on store billing and local instalment options are not part of the flow. For physical goods and services consumed outside the app, section 3.1.3(e) requires payment methods other than in-app purchase, so your own checkout applies and local instalment presentation is available. Check both stores’ current policies before designing the flow.
Do push notifications count as commercial electronic messages in Turkey?
The Regulation defines a commercial electronic message in Article 4(1)(o) by reference to channels such as telephone, call centres, fax, automatic dialling machines, smart voice recorder systems, electronic mail and short message service. In-app push is not named, and the list is illustrative rather than exhaustive, so the classification of a given notification should be assessed rather than assumed. SMS and email sent by your app are clearly inside. Take Turkish advice on your own notification types.
Which app messages can we send without consent?
Article 6 of the Regulation sets out the situations: messages about changes, use and maintenance of goods or services obtained, where the recipient gave their contact details to be reached (6(1)); messages about an ongoing subscription, membership or partnership, and collection, debt reminders and information updates (6(2)), which may not promote or advertise; and messages to merchants and tradespeople (6(3)), until they exercise the right to refuse. Under 6(5), messages under paragraphs 1, 2 and 4 are not checked against İYS. Adding a promotion to such a message changes its character.
Is one consent screen enough for KVKK?
A single screen that combines the privacy notice with a consent tick is the construction the Personal Data Protection Board addressed in decision 2018/90 of 26 July 2018, holding that informing and obtaining explicit consent must be carried out separately and instructing the controller to separate the mechanisms evidencing each. Present the notice as a notice, keep explicit consent as its own unticked affirmative action, and keep marketing permission out of the account creation requirement.
Do we need in-app account deletion?
Apple’s guidelines state that if an app supports account creation, it must also offer account deletion within the app (section 5.1.1(v)). Separately, data subject rights under Law No. 6698 apply regardless of the store rule, arrive in Turkish and are time-bound, so the deletion path should be in the app, in Turkish, and connected to a process that deletes rather than deactivates.
Conclusion
App localisation for Turkey is decided in four places, and the store listing is not one of them.
Establish first which side of the store payment rule your app sits on, because section 3.1.1 and section 3.1.3(e) point in opposite directions and that determines whether the instalment expectation can be met at all. Build the consent screens as separate acts — notice, explicit consent, marketing permission — rather than one tick, following the Board’s 2018/90 reasoning. Classify every notification as service or commercial at template level, using Article 6’s specific situations rather than treating the whole channel one way. And build the interface for Turkish grammar rather than translating into it: suffixes that inflect, strings that run longer, locale-correct case handling, and formats that read as local.
For the listing and acquisition side, our guides to app store optimization in Turkey and mobile app user acquisition in Turkey are the companion pieces, and our pillar guide to marketing in Turkey for foreign brands is the place to start.
This article is general information about mobile app localisation, platform policies and Turkish regulatory obligations, and the provisions and guideline sections cited carry the references given. App store policies and regulations change; confirm the current versions before designing your flows. It is not legal advice, and the classification of your notifications and consent design should be confirmed with qualified Turkish counsel.