Best execution for a stablecoin payout is the best total result, not the best rate. The six factors, how to weigh them, and the records to keep.
Best execution for a stablecoin payout is the best total result for the payout, not the best exchange rate. It weighs the amount the recipient receives, every fee, the time to funds, and the chance the payout settles on the first try. Proving it takes a written policy and a record of each quote.
The phrase comes from securities law, where it is a legal duty. For a payout it is usually a governance question: when an auditor or a board asks "did we get a fair deal on this conversion," what do you show them? How on/off-ramp providers make money explains what you pay for. This page explains how to show you paid a fair amount.
Key takeaways
From securities regulation. MiFID II, Article 27, requires investment firms to "take all sufficient steps to obtain, when executing orders, the best possible result for their clients taking into account price, costs, speed, likelihood of execution and settlement, size, nature or any other consideration relevant to the execution of the order" (ESMA Interactive Single Rulebook).
That rule is written for orders in financial instruments. A stablecoin payout is a payment, so it usually sits outside it. The factor list still travels well. It is the most precise short definition of "a good result" for any conversion, and it gives finance teams words that auditors already recognize.
The wholesale FX market has its own standard. The FX Global Code, Principle 14, says a dealer's mark up "should be fair and reasonable" and asks dealers to make clear "that their final transaction price may be inclusive of Mark Up" (FX Global Code). Principle 13 asks both sides to understand how reference prices are established.
The same six factors MiFID II lists, translated to a payout. Price and costs set the amount received. Speed and likelihood of settlement set when, and whether, the money arrives. Size and the nature of the payout decide which of the others matters most for a given payment.
| Factor | What it means for a payout | How to measure it | Evidence to keep |
|---|---|---|---|
| Price | The rate you got vs the market rate | Quoted rate vs mid-market at the same minute | Quote, reference rate and its source |
| Costs | Every fee line, plus network and bank costs | Mid-market value minus amount received | Itemized quote fields |
| Speed | Time from execute to funds in the recipient's account | Execute timestamp to completed timestamp | Status history per payout |
| Likelihood of settlement | Chance the payout lands on the first try | Failure and return rate by rail | Failed payouts and their reasons |
| Size | Whether the price holds at your amount | Quotes at several sizes | Quote ladder results |
| Nature | Who receives it and how urgent it is | Payroll, supplier, refund, treasury | Payout category in your ledger |
How to test off-ramp liquidity depth covers the size factor with a quote ladder. Most liquid currency pairs explains why price varies so much by corridor.
Because rate is one factor of six. A provider can quote a tighter rate and deliver on a slower rail, fail more often, or charge fees outside the rate. Each failed payout has its own cost: a new quote at a market that may have moved, someone's time to fix the bank details, and a recipient who waits.
Illustrative example. You pay 50,000 USDC to a supplier in Mexico, monthly. Mid-market is 18.50 MXN per USDC, so the mid-market value is MX$ 925,000. Assume each failed payout costs an adverse move of 0.5% on the retry plus $50 of team time, about MX$ 5,550 in total.
| Route A | Route B | |
|---|---|---|
| Rate vs mid | 0.40% under | 0.50% under |
| Cost in the rate | MX$ 3,700 | MX$ 4,625 |
| Failure rate (assumed) | 2% | 0.2% |
| Expected failure cost | 0.02 × 5,550 = MX$ 111 | 0.002 × 5,550 = MX$ 11.10 |
| Expected total cost | MX$ 3,811 | MX$ 4,636.10 |
| Time to funds | Next business day | Minutes |
Route A still wins on expected cost by MX$ 825.10. Route B wins on speed by about a day. Neither is "best" until you decide what the payout is for. A supplier with a 30-day term takes Route A. Payroll on a Friday afternoon takes Route B. These numbers are assumptions, not any provider's pricing.
That decision belongs in a written policy, made once, not argued payout by payout.
Write the weights down per payout type, then apply them every time. Most teams use a short ranking: for payroll, speed and settlement certainty come first; for supplier payments on terms, cost comes first; for refunds, certainty comes first. The ranking turns a judgment call into a rule you can audit.
A workable policy fits on one page:
Who carries FX risk in a stablecoin payout helps with the speed side: the longer funds sit between steps, the more exchange rate risk someone holds.
The quote and the outcome, plus a reference you captured yourself. If you only keep the provider's rate, you can't show it was fair. If you only keep a market rate, you can't show what you paid. Keep both, at the same minute, with every fee line.
For every payout, store:
BlindPay quotes carry most of this. A payout quote returns commercial_quotation, the raw market rate, blindpay_quotation, the rate net of BlindPay's fee, plus flat_fee, partner_fee_amount, billing_fee_amount, sender_amount, receiver_amount, and expires_at (payout quotes docs). Quotes lock for 5 minutes. Fees vary by rail and network and are disclosed in the live quote before execute; BlindPay does not publish a static rate card, so the quote record is the evidence.
For speed and settlement, BlindPay's rule of thumb is that Pix, PIX Safe, SPEI, and Transfers 3.0 settle in minutes, RTP is instant, and ACH, wire, TED, ACH Colombia, and SEPA take about 1 to 2 business days (payment methods). Log your own times anyway. The policy should rest on what you observed.
Pull the month's quotes and outcomes, group them by corridor and payout type, and check each against the policy. The output is a one-page summary a controller can sign: effective cost per corridor, failure rate per rail, median time to funds, and any payout that broke a threshold, with the reason.
Four numbers per corridor cover most of it:
If a corridor drifts, request competing quotes for a week and compare. The free option inside a locked quote explains why quote windows are short and why providers watch how often quotes lapse, which is one more reason to keep approvals fast.
Write the one-page policy for your top payout type this week. Then export last month's BlindPay quotes and payouts, capture a mid-market reference for each, and compute the four review numbers. The payout quotes docs list the fields to export.
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.