WM/R 4pm, PTAX, Banxico FIX, and ECB rates are benchmarks, not prices. When a contract should use a fix, when a payout needs a live quote.
Use a benchmark fix for contracts, valuation, and reporting, and a live quote for the payout itself. A fix such as WM/R 4 p.m., PTAX, Banxico's FIX, or the ECB reference rate is an average of a past window. A live quote is an executable price for your amount right now. Most teams need both.
The confusion shows up at payment time. A supplier invoice says "converted at PTAX," the payout quote says something else, and someone asks which one is right. Both are. They answer different questions. How on/off-ramp providers make money explains the margin inside a quote; this page explains how a benchmark relates to it.
Key takeaways
Four benchmarks cover most payout corridors. Each has an administrator, a window, and a publication time, and none of them is a price you can trade at after it prints. Knowing which one a contract names, and when it was calculated, is the first step to explaining any gap.
| Benchmark | Administrator | How it is set | Typical use |
|---|---|---|---|
| WM/R 4 p.m. UK closing spot | LSEG (WMR) | Calculated from trading data and indicative quotes for more than 150 currencies | Fund valuation, index calculation, settling contracts |
| PTAX (USD/BRL) | Banco Central do Brasil | Arithmetic mean of four daily consultations with currency dealers | Brazilian contracts, tax, accounting |
| FIX (USD/MXN) | Banco de México | Average of wholesale quotes for settlement two banking days later, released from 12:00 | Dollar obligations payable in Mexico |
| Euro reference rates | European Central Bank | Daily concertation between central banks around 14:10 CET, updated around 16:00 CET | Information and reporting |
Sources for each row: the WMR FX Benchmarks fact sheet, which lists uses from "Settling financial contracts" to "Valuation of investment funds"; BCB's open data portal for PTAX; Banxico's FIX page; and the ECB reference rates page.
The ECB is blunt about its own rates: "Using the rates for transaction purposes is strongly discouraged." That sentence applies in spirit to every fix on the list.
Because a fix is published after its window closes, and the market keeps moving. To fill you at the fix, someone has to trade during the window and take the risk that their trades differ from the average. That service exists in wholesale FX, as a fixing order, but it is not the default for a payout.
Three practical reasons a payout uses a live price instead:
So the honest framing is: the fix tells you what the market averaged; the quote tells you what your payout will cost.
When many parties need to agree on one number after the fact. Contracts, tax calculations, financial statements, and month-end valuations all need a rate anyone can look up later and get the same answer. A fix does that. A live quote, timestamped to one minute for one amount, does not.
Use a fix for:
Which reference rate a finance team should use covers the reporting choice in short form.
Every time money actually moves. A live quote is the price at which your specific payout executes: amount, corridor, rail, network, fees, and a window to accept it. It is the only number that tells you exactly what leaves your wallet and what lands in the recipient's account.
BlindPay prices every payout this way. A payout quote returns commercial_quotation, the raw market rate when the quote was created, and blindpay_quotation, the rate net of BlindPay's fee, plus sender_amount and receiver_amount. It locks those numbers for 5 minutes; read expires_at on every response (payout quotes docs). Fees vary by rail and network and are disclosed in the live quote before execute.
If you need a rate held longer than a quote window, that is a different product. Live quote vs forward contract vs fixed rate explains when a forward fits.
Let the fix set the local amount, then use a receiver-side live quote to deliver exactly that amount. The supplier gets what the contract says. Your stablecoin cost moves with the market and the quote. The difference from the fix-implied cost is yours to track, split into movement and execution.
On BlindPay, currency_type: "receiver" makes request_amount the fiat amount the bank account receives, so the quote solves for the stablecoin you send (payout quotes docs).
Illustrative example. A supplier invoice of R$ 540,000 was priced at PTAX 5.40 on the invoice date, an implied cost of 100,000 USD. On payment day the mid-market rate is 5.38, and the live receiver-side quote rate is 5.37 BRL per USDC.
| Step | Calculation | USDC |
|---|---|---|
| Cost implied by the fix | 540,000 / 5.40 | 100,000.00 |
| Cost at payment-day mid-market | 540,000 / 5.38 | 100,371.75 |
| Cost on the live quote | 540,000 / 5.37 | 100,558.66 |
| Market movement since the fix | 100,371.75 minus 100,000.00 | 371.75 |
| Execution cost (spread and fees) | 100,558.66 minus 100,371.75 | 186.91 |
Of the 558.66 USDC gap, two thirds is market movement, which no provider controls. One third is the cost of execution, which is the part to compare across providers. These are illustrative numbers, not BlindPay pricing.
Name one fix per reporting job and one rule for execution. Write which benchmark marks balances at month end, which one contracts reference, and that payouts execute on live quotes captured with a mid-market reference at the same minute. Then no one argues about it in the close.
A short version:
Best execution for stablecoin payouts covers the records that make the execution line defensible.
Pick one contract that names PTAX or FIX. On a BlindPay development instance, create a receiver-side quote for its local amount, record commercial_quotation, and run the movement and execution split above. The payout quotes docs explain currency_type.
Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24/7 treasury, bill pay, and PSP payouts.
Push means the payer sends an ACH transfer. Pull means you debit a connected account. How each funds a USD to USDC on-ramp, the fees, and the return risk.
AP2, ACP, and x402 each verify that an AI agent had permission to spend. Here is what every protocol covers, who backs it, and the reconciliation gap none of them close.