Ramp Radar

Methodology

How route ranking is calculated

We make the calculation logic visible so users can understand why a route wins on price, speed or risk before leaving for a provider.

Calculation model

The route engine separates provider quotes, known fees, spread and data quality signals instead of hiding them inside one opaque score.

Net received

Provider returned amount minus known provider, rail, card, wallet and network fees that are visible to us.

Estimated spread

Difference between the route effective rate and a benchmark built from CEX spot prices plus FX mid-rate.

Route confidence

Source quality, quote freshness, provider availability, KYC/limit fit and route caveats combined into one confidence signal.

No markup
Source-aware
Provider executes
01

What we compare

Fiat-to-crypto and crypto-to-fiat routes for the selected amount, country, payment rail, fiat currency, stablecoin and network.

02

What "net received" means

The estimated amount expected to arrive after visible provider, payment, wallet and network costs. Unknown bank or issuer fees stay flagged separately.

03

How we estimate known fees

Known fees come from live provider responses, published fee tables and stored route capability metadata. We do not invent hidden charges.

04

How we estimate spread

We compare the route effective rate with a neutral benchmark from crypto spot markets and fiat mid-rates, then show the deviation as route cost.

05

How we calculate confidence

Confidence rises with live quotes, fresh checks, official sources and stable route metadata. It falls when data is stale, partial or caveated.

06

What data sources we use

Official provider APIs, provider pages, public fee disclosures, market benchmarks, internal quote snapshots and manual review notes where needed.

07

How often data is checked

Live routes are checked during comparison, while provider health and stored snapshots are refreshed on scheduled jobs and manual review runs.

08

Why quotes may differ

Provider rates can move, card issuers can add fees, KYC can change limits and final execution happens on the provider side after redirect.

09

What we do not do

We do not custody funds, execute exchanges, add markup, sell order flow, bypass KYC or guarantee provider approval.

10

Legal and compliance disclaimers

Route output is informational analytics, not legal, tax, investment, AML or financial advice. Provider terms and local rules control.