A natural hedge offsets currency risk by matching inflows and outflows in one currency. How it works with Pix on- and off-ramps, and when to net first.
A natural FX hedge offsets currency risk by matching money coming in and going out in the same currency, with no derivatives involved. A company that earns reais and pays reais is naturally hedged on that amount. Stablecoin on- and off-ramps don't create the hedge. They move whatever is left over after you match.
That distinction saves real money. Plenty of teams on-ramp every real they collect, then off-ramp reais again to pay local costs, and pay the spread twice on money that never needed to leave Brazil.
Key takeaways
It's an offset built into how the business operates. AccountingTools describes natural hedges as arising "through the normal course of business", for example when "cash inflows and outflows are in the same currency" (AccountingTools).
The idea is old and widely used. CFO.com has reported on companies "forsaking derivatives for natural hedges", which it defines as "matching revenues and costs for the same currency or offsetting losses in one currency with gains in another" (CFO). Back in 2011, an author of a Georgia Tech Financial Analysis Lab report told CFO.com that natural hedges were "gaining in significance", partly because derivative hedge accounting is such a burden (CFO).
Two limits worth knowing up front. Natural hedges "rarely eliminate all of the risk", per AccountingTools, and CFO.com notes they are "less effective" at reducing translation risk, the effect of rate moves on a multinational's reported earnings.
Because every leg converts. An on-ramp turns BRL into a dollar stablecoin. An off-ramp turns it back. In between, you hold dollars.
Look at what each quote does. A payin quote takes request_amount in reais (with currency_type: sender) and returns the USDC the wallet receives. A payout quote takes USDC and returns the reais the bank account receives. Both show commercial_quotation, the market rate, next to blindpay_quotation, the rate after BlindPay's fee (payout quotes, payin quotes).
So a R$ collected and a R$ paid out through stablecoin rails are two conversions, each with its own margin. Why on-ramp and off-ramp rates differ explains the bid and ask behind that, and how to read an FX quote shows which way each rate points.
None of this is a flaw. It's what a cross-border rail is for. The mistake is using a cross-border rail for money that was never going cross-border.
Illustrative example. A US company with a Brazilian subsidiary collects R$600,000 a month from Brazilian customers and pays R$400,000 a month to Brazilian contractors. The rest goes home in dollars. Assume a mid rate of 5.40 BRL per USD and a 0.5% margin on each conversion.
Gross approach. On-ramp all R$600,000, then off-ramp R$400,000 back for contractors.
| Leg | Arithmetic | Result |
|---|---|---|
| On-ramp rate | 5.40 x 1.005 | 5.427 BRL per USDC |
| R$400,000 in | 400,000 / 5.427 | 73,705.55 USDC |
| Off-ramp rate | 5.40 x 0.995 | 5.373 BRL per USDC |
| Back to BRL | 73,705.55 x 5.373 | R$396,019.90 |
| Round-trip loss | 400,000 - 396,019.90 | R$3,980.10, about 1.0% |
Net approach. Pay the R$400,000 locally from the subsidiary's reais. On-ramp only the R$200,000 that has to reach the US.
The net approach skips the R$3,980.10 round trip every month, about R$47,761 a year, before flat fees. The R$200,000 still pays one margin, because that money genuinely has to cross the border. That's the conversion worth paying for.
The margins here are invented for the arithmetic. Real ones show up in your quotes. BlindPay has no static rate card: per-transaction fees vary by rail and network and are disclosed in the live quote before you execute.
Match by currency and by timing. A natural hedge only works if the money is in the right place at the right moment.
| Situation | Better move | Why |
|---|---|---|
| Local inflows and local outflows, same entity, similar timing | Net locally, convert the surplus | No conversion on matched amounts |
| Local inflows, dollar outflows (US vendors, USDC payouts) | On-ramp and hold USDC | Dollar costs need dollars anyway |
| Dollar inflows, local outflows | Off-ramp per payout with a live quote | One conversion, rate locked per payment |
| Local inflows and outflows but no local entity or account | Round-trip, but time it tight | You pay two margins; keep the gap short to cut rate risk |
| Inflows and outflows months apart | Consider a forward for the economic rate | Matching fails when timing doesn't line up |
The last row is where natural hedging stops. If you collect reais in March and owe reais in September, the flows don't offset in time. Live quote vs forward contract vs fixed rate covers when a forward makes sense alongside a live quote.
Only against dollar costs. USDC is a dollar stablecoin, so holding it means holding dollar exposure.
If your next bills are in dollars, that's exactly right: on-ramp the reais once, hold USDC in a wallet, and pay dollar obligations without converting again. If your next bills are in reais, holding USDC means you're now exposed to BRL strengthening between collection and payment.
Who carries FX risk in a stablecoin payout maps that exposure step by step. The short version: the provider carries it inside a quote window, and you carry it outside one.
A simple monthly routine works for most teams.
commercial_quotation and blindpay_quotation for every conversion. If you see the same reais going in and out within days, that's money a better netting step would have saved.For the on-ramp side of Brazil specifically, how to on-ramp BRL, MXN, ARS, and COP walks through the Pix flow.
It can't fix timing mismatches, and it won't flatten your reported earnings. CFO.com is direct that natural hedges work on transaction exposure and are weaker on translation risk.
It also can't hedge what you can't forecast. A marketplace whose BRL payouts depend on next month's sales has a moving target. The practical answer there is to keep conversion windows short: convert close to the payment, with a binding quote, so the rate risk you carry lasts minutes instead of weeks.
Pull last quarter's flows, group them by currency and week, and add up how many reais you converted to USDC and back within the same month. Then price that round trip with a payin and a payout quote from the payout quotes docs.
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.