Sectors Turkish ↔ English
Banks and fintech
Two different jobs sit under one heading: verifying documents a Turkish-speaking customer supplies, and putting your own product in front of Turkish speakers in language they trust.
Onboarding and lending documents
Customer files bring a T.C. kimlik kartı or passport, an address document, Turkish bank statements and payslips. Mortgage and affordability cases add Turkish employment letters, a tapu where an overseas property is part of the picture, and occasionally an inheritance decision. What lenders ask for is described on translations for banks and mortgage lenders. A growing share of these documents are e-Devlet printouts carrying a verification code, and we translate the code and reference lines as well as the content so that your team can check the document against the issuing system; e-Devlet documents in the UK explains how that works.
Names, and why matching fails
Turkish characters do not survive most systems intact: ç, ğ, ı, ö, ş and ü are dropped, folded or replaced, and a Turkish passport’s machine-readable zone already carries a stripped version of the holder’s name. The same customer therefore appears with several spellings across identity documents, statements and screening lists. We translate each name as it is printed and set out the variants explicitly, which is what a screening or KYC review needs; silently normalising them would defeat the check. The detail is in names, Turkish characters and transliteration.
Customer-facing Turkish
The other half of this work is your own content: app strings, onboarding flows, terms, fee tables, complaint procedures and support articles in Turkish. Financial wording is regulated wording, so a translator’s job here is to carry the meaning across without softening a risk warning or improving a disclosure. We work to a client glossary, keep placeholders and variables intact, and flag any English source sentence that cannot be rendered accurately rather than paraphrasing it. Interface work is handled as website and product localisation, priced by volume rather than per certificate.
How accounts work
Institutions set a page rate and turnaround in advance terms we agree with you in writing before the first job, with a named contact, secure transfer of customer files, restricted access and deletion on instruction. Document work is from £10.00 per 1,000-character page Turkish into English, certification included, no UK VAT charged; a six-month statement set typically comes to £40–90 and a payslip is a single page. Turkish localisation is from £6.50 per page: a 30,000-character string file is about £195, and a short terms update is priced from the file the same working day.
Frequently asked questions
How do you receive customer files securely?
Through the channel you specify — your portal, an encrypted transfer or a password-protected archive. Access is limited to the translator and reviser, and files are deleted on instruction.
Do you verify that a Turkish document is authentic?
No. We translate it and describe the seals, stamps and signatures on it. Authentication is for the issuer or a verification provider.
Can you keep our product terminology consistent across releases?
Yes. We maintain a glossary per client and apply it across documents and interface strings, which matters more in finance than anywhere else.
Is machine translation used?
Not on customer documents. For high-volume support content, post-edited machine translation can be agreed in advance in writing, with the limits stated.