,
. Proper nouns: Revolut, Coutts, UBS, St James's Place, Swiss house, Revolut X, Financial Conduct Authority, Markets in Crypto Assets (MiCA), Cyprus, European Economic Area, Nasdaq. Keep numbers and percentages. Crypto terms: crypto trading, custody, tokens, maker fees, API, TradingView charts, wealth revenue, digital-asset infrastructure, leveraged products, discretionary portfolio management, wealth advisory, mass-affluent, retail banking, minimums, one-stop shop, well-off but not super-rich, hybrid model, incumbents, regulatory runway, depositor coverage, pre-tax profit, black (profit), listing, valuation target. Translate naturally: "blends" -> "menggabungkan", "squarely" -> "tepat", "abandoned" -> "tinggalkan", "outgrown" -> "tumbuh melampaui", "can't — or won't — meet" -> "tidak bisa — atau tidak mau — memenuhi", "effectively a one-stop shop" -> "secara efektif menjadi toko serba ada", "ranks" -> "menjadi salah satu", "charges zero maker fees" -> "mengenakan biaya maker nol", "provides API access" -> "menyediakan akses API", "climbed" -> "naik", "meaningful driver" -> "pendorong signifikan", "grew nearly 300%" -> "tumbuh hampir 300%", "normalising" -> "normalisasi", "combine" -> "menggabungkan", "few incumbents offer" -> "jarang ditawarkan oleh pemain mapan", "granted" -> "memberikan izin", "alongside" -> "bersamaan dengan", "awarded" -> "diberikan", "gives depositor coverage" -> "memberikan perlindungan deposan", "On top of that" -> "Selain itu", "secured" -> "memperoleh", "passportable access" -> "akses yang dapat diportofolio", "broad enough" -> "cukup luas", "posted pre-tax profit" -> "mencatat laba sebelum pajak", "fifth straight year in the black" -> "tahun kelima berturut-turut dalam kondisi untung", "build-up" -> "persiapan", "potential Nasdaq listing" -> "potensi pencatatan di Nasdaq", "reports pointing to" -> "laporan menunjukkan", "valuation target" -> "target valuasi", "test whether" -> "menguji apakah", "credibly pitch itself" -> "dapat secara kredibel mempromosikan dirinya", "crypto-heavy client base" -> "basis klien yang berat kripto", "hand over discretionary portfolios" -> "menyerahkan portofolio diskresioner", "likely shapes" -> "kemungkinan akan membentuk". Meta description: "Revolut will launch a UK private banking unit this summer with a £500,000 deposit threshold, combining traditional wealth management with its crypto exchange. The move targets mass-affluent clients and comes ahead of a potential 2028 Nasdaq listing." Translate: "Revolut akan meluncurkan unit perbankan swasta di Inggris musim panas ini dengan ambang setoran £500.000, menggabungkan manajemen kekayaan tradisional dengan bursa kriptonya. Langkah ini menargetkan klien mass-affluent dan dilakukan menjelang potensi pencatatan di Nasdaq pada 2028." Note: In Indonesian, use "£500.000" (dot as thousand separator) or "£500.000" consistent. In original they use "£500,000" with comma. In Indonesian, decimal comma is used, but for thousands we use period. But in financial contexts, often keep original notation? Better to use period as thousand separator in Indonesian. Also "£500k" in title: keep "£500k" or expand? I'll keep "£500k" as is common. But in content, they wrote "£500,000" and "£3 million", "£1 million", etc. Translate as "£500.000" (with dot) and "£3 juta", "£1 juta". For amounts like "$630,000" -> "$630.000" (dot). Also "$876 million" -> "$876 juta", "$2.3 billion" -> "$2,3 miliar" (comma for decimal). In Indonesian, billion is miliar, trillion is triliun. $2.3 billion is $2,3 miliar. $150 billion to $200 billion -> $150 miliar hingga $200 miliar. "2025" and "2024" years remain. Also note: "Revolut Trading" is a proper noun, keep. "Markets in Crypto Assets (MiCA)" keep acronym. "European Economic Area" -> "Area Ekonomi Eropa" or "EEA"? Better keep "European Economic Area" or translate? I'll translate "Area Ekonomi Eropa" and put acronym in parentheses. "Financial Conduct Authority" -> "Otoritas Perilaku Keuangan" (FCA) but keep original name? Usually in Indonesian media, they keep English name. I'll keep "Financial Conduct Authority" and add "FCA" if needed. But original says "The Financial Conduct Authority granted Revolut Trading permission..." so keep as is. Also "Coutts", "UBS", "St James's Place", "Swiss house" -> "Swiss house" might be "rumah Swiss" but better "bank Swiss". I'll translate "Swiss house" as "bank Swiss". "St James's Place" is a proper noun, keep. "mass-affluent" -> "mass-affluent" is a term, often translated as "kaya massal" but better keep "mass-affluent" or "kalangan makmur massal"? I'll use "kalangan makmur massal" or just "mass-affluent" with explanation? In Indonesian crypto articles, they sometimes keep English terms. I'll use "mass-affluent" in quotes or translate as "kalangan makmur menengah atas"? But original says "mass-affluent gap" -> "celah mass-affluent". I'll keep "mass-affluent" as is, or translate as "kelas menengah atas yang makmur"? Let's decide: Use "mass-affluent" (konsumen dengan kekayaan menengah atas) but to be natural, I'll say "klien mass-affluent" since it's a known term. In meta: "mass-affluent clients" -> "klien mass-affluent". Also "retail banking" -> "perbankan ritel", "wealth advisory" -> "konsultasi kekayaan", "discretionary portfolio management" -> "manajemen portofolio diskresioner", "leveraged products" -> "produk leverage", "crypto trading and custody operation" -> "operasi perdagangan dan kustodian kripto", "crypto arm" -> "lengan kripto", "crypto stack" -> "tumpukan kripto", "digital-asset infrastructure" -> "infrastruktur aset digital", "hybrid model" -> "model hibrida", "incumbents" -> "pemain mapan", "regulatory runway" -> "landasan regulasi", "depositor coverage" -> "perlindungan deposan", "pre-tax profit" -> "laba sebelum pajak", "in the black" -> "dalam kondisi untung", "build-up" -> "persiapan", "valuation target" -> "target valuasi", "crypto-heavy client base" -> "basis klien yang banyak berkecimpung di kripto". Now write JSON. Ensure proper escaping of quotes. Use double quotes for JSON keys and string values. The HTML content will be a single string with escaped quotes if any. But we are writing JSON in response, so we need to escape double quotes inside the string. However, the HTML content contains double quotes in attributes? No, it only has
and
