The visible fee is often only part of the cost when USD is sent abroad for conversion by the recipient's bank. That bank sets its own rate on the incoming USD, usually without showing the sender the rate or giving the recipient a mid-market comparison. If a company needs delivery in local currency, the decision is not whether to use a destination-currency provider. It is which provider to select and how to compare their actual economics.
Corridor network depth
Local-currency payout capability varies materially between providers, and catalogue claims may conceal that difference. One provider may support a country through a correspondent bank, with settlement taking two to three days and a spread that differs from its quoted rate. Another may connect directly to the local clearing system, delivering the same currency the same day at a tighter rate. Both can appear as supported. Their operating capabilities are not equivalent.
Network depth describes how directly a provider connects with payment infrastructure in each destination. Direct access to local rails, through a local subsidiary, a licensed payment institution, or an account at a major local clearing bank, generally supports quicker settlement, stronger rates, and fewer intermediary points where value can be deducted in transit.
The clearest differences in network depth are not always in the highest-volume corridors. EUR and GBP payments are broadly supported because SEPA and UK Faster Payments are widely accessible. More variation appears in INR, PHP, IDR, KES, NGN, BRL, and MXN, where some providers have local infrastructure while others use SWIFT correspondents with an embedded markup. For substantial payout volumes in Southeast Asia, South Asia, or Africa, that distinction affects both cost and settlement reliability.
Settlement promises and reality
Marketing claims about settlement timing should be read as ideal-case limits, not operating guarantees. Same-day delivery generally depends on submitting before a stated cut-off, an open destination banking system, accurate recipient details on the first attempt, and no compliance flags. Across a complete payment portfolio, the actual same-day rate is usually below the headline claim.
The conditions that weaken settlement claims are predictable: submissions near or after the same-day cut-off, payments to smaller regional banks without direct fast-rail connectivity, and instructions with an ambiguous bank name or branch code that require manual review. New beneficiaries may also receive additional automated compliance screening on their first payment.
Ask providers for recent-quarter settlement distributions on the corridors you use, rather than advertised lead times. Some will provide the data directly. Others will describe only the best case. How a provider handles this question indicates how openly it expects to report operational performance after onboarding.
Transparent fee structures
Payout pricing must be compared on equivalent components. A USD 2 flat fee appears cheaper than USD 5 until the FX rates are examined: the first may include a 1.5% margin, while the second charges 0.2% above mid-market. On USD 10,000, the provider charging USD 2 has the higher total cost.
Compare the flat payment fee, if any, the FX margin above mid-market, and whether intermediary or destination bank charges are included or passed separately to the sender or recipient. "No fees" is often an incomplete description. It may mean only that the charge is not a separate line item, while cost remains embedded in the rate or the gap between the quoted rate and mid-market.
Some providers show their FX rate against mid-market in real time. If a provider will not show that comparison or state its standard margin for your main corridors, the omission signals how pricing may be treated after you become a customer.
Questions for payout partners
The questions that distinguish providers in practice are more specific than a standard due diligence checklist.
For each key corridor, ask whether settlement uses local rails directly or SWIFT correspondent routing. If it uses SWIFT correspondent routing, ask how many correspondent hops are typical and whether the provider can see the full chain. A provider confident in its infrastructure should answer specifically. One that relies mainly on SWIFT correspondent routing may respond vaguely or refer you to support documentation.
Ask what percentage of payments to your main corridors settled within the advertised window during the latest quarter. A provider with genuine local network depth should hold this data. A provider dependent on correspondent bank processing may not track it, or may acknowledge that performance is outside its direct control.
Ask how compliance screening operates and what follows when a payment is flagged. Clarify the typical resolution time and who owns the resolution. For time-sensitive supplier payments, a queue resolved in four hours is operationally different from one resolved in four business days.
Ask for the margin above mid-market on each currency pair you use regularly, and whether it is fixed or volume-tiered. On high-volume corridors, volume-based tiers may be negotiable according to the provider and relationship size.
Assessing the whole view
No provider will answer every question perfectly, and that is not the objective. Select one whose network fits your actual corridors, whose fee and settlement disclosures support AP planning and reconciliation, and whose support model fits your team's capacity to handle exceptions.
The diligence process itself is revealing: responses to specific operational questions, rather than general product pitches, show which providers treat corporate customers as partners and which regard detailed questions as an inconvenience. That behavior is usually consistent after go live.
