Two sets of books
Western Union has two sets of books, and almost every article you read about the stablecoin story mixes them up.
The first set is what it costs Western Union to move your dollars from the shop or the app to its agent in Manila. For a long time that happened through other banks: a dollar left Western Union, sat in a correspondent bank account over the weekend, cleared on Monday, and was passed on to the agent who paid your mother. That slow pass is what the May launch is replacing.
The second set is what it costs you at the counter. The fee the receipt shows, and the gap between the real exchange rate on Google and the one Western Union gives you. That number has not moved.
The stablecoin is a change on the first set of books. The receipt you get is on the second.
What Western Union actually did
On 4 May 2026, Western Union launched a dollar token called USDPT. It is issued by Anchorage Digital Bank, which is a US-regulated bank that is allowed to hold crypto. It settles on Solana, which is one of the faster blockchains, using software from a firm called Fireblocks. Western Union uses it inside its own network. The pilot countries are the Philippines and Bolivia.
The simple version: instead of parking dollars in a bank over the weekend to settle up with agents, Western Union now parks them in a dollar token that moves between its own wallets at any hour. The money gets to the agent in seconds instead of in days. That is a real change, and it is Western Union's to keep.
In August the company added a second product on top of the token, called the Stablecard. It is a Visa card issued with a partner called Rain. It lets a person who holds the token spend it like dollars. It is live in 37 countries, with Western Union saying it will be in more than 60 by the end of this year. The country list has not been published. If your sister in Manila does not already hold one, it is not relevant to a routine family send. The card is pitched at people in countries where the local currency is losing value, not at UK or US senders paying in.
What Western Union says the stablecoin saves
At an industry event in March, chief executive Devin McGranahan said traditional money transfers cost 2 to 3 percent of the amount sent, and that the stablecoin would bring that down to 0 to 2 percent, depending on the country and the amount. The company's own framing elsewhere is simpler: "USDPT will allow us to own the economics linked to stablecoins."
Read that line again. The saving is on the economics Western Union owns. It is a cost that is coming off Western Union's balance sheet, not off your receipt. The 0 to 2 percent is a projection, and it is a projection for the company, not a quote at the counter.
What $200 to Manila looks like on your receipt
The real exchange rate at the time of writing, the one you get if you search dollar to peso on Google, is about 62.9 pesos per US dollar. That puts $200 at 12,584 pesos. £200 at the real rate is about 16,642 pesos.
Independent cost tables through 2025 and the first half of 2026 have put a Western Union agent cash pickup on a US-to-Philippines send at about 5 to 7 percent all in, and the Western Union app and website at about 2.5 to 4 percent all in. On a $200 send that is roughly $10 to $14 missing at the cash counter, or $5 to $8 missing on the app, by the time the fee and the gap in the rate are both taken into account. Your mother sees between 11,700 and 12,000 pesos at the counter, or 12,100 and 12,300 pesos on the app, instead of 12,584.
On the same $200, Wise charges a visible fee of a dollar or two and gives you a rate within about half a percent of Google's. The peso figure in your mother's bank account or bKash wallet is close to 12,500, with the fee shown on the screen before you send. Remitly from the US to a Philippines bank account on $200 is a $4.99 fee at the time of writing, with the rate itself a few tenths of a percent off Google's. The peso figure comes out close to Wise once both are compared like for like.
The UK side is the same pattern wearing a different label. Western Union's UK page carries a "0 fee first online transfer" line. The company's own footnote says it makes money from the exchange rate. The visible fee is small or missing; the gap sits inside the rate instead. On £200, the receipt from Wise or Remitly arrives within about £1 or £2 of the real rate; the receipt from Western Union typically arrives £5 to £10 short of that, depending on whether you pay in a shop or on the app.
Catch
A "0 fee" headline is not a free send. The real test is the number of pesos shown next to your amount before you confirm. If it is lower than the figure the Wise app shows for the same send, the gap is the price.
The pattern, named once
An operator moves to a cheaper service. The sender's price is a separate decision from the operator's cost. The two have never had to move together, and they rarely do. The man on the corner of a Lagos street knew it in 1980 and the treasury of a 170-year-old wire company knows it in 2026. If the receipt is going to come down, it will come down because another provider has forced the issue, not because the backend got cheaper.
The verdict
Do not wait for Western Union to pass the stablecoin saving on. Send with Wise or Remitly on your next send. Both of them already give you a receipt close to the real exchange rate on a $200 or £200 send, and both show the fee on the screen before you commit. If you walk into the Western Union shop out of habit, ask the person at the counter what you will receive in pesos, and compare that figure against what the Wise app shows you for the same amount. On a routine family send, the gap will cover a bag of rice.
Boki has a longer piece on when a stablecoin is actually cheaper than a transfer app in your own hands: when a stablecoin beats a transfer app. That one is about you holding the token. This one is about Western Union holding it.
Rates and figures on this page were pulled on 2026-10-15. The real USD to PHP rate used is 62.9 pesos per dollar; the real GBP to PHP rate used is about 83 pesos per pound.
Corrections
None so far. If we get something wrong, the fix is dated here.