The Daily Brief
The peso edges up, the pound hits a monthly low, and nobody's saying why
· as of 08:00 GST
Manila's peso nudges up against a steady dirham this morning, which matters more to households here than the swings in Europe's currencies further down the board. There's no attributed reason for any of today's moves — just a board where one corridor drifted the reader's way and others didn't.
What moved
The Philippine peso rose 0.31% against the dirham to 0.058689 AED, a move larger than its usual daily drift. The British pound fell 0.20% to 4.8526 AED, its softest showing in a month. The Swiss franc slipped 0.49% to 4.4295 AED, also its weakest point in the past month. The Egyptian pound fell 0.71% to 0.070933 AED, a sharper daily move than it typically makes.
Corridor spotlight
Sending 1,000 AED to Pakistan gets about 75,448 rupees today — about 10 rupees more than a week ago.
A rotating illustration across the UAE’s main remittance corridors — shown for one corridor each day, not necessarily yours. Find your own rate on the World Rates board.
Crypto beat
Bitcoin rose 0.4% over the last 24 hours and Ethereum rose 0.1%, with bitcoin's share of the total crypto market at 58.6%. Crypto trades around the clock and is volatile — these are 24-hour moves, not a trend. CoinDesk reports the U.S. Federal Reserve has moved on proposals to implement the GENIUS Act for stablecoins, new rules that shape how dollar-pegged stablecoins operate — relevant to any dirham-to-dollar-stablecoin payment rail.
Crypto trades 24/7 — figures from our latest snapshot; see live prices. Reference, not advice — position, never prediction.
This is what happened, not a prediction — we don't say where rates go next.
Gold isn’t included in the fiat movements above — we don’t hold a clean 24-hour baseline for it. Crypto is covered separately in the Crypto beat. See our Methodology.
Sources & transparency
Composed with AI from the data and named sources above, then checked figure-by-figure against them before publishing (model: Claude Sonnet 5). See our Methodology and Editorial policy.